Pipeline data isn't reloaded automatically after editing Pipeline

[JohnNiang]

Describe the bug Pipeline data isn't reloaded automatically after editing Pipeline

Versions used(KubeSphere/Kubernetes) KubeSphere: v3.2.0

To Reproduce Steps to reproduce the behavior:

1. Create a simple Pipeline
2. Go to the detail page
3. Click Edit Jenkinsfile
4. Paste the follow content into the modal

pipeline {
  agent none
  stages{
    stage('Input test') {
      steps {
        input(id: 'deploy-to-prod', message: 'deploy to prod?')
      }
    }
  }
}

5. Click More -> Edit Settings, and add Build Parameters
6. Click OK button to complete editing
7. Click Run button to see nothing but running

Expected behavior

After I click the Run button, I should get a Set Parameters modal like below:

/kind bug /area devops /priority high /milestone v3.2

[ks-ci-bot]

@JohnNiang: You must be a member of the kubesphere/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility.

In response to this:

Describe the bug Pipeline data isn't reloaded automatically after editing Pipeline

Versions used(KubeSphere/Kubernetes) KubeSphere: v3.2.0

To Reproduce Steps to reproduce the behavior:

1. Create a simple Pipeline
2. Go to the detail page
3. Click Edit Jenkinsfile
4. Paste the follow content into the modal

pipeline {
 agent none
 stages{
   stage('Input test') {
     steps {
       input(id: 'deploy-to-prod', message: 'deploy to prod?')
     }
   }
 }
}

5. Click More -> Edit Settings, and add Build Parameters
6. Click OK button to complete editing
7. Click Run button to see nothing but running

Expected behavior

After I click the Run button, I should get a Set Parameters modal like below:

/kind bug /area devops /priority high /milestone v3.2

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[LinuxSuRen]

This issue might be related to https://github.com/kubesphere/ks-devops/issues/144

[JohnNiang]

/remove-priority high /priority medium Due to complexity of asynchronization problem which is not only a console issue, I'll change the priority to medium currently. We will handle it in the future.

[chilianyi]

/close

[ks-ci-bot]

@chilianyi: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.