[JENKINS-21423] Matrix jobs consistently fail when run concurrently

Jenkins 1.518

We use matrix jobs for deployments and have noticed matrix jobs always fail when we disable Run each configuration sequentially. The failure appears on random hosts.

• Our jobs assemble a zip file which is SCP'd to a target host and inflated.

Problem seen and important points

• The wagon-maven-plugin:1.0-beta-4:upload step runs and appears to SCP the zip file to the target host.


• We can see the zip file in the Jenkins workspace directory for the axis.


• The zip file is not found on the target host and the deploy fails.


• The same matrix job succeeds when run sequentially.


• We see the same behavior with all matrix jobs.

Additional observations

• This problem does not appear resource-related because we can run non-matrix jobs concurrently and they succeed.


• The same bad behavior for matrix jobs occurs on single and multi-node Jenkins servers. Thus it isn't a slave problem.

---
Originally reported by sstack, imported from: Matrix jobs consistently fail when run concurrently

• status: Open
  
• priority: Major
  
• component(s): matrix-project-plugin, maven-plugin
  
• resolution: Unresolved
  
• votes: 1
  
• watchers: 3
  
• imported: 2025-12-06
  

Raw content of original issue

Jenkins 1.518

We use matrix jobs for deployments and have noticed matrix jobs always fail when we disable Run each configuration sequentially. The failure appears on random hosts.



	
Our jobs assemble a zip file which is SCP'd to a target host and inflated.



Problem seen and important points



	
The wagon-maven-plugin:1.0-beta-4:upload step runs and appears to SCP the zip file to the target host.

	
We can see the zip file in the Jenkins workspace directory for the axis.

	
The zip file is not found on the target host and the deploy fails.

	
The same matrix job succeeds when run sequentially.

	
We see the same behavior with all matrix jobs.



Additional observations



	
This problem does not appear resource-related because we can run non-matrix jobs concurrently and they succeed.

	
The same bad behavior for matrix jobs occurs on single and multi-node Jenkins servers. Thus it isn't a slave problem.

• environment: Solaris and Linux VM's

Start by reproducing a matrix job with Run each configuration sequentially disabled, comparing concurrent and sequential runs. Trace the matrix-project-plugin path around the wagon-maven-plugin:1.0-beta-4:upload step and the axis workspace, then verify that concurrent deployments reliably deliver the zip to each target host.

Written by the indexing model from the issue text.