|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
What shoudl be the logic for setting the version then ?
If I understand correctly, using "Create Delivery Pipeline version" sets an env variable "PIPELINE_VERSION", and also pass it on as a build parameter downstream, whether or no the "set Build display name" is checked or not.
Also, currently the default behavior is to use the first build's display name (whether or not it was set by the mechanism above).
I would propose that the pipeline would look at the PIPELINE_VERSION env variable, starting from the end of the pipeline and moving backwards if necessary (to reflect the fact that you can set/override the pipeline version later in the pipeline). If that env var is not found anywhere in the pipeline instance builds, then the logic would default to the current behavior, in order to maintain backward-compatibility.
Does that sound sensible?
Thanks for your feedback!