Jesse Glick added a comment - 2018-06-11 19:49 For example, in a dep on workflow-job-plugin , Searching for updates to org.jenkins-ci.plugins.workflow:workflow-job:2.22-rc300.4c8c8ab531e3 within jglick:logs-JENKINS-38381 Found 79 candidates from https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/workflow/workflow-job/2.22-rc344.2563730618be/ down to https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/workflow/workflow-job/0.1-beta-1/ Considering https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/workflow/workflow-job/2.22-rc344.2563730618be/ Mapped to: https://github.com/jenkinsci/workflow-job-plugin/commit/2563730618be282ec4c183338c9c8dcf5f5f1c93 Seems to be within jglick:logs-JENKINS-38381, so accepting Can update dependency org.jenkins-ci.plugins.workflow:workflow-job:jar:2.22-rc300.4c8c8ab531e3 to 2.22-rc344.2563730618be Even though 344 > 300, this is wrong since workflow-job-plugin$ git merge-base 2563730618be 4c8c8ab531e3 2563730618be282ec4c183338c9c8dcf5f5f1c93 Dropping --first-parent would have fixed the problem: workflow-job-plugin$ for c in 2563730618be 4c8c8ab531e3; do echo $c; git rev-list --count --first-parent $c; git rev-list --count $c; done 2563730618be 344 739 4c8c8ab531e3 300 780 Assuming performance is acceptable, it ought to be compatible to change incrementals-tools to use the new strategy, since the change will only apply to commits which pick up the new version of the tool, and the count will be no less than what it would have been otherwise.

Jesse Glick added a comment - 2018-06-15 12:42 Tricky to make sure plugin authors remember to update git-changelist-maven-extension . Maybe plugin-pom can somehow report an Enforcer error if the version in use is older than some threshold.