Re:A Better Development Workflow with Vagrant
by brokenparser on Tuesday April 16, 2013 @03:37PM
(#5560323)
Of course, but if you do that please also use a CI tool (such as Jenkins) to ensure the Vagrantfile stays valid. It's actually good to rebuild that VM regularly, especially when it's almost time to deploy.
[ Parent
| on HN ]
Re:A Better Development Workflow with Vagrant
by mateuszf on Wednesday April 17, 2013 @02:23AM
(#5563008)
I haven't done it myself, but I've heard that the same effect (clean starting point) can be achieved with snapshots and restores without the waiting time - it is supposed to work very fast.
Re:A Better Development Workflow with Vagrant
by zjmichen on Tuesday April 16, 2013 @03:41PM
(#5560347)
Yeah, close to deploy is different. What does a CI tool do in this case? I'm somewhat unfamiliar with the concept.
Re:A Better Development Workflow with Vagrant
by jmcqk6 on Tuesday April 16, 2013 @06:35PM
(#5561404)
If you run your tests in a pristine and isolated environment, then you can be more confident in the lack of side-effects.
Basically, by integrating this into your CI tool, you ensure that all your tests / deploys run through a standardized and pristine environment.