Upgrade to Vagrant 1.2.2 #31

New Issue

rtyler · 2018-10-29T16:49:31Z

rtyler commented

2018-10-29 16:49:31 +00:00

Author: @aberrios85 Posted at: 21.06.2013 09:35

Any chance the plugin can be upgraded to version 1.2.2 of Vagrant? Current plugin doesn't like the Vagrantfiles currently created with 1.2.2

Author: @aberrios85 Posted at: 21.06.2013 09:35 Any chance the plugin can be upgraded to version 1.2.2 of Vagrant? Current plugin doesn't like the Vagrantfiles currently created with 1.2.2

rtyler commented

2018-10-29 16:49:32 +00:00

Author: @hcguersoy Posted at: 09.08.2013 21:56

+1 for this
May the problem is that vagrant 1.2.x doesn't comes via gems anymore and has to be "installed". May there is a way to call vagrant 1.2.x via jruby?

Author: @hcguersoy Posted at: 09.08.2013 21:56 +1 for this May the problem is that vagrant 1.2.x doesn't comes via gems anymore and has to be "installed". May there is a way to call vagrant 1.2.x via jruby?

rtyler commented

2018-10-29 16:49:32 +00:00

Author: @aberrios85 Posted at: 10.08.2013 07:45

I used this fork, its works quite nicely: https://github.com/smartlogic/vagrant-plugin and forked it again locally. I'll try and upload my fork to github next week.

Author: @aberrios85 Posted at: 10.08.2013 07:45 I used this fork, its works quite nicely: https://github.com/smartlogic/vagrant-plugin and forked it again locally. I'll try and upload my fork to github next week.

rtyler commented

2018-10-29 16:49:32 +00:00

Author: @hcguersoy Posted at: 10.08.2013 14:44

Pls give'n sign here then you upload your fork.

Author: @hcguersoy Posted at: 10.08.2013 14:44 Pls give'n sign here then you upload your fork.

rtyler commented

2018-10-29 16:49:32 +00:00

Author: @drangons Posted at: 18.09.2013 11:35

+1
This would be helpful

Author: @drangons Posted at: 18.09.2013 11:35 +1 This would be helpful

rtyler commented

2018-10-29 16:49:32 +00:00

Author: @jwmarshall Posted at: 30.10.2013 19:11

Any update on this? I've tried compiling and installing @aberrios85 version of the plugin that should support 1.2.2 but it did not work for me. Furthermore I need the plugin to support for vagrant plugins and building a specific box name. Any help is appreciated!

Author: @jwmarshall Posted at: 30.10.2013 19:11 Any update on this? I've tried compiling and installing @aberrios85 version of the plugin that should support 1.2.2 but it did not work for me. Furthermore I need the plugin to support for vagrant plugins and building a specific box name. Any help is appreciated!

rtyler commented

2018-10-29 16:49:33 +00:00

Author: @hcguersoy Posted at: 30.10.2013 20:27

Hi,

now I'm using vagrant out of Jenkins with the help of the shell executor.
The only thing you have to take care is that jenkins will kill all processes started by a job. But you can override this using a "hidden feature" by setting an environment variable called "BUILD_ID".

Example:

export BUILD_ID=dontKillMe
vagrant up --no-provision
vagrant provision

This will start a VM using vagrant but don't stop it. If you have to stop the vm in an another job you have to link to the .vagrant directory of the provisioning job.

Author: @hcguersoy Posted at: 30.10.2013 20:27 Hi, now I'm using vagrant out of Jenkins with the help of the shell executor. The only thing you have to take care is that jenkins will kill all processes started by a job. But you can override this using a "hidden feature" by setting an environment variable called "BUILD_ID". Example: ``` shell export BUILD_ID=dontKillMe vagrant up --no-provision vagrant provision ``` This will start a VM using vagrant but don't stop it. If you have to stop the vm in an another job you have to link to the .vagrant directory of the provisioning job.

rtyler commented

2018-10-29 16:49:33 +00:00

Author: @jwmarshall Posted at: 30.10.2013 20:46

The problem is not that I need to vagrant boxes to stick around, the problem is that we build lots of boxes for various git-flow branches as well as all pull requests. Sometimes these boxes fail and are not stopped/destroyed properly. I'm working on a bash script that will trap the exit codes and cleanup after these types of failures. It might still require your BUILD_ID environment variable in some cases, so thank you for that bit of information.

FWIW this plugin worked great with the previous versions of jenkins and vagrant.

Author: @jwmarshall Posted at: 30.10.2013 20:46 The problem is not that I need to vagrant boxes to stick around, the problem is that we build lots of boxes for various git-flow branches as well as all pull requests. Sometimes these boxes fail and are not stopped/destroyed properly. I'm working on a bash script that will trap the exit codes and cleanup after these types of failures. It might still require your BUILD_ID environment variable in some cases, so thank you for that bit of information. FWIW this plugin worked great with the previous versions of jenkins and vagrant.

Sign in to join this conversation.

No Label

No Milestone

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: rtyler/m2release-plugin#31