Project: bamboo
Issue BAM-9511: Mercurial Repository should correctly filter changesets since last build (even if there was more than 100 changesets)
http://tardigrade.sydney.atlassian.com:8085/bamboo/browse/BAM-EXT-4049 on bamboo-hg repository, lastVcsRevisionKey = 1c969a8270b7b6b70ff7f855a31fde22d3abae0c (Marcin Gardias code change) currentRevisionKey = 06998bc525a291de042309b8972e5d743d491d8b (Krystian's merge) between those two revisions Bamboo has found 106 code changes. Due to hard limit (100 changeset parsed for the build, no more) the Mercurial Repository falsely filters out the not-relevant changesets to current branch: bq. The Mercurial Plugin might incorrectly report the changesets triggering the build *if* there was more than 100 (HgRepository.CHANGESET_LIMIT) changes between the last build. The Mercurial Plugin will just have not enough information to traverse the changeset graph properly and will in defense report all changesets between, even those non-related to the built branch. Code responsible is near here: [HgCommandProcessor.filterOutUnreachableChangesets|https://atlaseye.atlassian.com/browse/bamboo-hg/components/bamboo-plugins/bamboo-plugin-mercurial/src/main/java/com/atlassian/bamboo/plugins/hg/HgCommandProcessor.java?r=d8b981d129d0#to384] I'm raising this issue so we can have a look at in in better detail.
Story points: 2