-
Notifications
You must be signed in to change notification settings - Fork 45
vagrant plugin does not trigger vagrant remotely in Jenkins #16
Comments
Starting work on this now. (This message brought to you by Hub board) |
Looks like this is going to require a lot of work on the ruby-runtime to execute code properly on the slaves. Damnit. |
Putting this issue back on the back-burner. (This message brought to you by Hub board) |
@rtyler do you have an idea as to if and when this issue will be handled ? |
If should be handled eventually, unfortunately this will require a lot of work in the Ruby plugin support itself to execute Ruby code on the slaves :( |
So, last update on this was 8 months ago, has there been any progress on this? I'm still running into this issue. |
Since this is a major issue I've added it to the Vagrant plugin's page on the Jenkins wiki: |
Is anyone working on this? |
Hi, I install vagrant plugin in Jenkins and when I try to build, I am getting the below errors. Please help me to solve this issue Started by user anonymous |
Any news on this? Not very useful for only running on master... |
would love to see this resolved, any progress? |
Is there any news on when this might be fixed? |
Using a Master Slave setup with Jenkins.
Slave server hosts vagrant and VBox for creation of instant boxes.
Enabling vagrant plugin in jenkins, and pointing to Slave server for triggering vagrant boot. In the slave setup, jenkins checks out the vagrant file into the remote workspace only.
It is found that the vagrant plugin looks for a Vagrantfile in the local workspace rather than looking for it in the Slave workspace. So when this plugin is used for booting, it complains with
The text was updated successfully, but these errors were encountered: