-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
-
Build Pipeline 1.4.8 on jenkins 1.628
Active Choices Plug-in 1.2 and Extensible Choice Parameter 1.3.2
I am creating a build pipeline as per the book Gradle In Action, for a big data pipeline which has about 20 deployable artifacts.
It is rare to want to deploy all of them at the same time, so I have tried using Jenkins plugins (Active Choices Plug-in 1.2 and Extensible Choice Parameter 1.3.2) that facilitate user input at a manually triggered step: the user can enter or select those projects that are to be deployed.
This is how they work for me in Build Pipeline 1.4.8 on jenkins 1.628
To supply user input the step must be opened where there is an option to Build with Parameters: that will ask for the user input. This works but other parameters like the build number do not propagate through, so the step fetches the wrong artifacts from nexus and the pipeline screen does not show the status.
If this step is run directly from the pipeline default values for the user input are used, and the pipeline works.
Ideally in the build pipeline to enter user input, the step would not have to be opened.
I have seen this functionality working in the cloudbees workflow plugin.
[JENKINS-30581] user input in build pipeline step breaks the pipeline
Please, improve your issue explanation by including a screenshot and if possible attaching an example project configuration. I'm still not clear which component this issue is referring to.
Finally, Active Choices was designed for interactive selection of parameters while you're using the build submission form. The Active Choices wiki page lists the following as a limitation: The parameters are supposed to be handled only by humans, and at the moment do not work when the job is triggered by plug-ins, API or scripts. Please see this issue for more.
+1 to ioannis - it's not clear to me what the issue is. Please include steps to reproduce and expected / observed behavior.
There was a known issue in the build pipeline 1.4.8 with fancybox not working with jquery 1.1x - specifically an issue working with the extensible-choice-parameter plugin, which it sounds like you used. That's been fixed in master and will be in the 1.4.9 release.
Since there's no feedback on this issue yet I'm going to close it out. Please re-open if you see the behavior again and provide steps to reproduce.
Thanks!
Not sounds like an issue of extensible-choice-parameter.
Remeved it from component/s.