[
https://issues.jenkins-ci.org/browse/JENKINS-12829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162487#comment-162487
]
SCM/JIRA link daemon commented on JENKINS-12829:
------------------------------------------------
Code changed in jenkins
User: Jesse Glick
Path:
src/main/java/hudson/plugins/mercurial/MercurialSCM.java
src/test/java/hudson/plugins/mercurial/MercurialSCMTest.java
http://jenkins-ci.org/commit/mercurial-plugin/a7483f9809464854c6af2d01db7ab6aab1c98461
Log:
Merge pull request #22 from nimeacuerdo/fix-multiple-revisions-per-build-issue
[FIXED JENKINS-12829] A failed update sets revision of build to 000000+
Compare: https://github.com/jenkinsci/mercurial-plugin/compare/99d221c...a7483f9
> A failed update sets revision of build to 000000+
> -------------------------------------------------
>
> Key: JENKINS-12829
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12829
> Project: Jenkins
> Issue Type: Bug
> Components: mercurial
> Affects Versions: current
> Reporter: David Santiago
> Assignee: David Santiago
> Attachments: 000000.png
>
>
> The mercurial plugin ensures that a failed clone operation throws the
> corresponding exception, but that's not the case if the subsequent update
> fails: no check is done of the return code of the hg update command.
> The effect is that the revision of the build is set to 000000+, which causes
> a huge changelog calculation in the next build, as basically the calculated
> log includes all the changesets in the history of the repo.
> I've even seen a worse corner case, where a build is assigned up to three
> different revisions if, for example, two update attempts fail and the third
> one works when using the cache+share extension.
--
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
