[JIRA] [vagrant-plugin] (JENKINS-26326) Boot up Vagrant VM not using relative path

[oleksiy.khilkev...@gmail.com (JIRA)]

Title: Message Title

Oleksii Khilkevych edited a comment on JENKINS-26326   Re: Boot up Vagrant VM not using relative path To add up, I found it seems like it tries to use different directory for each of the different build steps it provides Console output cut: { { code:java} [workspace] $ vagrant -v Vagrant 1.7.2 [ vagrant ]: Executing command :[vagrant, up, --destroy-on-error] in folder /Users/oleksii [oleksii] $ vagrant up --destroy-on-error A Vagrant environment or target machine is required to run this command. Run `vagrant init` to create a new Vagrant environment. Or, get an ID of a target machine from `vagrant global-status` to run this command on. A final option is to change to a directory with a Vagrantfile and to try again. Build step 'Boot up Vagrant VM' marked build as failure Finished: FAILURE {code } } Console output cut #2 { { code:java} [workspace] $ vagrant -v Vagrant 1.7.2 [ vagrant ]: Executing command :[vagrant, provision] in folder /Users/oleksii/Downloads [Downloads] $ vagrant provision A Vagrant environment or target machine is required to run this command. Run `vagrant init` to create a new Vagrant environment. Or, get an ID of a target machine from `vagrant global-status` to run this command on. A final option is to change to a directory with a Vagrantfile and to try again. Build step 'Provision a Vagrant VM' marked build as failure Finished: FAILURE {code } } Add Comment   This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.