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

          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: