[
https://issues.jenkins-ci.org/browse/JENKINS-13056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160278#comment-160278
]
Ulli Hafner commented on JENKINS-13056:
---------------------------------------
Ok, I understand. I.e. we need some kind of ancestor of a build. This might be
not trivial since not every SCM change will lead to a new build.
{quote}
Also it seems (but I'm highly uncertain so please correct me if I'm wrong),
that also unstable builds are considered for the reference build (and only
failed ones are excluded). Thus it is not enough to set the status threshold
(either new or total) for unstable but one has to set it for failed if one
wants to affect the reference build. Also I assume that only the status
threshold and not the health threshold effect the reference build.
{quote}
Currently, a reference build is obtained from the last build that has a
successful (not unstable) warnings result. The warnings result is independent
from the overall build result.
> 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
