|
||||||||||||||
|
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.
This case does represent an issue; the only the default promotion levels are supported. But since Ronan who opened this case, clearly states that this is apparently not Ronan's concern but rather that the plugin is trying to change the promotion level ...al all
This is by design: We're looking for a baseline with a certain promotion level, and when we're done with it, we'll flip the promotion level - either to the next - or to rejected - dependent on the outcome of the build step.
If we didn't flip the promotion level , the build would simple build the same baseline over and over again.
There is a workaround for this based on setting the promotion level to the option "ANY" in this mode the plugin will build the lates baseline - no matter what promotion level it has.
I'm closing this "Not a defect" and opening a new "Only default Promotion levels are supported" instead.