-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Speeding up provisioning #4
Comments
You can export the provisioned VM as a new |
Awesome! Is this
? |
Just |
I've packaged a vanilla provisioned vagrant box. Any idea of the simplest way to use this to create new |
just declare it as the base in your vagrantfile. |
Hm, I imagine we don't want to add or replace the stuff in the virtual machines github repo, but instead want to use local Jenkins scripts to do this. Maybe I can script something like this:
and this could do the trick. |
What do we need to resolve Is this issue? We now use |
I'm not 100% sure about this, but I think you want to export the box, after provisioning, as a fixed image. Then for each run, you should create a fresh VM from that image. This is safer than |
This is exactly what we want to do. I think we want to have the |
It takes a long time to provision these VMs over the network, so I am thinking we either need to either (1) locally share already-provisioned Vagrant boxes, or (2) set up a local mirror for
yum
to use.The text was updated successfully, but these errors were encountered: