[
https://issues.jenkins-ci.org/browse/JENKINS-13056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ulli Hafner updated JENKINS-13056:
----------------------------------
Summary: Obtain reference build from SCM/Trigger (was: Warnigs
Reference Build from SCM/Trigger)
Component/s: analysis-core
core
I think that feature is something that should be first added to core (SCM) as
an extension point. E.g. in general the build stable results (test results,
analysis results, etc.) should use that extension point to determine a
reference build. Or is this only meaningful for static analysis?
When this extension point is provided, the static analysis plug-in can use that
extension point to provide that behavior.
Can you please add some build sequences or examples to describe in more detail
your requirements? Currently, in the warnings plug-in a reference build is the
last build with results below a threshold. Should this also be done in your use
case?
> Obtain reference build from SCM/Trigger
> ---------------------------------------
>
> Key: JENKINS-13056
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13056
> Project: Jenkins
> Issue Type: Bug
> Components: analysis-core, core, warnings
> Reporter: Roland Schulz
> Assignee: Ulli Hafner
>
> It would be great if the SCM would be queried for the reference build. If the
> builds are not in order (e.g. because the build are triggered by code review
> (e.g. Gerrit)), it doesn't make sense to use the last build as reference. The
> SCM (e.g. Git) or the Trigger (e.g. Gerrit) would know the previous commit
> which should be used as reference.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
