Text of github.com › jenkinsci › branch-api-plugin › issues › 640 as Styx crawled it on Nov 19, 2026. The page may have changed since. Only its words are kept, without pictures or layout.

Open the live page

[JENKINS-41255] Upgrading from a navigator that did not assign consistent source ids to a version that does assign consistent source ids causes a build storm on first scan · Issue #640 · jenkinsci/branch-api-plugin · GitHub

Skip to content You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert [JENKINS-41255] Upgrading from a navigator that did not assign consistent source ids to a version that does assign consistent source ids causes a build storm on first scan #640 New issue Copy link New issue Copy link Closed Enhancement Closed [JENKINS-41255] Upgrading from a navigator that did not assign consistent source ids to a version that does assign consistent source ids causes a build storm on first scan #640 Enhancement Copy link Labels component:branch-api-plugin imported-jira-issue priority:critical resolution:fixed Description jenkins-infra-bot opened on Jan 20, 2017 Issue body actions This affects only Organization Folders.

The first time they are scanned - after upgrade - all the SCMSource implementations will be given new permanent IDs rather than getting a random ID with every scan. As an ID change triggers a rebuild, the result is a build storm of all branches in all repositories in the organization folder. Originally reported by stephenconnolly , imported from: Upgrading from a navigator that did not assign consistent source ids to a version that does assign consistent source ids causes a build storm on first scan assignee : stephenconnolly status : Closed priority : Critical component(s) : branch-api-plugin resolution : Fixed resolved : 2017-01-23T21:11:22+00:00 votes : 1 watchers : 4 imported : 20251211-141027 Raw content of original issue This affects only Organization Folders.

The first time they are scanned - after upgrade - all the SCMSource implementations will be given new permanent IDs rather than getting a random ID with every scan. As an ID change triggers a rebuild, the result is a build storm of all branches in all repositories in the organization folder. Activity jenkins-infra-bot commented on Jan 20, 2017 jenkins-infra-bot on Jan 20, 2017 Author More actions Remote links associated with this issue: PR#​74 CloudBees Internal OSS-1894 jenkins-infra-bot commented on Jan 21, 2017 jenkins-infra-bot on Jan 21, 2017 Author More actions scm_issue_link: Original comment link Raw content of original comment: Code changed in jenkins User: Stephen Connolly Path: src/main/java/jenkins/branch/MultiBranchProject.java src/main/java/jenkins/branch/OrganizationFolder.java src/test/java/integration/EventsTest.java http://jenkins-ci.org/commit/branch-api-plugin/95bd3e9b604a13258a4f34c5a7a6fd7569e99cd7 Log: JENKINS-41255 Propagate SCMSource id changes when the new SCMSource is identical to the old Code changed in jenkins User: Stephen Connolly Path: src/main/java/jenkins/branch/MultiBranchProject.java src/main/java/jenkins/branch/OrganizationFolder.java src/test/java/integration/EventsTest.java http://jenkins-ci.org/commit/branch-api-plugin/95bd3e9b604a13258a4f34c5a7a6fd7569e99cd7 Log: JENKINS-41255 "> JENKINS-41255 Propagate SCMSource id changes when the new SCMSource is identical to the old jenkins-infra-bot commented on Jan 21, 2017 jenkins-infra-bot on Jan 21, 2017 Author More actions scm_issue_link: Original comment link Raw content of original comment: Code changed in jenkins User: Stephen Connolly Path: src/main/java/jenkins/branch/MultiBranchProject.java http://jenkins-ci.org/commit/branch-api-plugin/6e2decef355098cb229944bb221248d5080915f7 Log: JENKINS-41255 Actually we should remove both sides of a match Code changed in jenkins User: Stephen Connolly Path: src/main/java/jenkins/branch/MultiBranchProject.java http://jenkins-ci.org/commit/branch-api-plugin/6e2decef355098cb229944bb221248d5080915f7 Log: JENKINS-41255 "> JENKINS-41255 Actually we should remove both sides of a match jenkins-infra-bot commented on Jan 21, 2017 jenkins-infra-bot on Jan 21, 2017 Author More actions scm_issue_link: Original comment link Raw content of original comment: Code changed in jenkins User: Stephen Connolly Path: src/main/java/jenkins/branch/MultiBranchProject.java http://jenkins-ci.org/commit/branch-api-plugin/9394a7eb697ed3cf83f37540b14c5e28fdcad7fb Log: JENKINS-41255 Address code review comments Code changed in jenkins User: Stephen Connolly Path: src/main/java/jenkins/branch/MultiBranchProject.java http://jenkins-ci.org/commit/branch-api-plugin/9394a7eb697ed3cf83f37540b14c5e28fdcad7fb Log: JENKINS-41255 "> JENKINS-41255 Address code review comments jenkins-infra-bot commented on Jan 21, 2017 jenkins-infra-bot on Jan 21, 2017 Author More actions scm_issue_link: Original comment link Raw content of original comment: Code changed in jenkins User: Stephen Connolly Path: src/main/java/jenkins/branch/MultiBranchProject.java src/main/java/jenkins/branch/OrganizationFolder.java src/test/java/integration/EventsTest.java http://jenkins-ci.org/commit/branch-api-plugin/f8676093204464ab9b1dd652297a60aea3f7b245 Log: Merge pull request #74 from stephenc/jenkins-41255 JENKINS-41255 Propagate SCMSource id changes when the new SCMSource is identical to the old Compare: c8d9b63...f867609 Code changed in jenkins User: Stephen Connolly Path: src/main/java/jenkins/branch/MultiBranchProject.java src/main/java/jenkins/branch/OrganizationFolder.java src/test/java/integration/EventsTest.java http://jenkins-ci.org/commit/branch-api-plugin/f8676093204464ab9b1dd652297a60aea3f7b245 Log: Merge pull request #74 from stephenc/jenkins-41255 JENKINS-41255 "> JENKINS-41255 Propagate SCMSource id changes when the new SCMSource is identical to the old Compare: c8d9b63...f867609 jenkins-infra-bot closed this as completed on Jan 23, 2017 jenkins-infra-bot commented on Feb 2, 2017 jenkins-infra-bot on Feb 2, 2017 Author More actions stephenconnolly: Original comment link Raw content of original comment: scm-api-2.0.2 git-2.6.4 or git-3.0.4 branch-api-2.0.2 bitbucket-branch-source-2.0.2 github-branch-source-2.0.1 cloudbees-folder-5.17 workflow-multibranch-2.11 scm-api-2.0.2 git-2.6.4 or git-3.0.4 branch-api-2.0.2 bitbucket-branch-source-2.0.2 github-branch-source-2.0.1 cloudbees-folder-5.17 workflow-multibranch-2.11 jenkins-infra-bot added enhancement imported-jira-issue component:branch-api-plugin resolution:fixed priority:critical on Dec 11, 2025 jenkins-infra-bot added a parent issue on Dec 11, 2025 [JENKINS-41234] SCM API 2.0 Upgrade Fallout github-branch-source-plugin#1029 jenkins-infra-bot removed enhancement on Dec 11, 2025 jenkins-infra-bot added the Enhancement issue type on Dec 11, 2025 Sign up for free to join this conversation on GitHub.

Already have an account? Sign in to comment Metadata Metadata Assignees No one assigned Labels component:branch-api-plugin imported-jira-issue priority:critical resolution:fixed Type Enhancement Projects No projects Milestone No milestone Relationships None yet Development No branches or pull requests Issue actions You can’t perform that action at this time.