Given that the vagrant portion of the project is there primarily to support providing a local testing environment for Mac and Windows users, and that it isn't needed or used on Linux builds (including the production testbots), it seems to me that it would make sense to split the vagrant-related files into their own project ... Those who need it can be directed to download it instead of drupalci_testbot, and the vagrant instructions can then pull in the most current version of the drupalci_testbot project via the scripts.

Comments

jthorson created an issue. See original summary.

Mile23’s picture

The vagrant stuff supports the project, not the other way around. :-)

So -1.

Mixologic’s picture

Component: Code » Vagrant/Local Testing

One thing that might be nice, however, is to somehow unify the host environment that gets built for the drupalci aws slaves (https://drupal.org/project/drupalci_jenkins), and the host environment that gets created for the vagrant box.

Mile23’s picture

Title: Strip out the vagrant portion of the project into a dedicated 'drupalci_vagrant' project » Unify AWS host environment with vagrant/dev environment
Mixologic’s picture

Mixologic’s picture

Status: Active » Fixed

Say, this got donezo.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.