Details
-
Type:
Improvement
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: mercurial-plugin
-
Labels:None
-
Similar Issues:
Description
By fixing JENKINS-4972, the mercurial plugin discards merges for the purpose of triggering builds and determining culprits.
This makes sense when the merge is within a single named branch (i.e. it is during the regular flow of development).
It does not make a lot of sense to drop the merge when it is a merge across named branches. These merges are typically merges of a fix from one version branch to another version branch, and if this merge introduces errors, the merger wants to know about it.
Attachments
Issue Links
- is blocking
-
JENKINS-12048 Wrong option "--branch" used by change polling
-
- Resolved
-
-
JENKINS-4972 Ignore merge changesets when filtering by module for polling
-
- Closed
-
- is duplicated by
-
JENKINS-12052 Polling a mercurial repo fails when the only change to the branch since the last build is a merge
-
- Resolved
-
Code changed in jenkins
User: Jesse Glick
Path:
src/main/java/hudson/plugins/mercurial/HgExe.java
src/main/java/hudson/plugins/mercurial/MercurialSCM.java
src/test/java/hudson/plugins/mercurial/MercurialSCMTest.java
http://jenkins-ci.org/commit/mercurial-plugin/3b54094736fc31fe159c2f5fa80d91b64db47851
Log:
[FIXED JENKINS-7594] Merges across named branches should not be ignored.
Rewriting compareRemoteRevisionWith to use 'hg st --rev ... --rev ...' which is simpler and more robust than examining intermediate csets.