-
Improvement
-
Resolution: Fixed
-
Critical
For parametrized promotion:
It is possible to set parameters values only for the first promotion execution for a specific build.
For re-execution parameters cannot be changed. Promotion process gets the same values.
- is related to
-
JENKINS-22005 Repeating/Duplicating promotion parameters
-
- Reopened
-
-
-
- Resolved
-
[JENKINS-8962] Cannot change parameter value for promotion re-execution
Kirill Evstigneev
created issue -
liamjbennett
added a comment - This should be a configurable option. Also you may want to disable the ability to edit parameters if the previous promotion has failed, thus forcing the user to fix the failure before moving on to the next promotion.
liamjbennett
added a comment - This should be a configurable option. Also you may want to disable the ability to edit parameters if the previous promotion has failed, thus forcing the user to fix the failure before moving on to the next promotion. 
Chris Z
added a comment - A little bit frustrating bug. 
Nathan Overbey
added a comment - Would gladly pay for this enhancement Nathan Overbey
made changes -
| Priority | Original: Major [ 3 ] | New: Critical [ 2 ] |
Nathan Overbey
added a comment - Changed issue type from Bug to Improvement Nathan Overbey
made changes -
| Issue Type | Original: Bug [ 1 ] | New: Improvement [ 4 ] |
Nathan Overbey
made changes -
| Labels | New: promoted-builds |
Nathan Overbey
added a comment - ok, my friends. I have found a work around. I wrote a script that executes after the promoted job. It strips out the promotion history (xml) from the build job (build.xml). I then post that xml file to http://jenkinsurl/job/test1/config.xml.
It takes a bit of scripting because you'll need to find the build.xml file.
Would still be nice to have this baked into the plugin in a manor that makes it easy to view the history via UI. My method wacks it in the UI.
Nathan Overbey
added a comment - ok, my friends. I have found a work around. I wrote a script that executes after the promoted job. It strips out the promotion history (xml) from the build job (build.xml). I then post that xml file to http://jenkinsurl/job/test1/config.xml .
It takes a bit of scripting because you'll need to find the build.xml file.
Would still be nice to have this baked into the plugin in a manor that makes it easy to view the history via UI. My method wacks it in the UI.
In case of promote failure due to incorrect parameter given (maybe typo), there is no chance to get it correct again unless triggering a new build and do the promotion.