-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
PRODUCTION
When running a maven job at the end of execution it is looking for the wrong pom.xml file and failing. Hence it logs I/O exception.
It is supposed to archive the pom.xml in the folder for build number 35364. But it is looking for improper build folder and failing.
Jenkins version: Jenkins 2.479
Maven Integration pluginVersion3.23
Maven Info PluginVersion0.3.1
Steps to Reproduce:
1) Install Jenkins for Windows in a server
2) Create a node with the two executors
3) Label that node
4) Run jnlp command to connect the VM to the Jenkins
5) Create a Maven execution Job with required parameters
6) Configure that job to execute concurrently
7) Use source code configuration to download the repository in a folder using build number variable. So every execution will be accessing unique files and there will not be any access violation.
8) Create a multi job project and add the execution job to be executed in parallel and pass the required parameter value for each job.
9) Configure the job to run on the connected node
10) Trigger the Multi job project
Actual Result:
Multi job executes the maven execution jobs with concurrent builds on a same node. At the end of each execution job (maven job) build respective pom.xml should be archived without any issues.
Expected Result:
Multi job executes the maven execution jobs with concurrent builds on a same node. At the end of a build it tried to archive pom.xml of other build and fails.