Has anyone faced the same issue before? Can you please guide me.
I am encountering below exception when I try to run a build on one of our Jenkins Slaves, the same Job succeeds if i tie it to our Jenkins Master or If I execute the Mvn sonar Command(in Bold below) from the cehcked-out workspace on slave node or I add a goal mvn sonar:sonar along with mvn clean deploy in my build steps.
[Services-Address] $ mvn -f /home/jenkinspan/workspace/
From the Look of it, I did verify that, the Maven PATH's are correct on both Slave and Master.
I added the command echo $PATH before the build commences.
have you tried to execute the same command on the command line?
- login to the slave (e.g. ssh) as the same user as the Jenkins slave is running with
- change to the same directory
- execute the mvn command
- was the same workspace used by a different Jenkins before?
- did you change the user the slave is running with
On 15.07.2012, at 03:46, krishna kurnala wrote:
yes. the same command works when i go to the directory run in the slave node or when i disable sonar plugin and add the step mvn sonar:sonar in the Build Job.
No, the workspace was NOT used by another user nor did i change the user.
Thanks for your time. Still scratching my Head.
On Sun, Jul 15, 2012 at 12:35 AM, domi <[hidden email]> wrote:
|Powered by Nabble||Edit this page|