All included branches are being scanned for a Jenkinsfile for each included pattern. In production, the same branch is being scanned 32 times, resulting in an execution time of 30 seconds for the multibranch scan, rather than 1 second. We have 16 included patterns.
Project repository base: svn://repo/repo1
Include branches: branches/TeamA-, branches/BUG-
Example output (a test repo with only a couple of branches):
[Wed Aug 07 05:43:29 UTC 2024] Starting branch indexing...
Opening conection to svn://repo/repo1/
Checking directory @HEAD
Checking candidate branch trunk@HEAD
'Jenkinsfile' found
Met criteria
No changes detected: trunk (still at 2)
Opening conection to svn://repo/repo1/
Checking directory @HEAD
Checking directory branches@HEAD
Checking candidate branch branches/BUG-1@HEAD
'Jenkinsfile' found
Met criteria
No changes detected: branches/BUG-1 (still at 2)
Checking candidate branch branches/BUG-2@HEAD
'Jenkinsfile' found
Met criteria
No changes detected: branches/BUG-2 (still at 2)
Checking candidate branch branches/DTU-2@HEAD
'Jenkinsfile' found
Met criteria
No changes detected: branches/TeamA-2 (still at 2)
Checking candidate branch branches/DTU-1@HEAD
'Jenkinsfile' found
Met criteria
No changes detected: branches/TeamA-1 (still at 2)
Checking directory branches@HEAD
Checking candidate branch branches/BUG-1@HEAD
'Jenkinsfile' found
Met criteria
No changes detected: branches/BUG-1 (still at 2)
Checking candidate branch branches/BUG-2@HEAD
'Jenkinsfile' found
Met criteria
No changes detected: branches/BUG-2 (still at 2)
Checking candidate branch branches/TeamA-2@HEAD
'Jenkinsfile' found
Met criteria
No changes detected: branches/TeamA-2 (still at 2)
Checking candidate branch branches/TeamA-1@HEAD
'Jenkinsfile' found
Met criteria
No changes detected: branches/TeamA-1 (still at 2)
Opening conection to svn://repo/repo1/branches/
Checking directory /branches@HEAD
[Wed Aug 07 05:43:29 UTC 2024] Finished branch indexing. Indexing took 0.12 sec
Finished: SUCCESS
Originally reported by
pwiseman, imported from: Subversion include branches are scanned too many times
- status: Open
- priority: Major
- component(s): subversion-plugin
- resolution: Unresolved
- votes: 0
- watchers: 1
- imported: 20251212-090250
Raw content of original issue
All included branches are being scanned for a Jenkinsfile for each included pattern. In production, the same branch is being scanned 32 times, resulting in an execution time of 30 seconds for the multibranch scan, rather than 1 second. We have 16 included patterns.
Project repository base: svn://repo/repo1
Include branches: branches/TeamA-, branches/BUG-
Example output (a test repo with only a couple of branches):
[Wed Aug 07 05:43:29 UTC 2024] Starting branch indexing...
Opening conection to svn://repo/repo1/
Checking directory @HEAD
Checking candidate branch trunk@HEAD
'Jenkinsfile' found
Met criteria
No changes detected: trunk (still at 2)
Opening conection to svn://repo/repo1/
Checking directory @HEAD
Checking directory branches@HEAD
Checking candidate branch branches/BUG-1@HEAD
'Jenkinsfile' found
Met criteria
No changes detected: branches/BUG-1 (still at 2)
Checking candidate branch branches/BUG-2@HEAD
'Jenkinsfile' found
Met criteria
No changes detected: branches/BUG-2 (still at 2)
Checking candidate branch branches/DTU-2@HEAD
'Jenkinsfile' found
Met criteria
No changes detected: branches/TeamA-2 (still at 2)
Checking candidate branch branches/DTU-1@HEAD
'Jenkinsfile' found
Met criteria
No changes detected: branches/TeamA-1 (still at 2)
Checking directory branches@HEAD
Checking candidate branch branches/BUG-1@HEAD
'Jenkinsfile' found
Met criteria
No changes detected: branches/BUG-1 (still at 2)
Checking candidate branch branches/BUG-2@HEAD
'Jenkinsfile' found
Met criteria
No changes detected: branches/BUG-2 (still at 2)
Checking candidate branch branches/TeamA-2@HEAD
'Jenkinsfile' found
Met criteria
No changes detected: branches/TeamA-2 (still at 2)
Checking candidate branch branches/TeamA-1@HEAD
'Jenkinsfile' found
Met criteria
No changes detected: branches/TeamA-1 (still at 2)
Opening conection to svn://repo/repo1/branches/
Checking directory /branches@HEAD
[Wed Aug 07 05:43:29 UTC 2024] Finished branch indexing. Indexing took 0.12 sec
Finished: SUCCESS
environment
4.462<br/>
subversion 1269.v53185011cd9f
All included branches are being scanned for a Jenkinsfile for each included pattern. In production, the same branch is being scanned 32 times, resulting in an execution time of 30 seconds for the multibranch scan, rather than 1 second. We have 16 included patterns.
Project repository base: svn://repo/repo1
Include branches: branches/TeamA-, branches/BUG-
Example output (a test repo with only a couple of branches):
Originally reported by
pwiseman, imported from: Subversion include branches are scanned too many times
Raw content of original issue
environment