Re-imaging a drupal.org development environment

Last updated January 30, 2013.

If a developer requests to have their Drupal.org development environment re-imaged, here is the process.

Note: This will destroy everything in the development environment! Make sure the requesting user has back ups.

1. First, connect to Jenkins.
2. Run the destroy_development_environment job. Enter:

   Site: drupal.org (this is the site you want to clone.)
   Name: [the part of the URL that comes before "-drupal.redesign.devdrupal.org", such as "metrics"]

   

   Be absolutely sure you type the right thing in here and don't obliterate someone else's development environment. There is no confirm, no "pass go and collect $200", the site is gone once this job runs.

3. Once this job complete, choose the deploy_development_environment job. Enter:

   Site: drupal.org (this is the site you want to clone.)
   Name: [the part of the URL that comes before "-drupal.redesign.devdrupal.org", such as "metrics". This should be named around an "initiative," rather than a person whenever possible.]
   Comment: [a description of the site and what it's for. This should reference a Drupal.org issue where changes are being discussed.]

   

   This job will take about half an hour (30 mins) to complete.

4. Post back to the issue that the request has been fulfilled, then mark it "fixed".

A note about legacy environments

If a development environment has a URL like http://davereid.redesign.devdrupal.org/ (vs. http://davereid-drupal.redesign.devdrupal.org/), it is one of the legacy environments set up before the destroy_development_environment was put into effect. The destroy_development_environment will fail in this case, and the Console Output will show an error along the lines of:

If this happens, destroy the environment instead with the drupal_redesign_destroy_development_environment job, then re-image it as outlined above to convert it to the new scripts.