Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-19121

Build pipeline plugin no longer prompts for parameters of parameterised job

      This used to work in 1.3.3. Where if the first job or a manually triggered job that was parameterized. Is triggered then the user is prompted to specify the parameters.

      This is no longer the case, I've tested both scenario's described. Downgrading is not an option because 1.3.5 fixes an issue with the pipeline rendering.

          [JENKINS-19121] Build pipeline plugin no longer prompts for parameters of parameterised job

          Feroz Panwaskar created issue -

          As an educated guess this may have come in because of this change for integration with the parameterized trigger plugin:

          https://github.com/jenkinsci/build-pipeline-plugin/commit/c7f243658eb5630bf6241b41db95187cef136148

          Feroz Panwaskar added a comment - As an educated guess this may have come in because of this change for integration with the parameterized trigger plugin: https://github.com/jenkinsci/build-pipeline-plugin/commit/c7f243658eb5630bf6241b41db95187cef136148

          Can confirm this is an issue with Jenkins 1.532.1 and build-pipeline-plugin 1.4.2.

          This is something of a showstopper for us when it comes to setting up our build pipelines. We need to be able to have manual jobs in our pipeline that will prompt the user for input.

          Lance Johnston added a comment - Can confirm this is an issue with Jenkins 1.532.1 and build-pipeline-plugin 1.4.2. This is something of a showstopper for us when it comes to setting up our build pipelines. We need to be able to have manual jobs in our pipeline that will prompt the user for input.

          Can confirm this is an issue with Jenkins 1.532.2 and build-pipeline-plugin 1.4.2.

          Jonas Bang Christensen added a comment - Can confirm this is an issue with Jenkins 1.532.2 and build-pipeline-plugin 1.4.2.

          Can confirm this is an issue with Jenkins 1.552 and build-pipeline-plugin 1.4.2.

          Matias Fernandez added a comment - Can confirm this is an issue with Jenkins 1.552 and build-pipeline-plugin 1.4.2.

          Swithin Foote added a comment -

          Can confirm this is an issue also with Jenkins 1.572, Build Pipeline 1.4.3 and Parameterized Trigger Plugin 2.25

          Swithin Foote added a comment - Can confirm this is an issue also with Jenkins 1.572, Build Pipeline 1.4.3 and Parameterized Trigger Plugin 2.25

          Is anyone able to confirm the expected behavior of the integration of the build pipeline plugin and the parameterized trigger plugin?

          For example, should the user be re-directed to the parameter form or prompted to enter parameters in a lightbox in the pipeline view?

          Is there any documentation for this as there is nothing on the twiki and I couldn't see any tests for it?

          We have been walking through the latest source from Github today and so far we have cannot see any flow in the build pipeline view that would prompt the user to enter parameters in the same way that a normal parameterized build would.

          Stuart Stevenson added a comment - Is anyone able to confirm the expected behavior of the integration of the build pipeline plugin and the parameterized trigger plugin? For example, should the user be re-directed to the parameter form or prompted to enter parameters in a lightbox in the pipeline view? Is there any documentation for this as there is nothing on the twiki and I couldn't see any tests for it? We have been walking through the latest source from Github today and so far we have cannot see any flow in the build pipeline view that would prompt the user to enter parameters in the same way that a normal parameterized build would.

          Jeff Storey added a comment - - edited

          This looks like a duplicate of JENKINS-25427. I submitted that is awaiting approval/merge - https://issues.jenkins-ci.org/browse/JENKINS-25427?focusedCommentId=215682&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-215682

          I believe the reason the prompt for parameters is no longer happening because the bpp.jelly file only displays the prompt when the BuildPipelineView's isProjectParameterized method is true. The problem is that the method doesn't exist. Adding it fixed the issue.

          Jeff Storey added a comment - - edited This looks like a duplicate of JENKINS-25427 . I submitted that is awaiting approval/merge - https://issues.jenkins-ci.org/browse/JENKINS-25427?focusedCommentId=215682&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-215682 I believe the reason the prompt for parameters is no longer happening because the bpp.jelly file only displays the prompt when the BuildPipelineView's isProjectParameterized method is true. The problem is that the method doesn't exist. Adding it fixed the issue.

          Great news, Jeff. Once your fix is approved, then please share the version of the Build Pipeline plugin in which this fix will be included. Have been waiting for this fix a long time now, can't wait to test it

          Jonas Bang Christensen added a comment - Great news, Jeff. Once your fix is approved, then please share the version of the Build Pipeline plugin in which this fix will be included. Have been waiting for this fix a long time now, can't wait to test it
          Kanstantsin Shautsou made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

            jeffastorey Jeff Storey
            fpanwaskar Feroz Panwaskar
            Votes:
            45 Vote for this issue
            Watchers:
            45 Start watching this issue

              Created:
              Updated: