|
||||||||
|
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.
Yes, the reference build would be always the latest available build of our master job, at least in the project I'm currently working with.
In case someone needs a finer control of the build to use as reference, however, one idea that came to me is to Warnings plugin to provide a post-build action like "store reference warnings". It could provide options like "In every build", "Only stable builds" or "Only non-failed builds". The user could then use it to choose exactly when he/she wants to update the reference warnings (either for that own job or for other jobs), specially if used together with Conditional Build Step plugin or Workflow plugin. This could work somewhat similar to the Clone Workspace SCM.