[JENKINS-23445] Can't use matrix-project with multiple-scms

On "master" task, no problem, jenkins checkout good repo and branch.

But on "slave" tasks, It checkout the same branch for all scm (git in my case).

How-to reproduce?

• create a multiconfiguration project


• Add 2 scm git
  
  
  
  • 1 for repo/branch A  (on / by default, or on dir "A", irrelevant)
  
  
  • 2 for repo/branch B and put it on dir "B"
  
  
  
  


• add configuration matrix, with one axis that can take multiple values

On slave the folders structure gets created correctly, but the second one is empty.

When checking the console output, the "master" task clones and checks out the two repos correctly (different revision numbers (long string, probably a hash) for each of the 2 repos).

Each of the "slave" tasks defined by the configuration matrix, will try to fetch and checkout the same revision number for both repos, and therefore will fail on the second one.

---
Originally reported by guilhem, imported from: Can't use matrix-project with multiple-scms

• assignee: kohsuke
  
• status: Open
  
• priority: Major
  
• component(s): matrix-project-plugin, multiple-scms-plugin
  
• resolution: Unresolved
  
• votes: 1
  
• watchers: 4
  
• imported: 2025-12-06
  

Raw content of original issue

On "master" task, no problem, jenkins checkout good repo and branch.


But on "slave" tasks, It checkout the same branch for all scm (git in my case).


How-to reproduce?



	
create a multiconfiguration project

	
Add 2 scm git

	


		
1 for repo/branch A  (on / by default, or on dir "A", irrelevant)

		
2 for repo/branch B and put it on dir "B"

	

	

	
add configuration matrix, with one axis that can take multiple values



On slave the folders structure gets created correctly, but the second one is empty.


When checking the console output, the "master" task clones and checks out the two repos correctly (different revision numbers (long string, probably a hash) for each of the 2 repos).


Each of the "slave" tasks defined by the configuration matrix, will try to fetch and checkout the same revision number for both repos, and therefore will fail on the second one.

Reproduce the configuration described: a multiconfiguration project with two Git SCMs, distinct branches or repositories, and a matrix axis with multiple values. Compare the master and slave task console output and workspace folders; done means each slave checks out the correct revision for both repositories and the second repository is populated.

Written by the indexing model from the issue text.