-
New Feature
-
Resolution: Fixed
-
Critical
-
None
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.
- links to
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-41255Propagate SCMSource id changes when the new SCMSource is identical to the old