In short the possibility to have a dialog before the trigger is executed for accepting parameters. This one is similar to the JENKINS-27238.

      Is it possible? Where would one start to try to implement such a feature?

          [JENKINS-32336] Inject parameters on manual build trigger

          Robert Ozga added a comment -

          I think it should be standard functionality. We still lack this functionality in our project.
          If you initialize the pipeline, it's possible to start a paramatrized job (see JENKINS-20873 ).
          If you want trigger manual step, that is also parametrized job, it's not possible to adjust parameters to this job.

          Robert Ozga added a comment - I think it should be standard functionality. We still lack this functionality in our project. If you initialize the pipeline, it's possible to start a paramatrized job (see JENKINS-20873 ). If you want trigger manual step, that is also parametrized job, it's not possible to adjust parameters to this job.

          yeap i agree
          the behaviour is inconsistent

          • When you trigger job manually from pipeline view it is just started (without possibility of set up parameters)
          • When you trigger the same job from job perspective the "parameter window" is shown

          Marek Kapowicki added a comment - yeap i agree the behaviour is inconsistent When you trigger job manually from pipeline view it is just started (without possibility of set up parameters) When you trigger the same job from job perspective the "parameter window" is shown

          I made a investigation
          When the pipeline is started then the plugin checks parametrs of first job

            if (component.firstJobParameterized) {
                              html.push('&nbsp;<a id=\'startpipeline-' + c  +'\' class="task-icon-link" href="#" onclick="triggerParameterizedBuild(\'' + component.firstJobUrl + '\', \'' + data.name + '\');">');
                          } else {
                              html.push('&nbsp;<a id=\'startpipeline-' + c  +'\' class="task-icon-link" href="#" onclick="triggerBuild(\'' + component.firstJobUrl + '\', \'' + data.name + '\');">');
                          }
          

          and displays the initParam list (if required).

          If the next step requires the parameters this is completly ignored by delivery-pipeline-plugin

          Marek Kapowicki added a comment - I made a investigation When the pipeline is started then the plugin checks parametrs of first job if (component.firstJobParameterized) { html.push( '&nbsp;<a id=\' startpipeline- ' + c +' \ ' class= "task-icon-link" href= "#" onclick= "triggerParameterizedBuild(\' ' + component.firstJobUrl + ' \ ', \' ' + data.name + ' \ ');" >' ); } else { html.push( '&nbsp;<a id=\' startpipeline- ' + c +' \ ' class= "task-icon-link" href= "#" onclick= "triggerBuild(\' ' + component.firstJobUrl + ' \ ', \' ' + data.name + ' \ ');" >' ); } and displays the initParam list (if required). If the next step requires the parameters this is completly ignored by delivery-pipeline-plugin

            patbos Patrik Boström
            judoole Ole Christian Langfjæran
            Votes:
            4 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: