At DrupalCon, cloning D8 is taking about 10 mins. So building the project is timing out. Instead, the idea is to clone Drupal locally, and then just copy it in place with the script. This git repo can be used by all three blueprints, and just switch between branches, depending on the blueprint.

Comments

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
commented

Note: there's the potential to use the Drupal 8.x blueprint to help in the Core sprint here at DrupalCon on Friday.

kostajh’s picture

kostajh commented

Probably most/many people using Drupal-up will already have Drupal cloned locally with their own feature branches, patch files, etc, so I think it would be better to have something like this:

  1. Add an option to specify the path to where Drupal is cloned on one's local machine (this could be set in a user's drushrc.php file so you don't have to type it out each time you run drush vb), e.g. --drupal-source=/path/to/drupal/repo
  2. When building a VM using the D6/7/8 blueprint, check to see if drupal-source is a valid Drupal repo and if so, the install.sh script can use that during the build process to mount it as a shared folder in the docroot for the VM
  3. If drupal-source is not valid, then we could clone Drupal locally

Another advantage to having a drupal-source option is that it's easier to use a D8 initiative sandbox for building up a VM, you should just adjust the drupal-source path to where you have the initiative sandbox checked out and you're ready to go.

Edit: If we went this route, we would also need to take #1741276: Add option for --docroot to mount as a NFS shared folder into consideration