|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-14292) warnings-plugin chooses wro... [email protected] (JIRA)
- [JIRA] (JENKINS-14292) warnings-plugin choose... [email protected] (JIRA)

Sorry about replying so late; missed the notification email, apparently.
I cannot really tell what version of the plugin the reference builds used. I don't think I was far behind on the upgrades, but it could have been a month or two ... 4.6 was the newest when I upgraded.
Here are some console output snippets:
First we have build #760 of jobA:
Build #700 is gone by now. Actually things started working as expected as the old builds expired, which backs your incompability statement. It would have been nice, though, if the plugin had chosen no reference instead of one it couldn't use anyway.
Next snippet is from build #284 of jobB:
This one shows that the tasks plugin has a different idea about reference than the warnings plugin.
The reference builds were in both cases (and many more cases) the last build made before upgrading to warnings 4.6.
The problem seems to have "solved" itself as the builds expire, but that only works because we do expire builds...