-
Bug
-
Resolution: Not A Defect
-
Major
I'm using the Parametrized Trigger Plugin. I go into the build and add the action "Trigger parametrized build on other projects". The other "Project" (i.e. the deploy job) appears to execute. However it does not stop and ask for the Parameters that are setup. (Choice, extended choice, etc.). If I execute the deploy job with "Build Now", it will in fact stop for parameters.
[JENKINS-14911] Triggered Build does not stop for Parameters
Nathan Overbey
created issue -
Nathan Overbey
added a comment - The original issue is no longer needed but the issue in the comment still exists. Opening a separate case for that.
Nathan Overbey
added a comment - The original issue is no longer needed but the issue in the comment still exists. Opening a separate case for that. Nathan Overbey
made changes -
| Resolution | New: Not A Defect [ 7 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
cjo9900
added a comment - The Parametrized Trigger Plugin is used to pass parameters from one job to another there is no prompting for parameters as there is no user interaction at this point.
So if you downstream job has parameters you need to pass all of these from the upstream job, using one of the options for creating the parameters. Note the missing parameters are not used or set to the defaults.
If you want the default values for the downstream job there is no need to trigger the job with parameters as these will be added automatically.
cjo9900
added a comment - The Parametrized Trigger Plugin is used to pass parameters from one job to another there is no prompting for parameters as there is no user interaction at this point.
So if you downstream job has parameters you need to pass all of these from the upstream job, using one of the options for creating the parameters. Note the missing parameters are not used or set to the defaults.
If you want the default values for the downstream job there is no need to trigger the job with parameters as these will be added automatically. | Workflow | Original: JNJira [ 145612 ] | New: JNJira + In-Review [ 206082 ] |
Also, after fiddling with the projects so no new jobs will promote properly. My Jenkins is in a really bad state now. I've noticed bad things happen when trying to promote a old build with a build promotion process that has been deleted. (the promotion process stays behind on old builds). Any suggestions on how to fix it without rebuilding my jenkins install?