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

          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

          Fixed in 1.4.5. Should appear in Update Center in next 24h.

          Kanstantsin Shautsou added a comment - Fixed in 1.4.5. Should appear in Update Center in next 24h.

          Arun Sangal added a comment -

          I have Jenkins 1.573, Build Pipeline Plugin: 1.4.7 – this issue still exists! Downstream job has a parameter (blank value as default and parameter type is validating parameter where it makes sure whether you have either a number or character etc).

          Issues:
          1. Clicking "run" green little icon on the downstream job is NOT prompting for any user input.
          2. While downstream job is running, it shows a progress bar (blue/white), clicking this progress bar is NOT bringing up the console window.

          Does update in Build Pipeline plugin requires an update in Jenkins core as well?

          Arun Sangal added a comment - I have Jenkins 1.573, Build Pipeline Plugin: 1.4.7 – this issue still exists! Downstream job has a parameter (blank value as default and parameter type is validating parameter where it makes sure whether you have either a number or character etc). Issues: 1. Clicking "run" green little icon on the downstream job is NOT prompting for any user input. 2. While downstream job is running, it shows a progress bar (blue/white), clicking this progress bar is NOT bringing up the console window. Does update in Build Pipeline plugin requires an update in Jenkins core as well?

          Arun Sangal added a comment -

          Build Pipeline plugin 1.4.7 - this issue still exists. Have two other issues too. PS my comment.

          Thanks a lot.

          Arun Sangal added a comment - Build Pipeline plugin 1.4.7 - this issue still exists. Have two other issues too. PS my comment. Thanks a lot.

          Patrick Ryan added a comment -

          +1
          I tried downgrading to 1.4.5 without success.

          If I have job A manually trigger job B, when I click the arrow to start job B, I would expect a build with parameters screen when I can choose things that will affect the rest of the pipeline.

          My example is a manual test that we may not want to run every time. When the pipeline gets to that point, I want it to be up to the user whether or not to spin up the env and run the tests. Therefore when they start that job, there will be a true/false that the user can pick which will decide the output.

          Thanks!

          Patrick Ryan added a comment - +1 I tried downgrading to 1.4.5 without success. If I have job A manually trigger job B, when I click the arrow to start job B, I would expect a build with parameters screen when I can choose things that will affect the rest of the pipeline. My example is a manual test that we may not want to run every time. When the pipeline gets to that point, I want it to be up to the user whether or not to spin up the env and run the tests. Therefore when they start that job, there will be a true/false that the user can pick which will decide the output. Thanks!

          Jean-Baptiste Brajkovic added a comment - - edited

          +1 Arun Patrick.
          Jenkins 1.620.
          Build pipeline Plugin 1.4.7, still the issue with the "Run" button which does nothing when the first task takes parameters.

          We have to go on the first tasks manually and run it from here.

          Jean-Baptiste Brajkovic added a comment - - edited +1 Arun Patrick. Jenkins 1.620. Build pipeline Plugin 1.4.7, still the issue with the "Run" button which does nothing when the first task takes parameters. We have to go on the first tasks manually and run it from here.

          +1

          We have the same problem with Jenkins ver. 1.609.2 and Build Pipeline 1.4.7

          jorge middleton added a comment - +1 We have the same problem with Jenkins ver. 1.609.2 and Build Pipeline 1.4.7

          Bruno Martins added a comment -

          +1

          Same problem with Jenkins Jenkins ver. 1.609.2 and Build Pipeline 1.4.8

          Bruno Martins added a comment - +1 Same problem with Jenkins Jenkins ver. 1.609.2 and Build Pipeline 1.4.8

          +1
          Same problem with Jenkins 1.634 and Build Pipeline 1.4.8

          Wolfgang Lumetsberger added a comment - +1 Same problem with Jenkins 1.634 and Build Pipeline 1.4.8

          Arun Sangal added a comment -

          OK, today it's totally broken. Till last week I was able to see a nice representation of the whole pipeline. After upgrading to 1.4.8 (latest Build pipeline plugin), now the boxes (which represent each triggered build/job call) are squeezed now and doesn't look good.

          What worst is clicking the "Run" button to even run the first job is bringing up a modal window (popup) but it's now not even showing up any parameters.

          http://s000.tinyupload.com/index.php?file_id=03793493629898722609

          Arun Sangal added a comment - OK, today it's totally broken. Till last week I was able to see a nice representation of the whole pipeline. After upgrading to 1.4.8 (latest Build pipeline plugin), now the boxes (which represent each triggered build/job call) are squeezed now and doesn't look good. What worst is clicking the "Run" button to even run the first job is bringing up a modal window (popup) but it's now not even showing up any parameters. http://s000.tinyupload.com/index.php?file_id=03793493629898722609

          Matt Williams added a comment -

          I'm still seeing this on:

          Jenkins 1.638
          Build Pipeline plugin 1.4.8
          Parameterized Trigger plugin 2.29

          Clicking the 'Run' button does nothing and neither does clicking the Console Output button if set to 'lightbox' mode.

          I can re-run finished jobs without problems though.

          Matt Williams added a comment - I'm still seeing this on: Jenkins 1.638 Build Pipeline plugin 1.4.8 Parameterized Trigger plugin 2.29 Clicking the 'Run' button does nothing and neither does clicking the Console Output button if set to 'lightbox' mode. I can re-run finished jobs without problems though.

          Guy Oh added a comment -

          This issue resolved for me with Jenkins v1.638 and PipeLine version 1.4.9.

          Guy Oh added a comment - This issue resolved for me with Jenkins v1.638 and PipeLine version 1.4.9.

          Confirmed fixed on jenkins 1.620, Pipeline version 1.4.9.
          Thanks!

          Jean-Baptiste Brajkovic added a comment - Confirmed fixed on jenkins 1.620, Pipeline version 1.4.9. Thanks!

          Tero Roininen added a comment - - edited

          Seeing this on:

          • Jenkins 1.638
          • Build Pipeline plugin 1.4.9
          • Parameterized Trigger plugin 2.29

          Didn't get prompted to enter parameters even though the pipeline job has three with defaults and one without a default. Just for information, the build job was created using the Job DSL plugin but I suppose it shouldn't affect on this. The pipeline view seems to correctly state that: "This job has parameters"

          Update: Tested with Safari 9.0.1 (11601.2.7.2) and with Chrome 47.0.2526.73 (64-bit)

          Tero Roininen added a comment - - edited Seeing this on: Jenkins 1.638 Build Pipeline plugin 1.4.9 Parameterized Trigger plugin 2.29 Didn't get prompted to enter parameters even though the pipeline job has three with defaults and one without a default. Just for information, the build job was created using the Job DSL plugin but I suppose it shouldn't affect on this. The pipeline view seems to correctly state that: "This job has parameters" Update: Tested with Safari 9.0.1 (11601.2.7.2) and with Chrome 47.0.2526.73 (64-bit)

          We still experience the same issue:

          • Jenkins 1.639
          • Build Pipeline plugin 1.4.9
          • Parameterized Trigger plugin 2.29

          Tested with Chrome 47.0.2526.80 and IE 11.0.9600.18097

          Peter van 't Hof added a comment - We still experience the same issue: Jenkins 1.639 Build Pipeline plugin 1.4.9 Parameterized Trigger plugin 2.29 Tested with Chrome 47.0.2526.80 and IE 11.0.9600.18097

          I'm having this problem, too.

          Vanessa Schissato added a comment - I'm having this problem, too.

          Still a problem for:

          Jenkins 1.654
          Build Pipeline plugin 1.5.2
          Parameterized Trigger plugin 2.30

          Tested with Chrome 49.0.2623.87 m, and Firefox 44.0.2.

          Katherine Morgan added a comment - Still a problem for: Jenkins 1.654 Build Pipeline plugin 1.5.2 Parameterized Trigger plugin 2.30 Tested with Chrome 49.0.2623.87 m, and Firefox 44.0.2.

          Eddie Sholl added a comment -

          I've submitted a pull request for this issue with a potential solution. It's available at https://github.com/Diabol/delivery-pipeline-plugin/pull/175

          Eddie Sholl added a comment - I've submitted a pull request for this issue with a potential solution. It's available at https://github.com/Diabol/delivery-pipeline-plugin/pull/175

          Nico Falk added a comment -

          Any news on this issue?

          Nico Falk added a comment - Any news on this issue?

          DEREK LU added a comment -

          We have a use case to manually start job (from build pipeline) with prompting the user to input values for parameters. is there a plan to have this fixed? Thanks.

          DEREK LU added a comment - We have a use case to manually start job (from build pipeline) with prompting the user to input values for parameters. is there a plan to have this fixed? Thanks.

          We would also very, very appreciate seeing this solved: Currently we're having several more or less awkward workarounds for this:

          • Let the jenkins job get the necessary info from a properties file, which is either located in the jobs' workspace or inside a version control system
          • "Ask" the user by sending an email and parse the reply

          Note: Yes, there now is the workflow plugin, which admittetly makes the construction of pipelines much more easier and already allows for entering parameters on manual approval steps. But waiting for user input results in the pipeline job to be keep "running", which feels (at least IMO) not very well, especially if the manual approval takes a long time (days or even weeks) ...

          Florian Miedniak added a comment - We would also very, very appreciate seeing this solved: Currently we're having several more or less awkward workarounds for this: Let the jenkins job get the necessary info from a properties file, which is either located in the jobs' workspace or inside a version control system "Ask" the user by sending an email and parse the reply Note: Yes, there now is the workflow plugin, which admittetly makes the construction of pipelines much more easier and already allows for entering parameters on manual approval steps. But waiting for user input results in the pipeline job to be keep "running", which feels (at least IMO) not very well, especially if the manual approval takes a long time (days or even weeks) ...

          That is the same reason why I don't have switched to pipeline (formerly workflow) plugin. Please vote for the corresponding Issue: https://issues.jenkins-ci.org/browse/JENKINS-37515

          Torsten Kleiber added a comment - That is the same reason why I don't have switched to pipeline (formerly workflow) plugin. Please vote for the corresponding Issue: https://issues.jenkins-ci.org/browse/JENKINS-37515

          @tkleiber: Great to hear, others are dealing with the same problems Do you have any workaround found for the "stalling pipeline issue"?

          Florian Miedniak added a comment - @ tkleiber : Great to hear, others are dealing with the same problems Do you have any workaround found for the "stalling pipeline issue"?

          Unfortunatly not.

          Torsten Kleiber added a comment - Unfortunatly not.

          DEREK LU added a comment -

          The Pipeline as code can promote for parameter value input, but it holds the executor. Our use case is to provide approval note from one stage to another, which may happen several days later.
          I have implemented a workaround in our case for now.
          Let the Manual Approving Job check a file parameter to decide to move forward or not.
          Then created another job to accept values for the parameter and save it to a file.
          In the Build pipeline, a string parameter is used to create a link to the parameter entering job, and it is displayed in the reversion box.
          the links is like
          <a onclick="buildPipeline.fillDialog('job/ParameterEntering/build?delay=0sec', 'Enter Parameters')"> Enter Parameters</a>
          This will popup the job in a lightbox within the build pipeline.
          It is complicated and just a workaround. We really hope if this issue can get fixed soon.

          DEREK LU added a comment - The Pipeline as code can promote for parameter value input, but it holds the executor. Our use case is to provide approval note from one stage to another, which may happen several days later. I have implemented a workaround in our case for now. Let the Manual Approving Job check a file parameter to decide to move forward or not. Then created another job to accept values for the parameter and save it to a file. In the Build pipeline, a string parameter is used to create a link to the parameter entering job, and it is displayed in the reversion box. the links is like <a onclick="buildPipeline.fillDialog('job/ParameterEntering/build?delay=0sec', 'Enter Parameters')"> Enter Parameters</a> This will popup the job in a lightbox within the build pipeline. It is complicated and just a workaround. We really hope if this issue can get fixed soon.

          DEREK LU added a comment -

          I made some change in my local as a customized workaround.
          Also I created a poll request "Provide an ability to enter build notes/parameters for a Manual step in the pipeline"
          https://github.com/geoffbullen/build-pipeline-plugin/pull/4
          Hope it can be developed and included in a formal release.

          DEREK LU added a comment - I made some change in my local as a customized workaround. Also I created a poll request "Provide an ability to enter build notes/parameters for a Manual step in the pipeline" https://github.com/geoffbullen/build-pipeline-plugin/pull/4 Hope it can be developed and included in a formal release.

          Juan Alvarez added a comment -

          Same here with Jenkins 2.7.2 and Build Pipeline Plugin 1.5.4.

          Juan Alvarez added a comment - Same here with Jenkins 2.7.2 and Build Pipeline Plugin 1.5.4.

          Same here with Jenkins 2.150.2 and Build Pipeline 1.5.8

          Stephen Hallyburton added a comment - Same here with Jenkins 2.150.2 and Build Pipeline 1.5.8

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

              Created:
              Updated: