[JIRA] (JENKINS-53951) withMaven fail to set maven path when global variable is set
Title: Message Title
Bernardo Vale commented on JENKINS-53951
Re: withMaven fail to set maven path when global variable is set
Output attached. Executed with:
sh "env"
echo " with Maven ="
withMaven(jdk: 'JDK-8', maven: 'maven_3.5.3') {
sh "mvn help:system"
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53951) withMaven fail to set maven path when global variable is set
Title: Message Title Bernardo Vale updated an issue Jenkins / JENKINS-53951 withMaven fail to set maven path when global variable is set Change By: Bernardo Vale Attachment: withmaven.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53951) withMaven fail to set maven path when global variable is set
Title: Message Title Bernardo Vale updated an issue Jenkins / JENKINS-53951 withMaven fail to set maven path when global variable is set Change By: Bernardo Vale If there's a global variable defining a path to maven /bin . Pipeline integration fails to setup the request requested 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 +MAVEN =/path/to/maven/3.5.3 /bin 3. Create a pipeline that uses withMaven step selecting maven 3.5.4Run sh "mvn --version"We expect it to show selected version 3.5.4 but it will show 3.5.3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53951) withMaven fail to set maven path when global variable is set
Title: Message Title Bernardo Vale created an issue Jenkins / JENKINS-53951 withMaven fail to set maven path when global variable is set Issue Type: Bug Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2018-10-08 21:14 Environment: Jenkins ver. 2.107.3 Priority: Minor Reporter: Bernardo Vale 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 Add Comment
