• Type: New Feature
• Resolution: Fixed
• Priority: Critical
• Component/s: branch-api-plugin
• Labels:

  None

[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

Stephen Connolly created issue - 2017-01-20 14:27

Stephen Connolly made changes - 2017-01-20 14:28

Epic Link

New: JENKINS-41234 [ 177999 ]

Stephen Connolly made changes - 2017-01-20 14:33

Description

New: 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.

Stephen Connolly made changes - 2017-01-20 16:00

Remote Link

New: This issue links to "PR#74 (Web Link)" [ 15294 ]

Stephen Connolly made changes - 2017-01-20 16:00

Status

Original: Open [ 1 ]

New: In Progress [ 3 ]

Stephen Connolly made changes - 2017-01-20 16:00

Status

Original: In Progress [ 3 ]

New: In Review [ 10005 ]

Stephen Connolly made changes - 2017-01-23 21:11

Resolution		New: Fixed [ 1 ]
Status	Original: In Review [ 10005 ]	New: Resolved [ 5 ]

Stephen Connolly made changes - 2017-02-02 12:14

Status

Original: Resolved [ 5 ]

New: Closed [ 6 ]

CloudBees Inc. made changes - 2017-12-05 05:33

Remote Link

New: This issue links to "CloudBees Internal OSS-1894 (Web Link)" [ 18522 ]