|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
Fixed/Workaround in version 2.20.
https://github.com/jenkinsci/promoted-builds-plugin/commit/8e0e17b1e21624cb3db68f23b868fb15d280aae3
The fix was to remove the button display condition which was `isManuallyApproved()`.
Promotions that are "Forced" are not the same as "manually approved".
It is now displayed unconditionally.
There are many use cases for re-executing the promotion, two of them are:
1. it didn't work the first time, duh!
2. side-effects that you want to re-execute.
The "Force promotion" workflow may very well be broken.
You may be able to get more data using/adapting the following groovy script:
import hudson.plugins.promoted_builds.*;jobs = hudson.model.Hudson.instance.getAllItems(FreeStyleProject) job = jobs[0] build = job.lastSuccessfulBuild println build.actions build.getAction(PromotedBuildAction.class).promotions.each { p -> println "promotion:" + p.name + ", manual:" + p.manuallyApproved + ", success:" + p.promotionSuccessful println p.badges }