|
||||||||
|
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.
I would also welcome if this Improvement would be done.
Could someone give at least some clue what to change in the source code of this plugin to make it happen? Then at least those who need it desperately could patch this plugin for themselves.
I tried to quickly look at the source and in ClaimPublisher.perform() and I saw this:
if (build.getResult().isWorseThan(Result.SUCCESS)) {
ClaimBuildAction action = "" ClaimBuildAction(build);
build.addAction(action);
So I'm puzzled why it does not work (I'm not familiar with the source code and I may look it at the wrong place).
Also, claiming of Unstable builds seems to work in Maven projects for some reason. What makes it work there?![]()
)
(Surely, this problem with the claim plugin does not help with migration to Gradle.