-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins ver. 2.107.3
If there's a global variable defining a path to maven/bin. Pipeline integration fails to setup the requested maven tool.
*Steps to Reproduce*
1. Install two maven versions, say 3.5.3 and 3.5.4
2. Define a global variable PATH+MAVEN=/path/to/maven/3.5.3/bin
3. Create a pipeline that uses withMaven step selecting maven 3.5.4
Run sh "mvn --version"
We expect it to show selected version 3.5.4 but it will show 3.5.3
[JENKINS-53951] withMaven fail to set maven path when global variable is set
Description |
Original:
If there's a global variable defining a path to maven. Pipeline integration fails to setup the request maven tool. **Steps to Reproduce** 1. Install two maven versions, say 3.5.3 and 3.5.4 2. Define a global variable MAVEN+PATH=/path/to/maven/3.5.3 3. Create a pipeline that uses withMaven step selecting maven 3.5.4 Run sh "mvn --version" We expect it to show selected version 3.5.4 but it will show 3.5.3 |
New:
If there's a global variable defining a path to maven/bin. Pipeline integration fails to setup the requested maven tool. **Steps to Reproduce** 1. Install two maven versions, say 3.5.3 and 3.5.4 2. Define a global variable PATH+MAVEN=/path/to/maven/3.5.3/bin 3. Create a pipeline that uses withMaven step selecting maven 3.5.4 Run sh "mvn --version" We expect it to show selected version 3.5.4 but it will show 3.5.3 |
Assignee | Original: Alvaro Lobato [ alobato ] | New: Cyrille Le Clerc [ cleclerc ] |
Attachment | New: withmaven.txt [ 44738 ] |
Assignee | Original: Cyrille Le Clerc [ cleclerc ] |