|
||||||||
|
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'd also like to be able to specify an arbitrary build as the reference for computing the number of new warnings, basically for the same reason: We use a single Gerrit job which usually runs multiple builds for pending changes concurrently, and these builds do not need to finish in the order they were triggered. So computing new warnings wrt the absolute number of warnings in the last stable) build does not make sense, neither for analysis results nor test results etc.
However, I do not see what this has to do with querying the SCM. Instead, I'd propose to add a "build chooser" like in the "Copy artifacts from another project" build step provided by the Copy Artifacts Plugin. If a build referenced by this build chooser exposes warnings of the same type (e.g. FindBugs warnings), that is taken as a reference for computing the number of new warnings. In the Gerrit example, the reference build would be the latest stable post-merge build of our master branch.