Change By: Jesse Bowes (07/Jan/15 8:08 PM)
Description: Under the Boot Up Vagrant VM task, specifying a relative path to the Vagrantfile doesnt work.

Tried: 
./Vagrantfile and Vagrantfile

It appears as though 'vagrant up' tries to execute in /

leaving the field empty gives a stack trace:

java.lang.NullPointerException
at java.util.regex.Matcher.getTextLength(Matcher.java:1234)
at java.util.regex.Matcher.reset(Matcher.java:308)
at java.util.regex.Matcher.<init>(Matcher.java:228)
at java.util.regex.Pattern.matcher(Pattern.java:1088)
at hudson.FilePath.normalize(FilePath.java:285)
at hudson.FilePath.<init>(FilePath.java:230)
at org.jenkinsci.plugins.vagrant.VagrantWrapper.parseVagrantEnvironment(VagrantWrapper.java:107)
at org.jenkinsci.plugins.vagrant.VagrantWrapper.validate(VagrantWrapper.java:184)
at org.jenkinsci.plugins.vagrant.VagrantWrapper.executeCommand(VagrantWrapper.java:133)
at org.jenkinsci.plugins.vagrant.VagrantUpCommand.perform(VagrantUpCommand.java:101)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)
at hudson.model.Build$BuildExecution.build(Build.java:199)
at hudson.model.Build$BuildExecution.doRun(Build.java:160)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533)
at hudson.model.Run.execute(Run.java:1745)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)

I can fix this by using the full path (/var/lib/jenkins/jobs/project/workspace/Vagrantfile), but it's not ideal
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to