Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
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
Comment #2
Mile23The vagrant stuff supports the project, not the other way around. :-)
So -1.
Comment #3
MixologicOne 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.
Comment #4
Mile23Comment #5
MixologicRelevant to this: #2840446: Use packer to generate the vagrant box
Comment #6
MixologicSay, this got donezo.