Thanks for the comments. I have read a lot more up on it, and I know better understand why the behavior is like it is.

It's sufficient to read the big yellow warning on https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin

I don't think it will help to rephrase the warning, since it is in the wrong place. You need that information when you are configurating your promotion, not when you are installing the plugin. The person creating the promotions will most likely never have seen the install page, unless your company has a single person managing all builds on Jenkins and its installation.

Secondly I don't find the advice to use permalink very useful, since it can only refer to the latest build/promotion. The promotion is tied to a specific build, so it does not make much sense to use artifacts from a newer version of the build.

I have not been able to find any documentation/guide/tutorial describing this properly, so I decided to write one here. In short: you should set build number to ${PROMOTED_NUMBER} instead of using a permalink, when you copy artifacts.

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/d/optout.

Reply via email to