Chip, James and I have been discussing the following workflow where Maven drives Vagrant:
1. Check from git 2. Maven builds CloudStack on the developer's workstation 3. If necessary, Maven provisions a base devcloud VM using Vagrant 4. Maven deploys the build from Step 2 into the devcloud provisioned in Step 2 Once James has the Vagrant devcloud box working, we were going to attack the Maven integration for provisioning and deployment. This approach would provide the equivalent functionality to the current deploy and rdeploy Ant tasks. Does this approach sound reasonable? -John On Oct 2, 2012, at 11:02 AM, Chip Childers <chip.child...@sungard.com> wrote: > On Fri, Sep 21, 2012 at 5:29 AM, sebgoa <run...@gmail.com> wrote: >> Hi James, >> >> I have been using devcloud and was testing the build but I never got around >> to solve the last few issues, somehow the box it created never had the xen >> kernel even though the puppet recipes seemed fine. There was also an issue >> with the root password not being set properly. There was also an issue with >> veewee not having the ubuntu 12.04.1 templates, but it seems to have been >> fixed. >> I will be happy to help you test it. >> >> -sebastien > > James and Sebastien - > > I committed a couple of fixes to the build process, specifically to > install and use mvn. I know that you guys are working on a cleaner > implementation (again, thanks), so I wanted you to be aware that the > source changed a little bit on that front. I added a script to > download and install maven 3, and modified the code compile script to > use maven for the deps download step. > > -chip > > >> On Sep 20, 2012, at 11:33 PM, James Martin wrote: >> >>> Howdy folks. Seems I sent this message to the old sourceforge list >>> earlier, if you have a duplicate, apologies (thanks to the kind soul >>> that pointed this out). >>> >>> I've been doing some work updating the devcloud puppet recipes -- >>> cleaning them up, making them at little easier to read, etc. I wanted >>> to make sure I was not duplicating anyone else's work before I >>> proceeded further. I'll submit a patch within a week or so if all is >>> good. Thanks! >>> >>> >>> -James >> >> -Sebastien Goasguen >> >> >> >> >>
