-
Improvement
-
Resolution: Postponed
-
Major
The current multijob implementation passes parameters to the specific downstream job builds that are part of it. The master value overwrites the default values of the downstream jobs for that parameters.
It would be handy if the multijob plugin has an intuïtive way to pass select information to these specific downstream builds.
This would allow the batch to overwrite a downstream job parameter with a value that is fixed (non-interactive) at the multijob level. Or it would allow to pass the multijob build number as a value with a specific name (e.g. BATCH_NUMBER) chosen by the user.
The downstream jobs can then check if this value exists, otherwise it will be an unresolvable macro and just stay empty.
Use case:
Using the build-name-setter plugin, the downstream build numbers could be set to ${BUILD_NUMBER}${BATCH_NUMBER}, where batch number is either empty (when the downstream job is run on its own) or " - Batch ${BUILD_NUMBER}" (when the variable was set in the upstream multijob project).
[JENKINS-17827] An intuïtive way to pass a variable/parameter (e.g. multijob build number) to all its downstream jobs.
Brother Bear
created issue -
Jenkins IRC Bot
made changes -
| Component/s | New: core [ 15593 ] | |
| Component/s | Original: parameters [ 15594 ] |
| Workflow | Original: JNJira [ 149123 ] | New: JNJira + In-Review [ 177258 ] |
| Component/s | Original: core [ 15593 ] | |
| Component/s | Original: envinject-plugin [ 15893 ] |
| Assignee | Original: Gregory Boissinot [ gbois ] |
Brother Bear
made changes -
| Comment | [ Is there any progress on this already? Thanks! ] |
Closing issue as part of tikal-multijob-plugin issues cleanup.
If still relevant, please open a matching issue in https://github.com/jenkinsci/tikal-multijob-plugin/issues (you can refer to this issue in its description)
| Resolution | New: Postponed [ 6 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
It has nothing to do with EnvInject or Jenkins core