Requesting Drupal.org dev site environment: GDO > D7/Commons migration

First we need to set up the system for D7 groups dev sites.

I set up http://groups.7.devdrupal.org/ as the canonical staging site for the upgrade. I haven't looked into why it is WSODing, have fun. There is a core hack that should be undone in D6 like #1540192: Remove users.access core hack. This is setup similarly to http://groups.staging.devdrupal.org/. You can get modules in BZR with the same Jenkins jobs. There is a very minimal set of modules there right now.

http://drupalcode.org/project/infrastructure.git/blob/refs/heads/master:... is the script that builds the site out from a snapshot of live D6. Anything site-specific, like migrations, can be added after elif [ "${uri}" = "groups.7.devdrupal.org" ]; then. It currently takes 4 hours. #1235638: Increase password security for *.drupal.org using phpass will knock an hour or two off that. The next build will have timestamps enabled so we know exactly what takes time. The job is http://localhost:8080/view/Groups/job/snapshot_to_groups.7.devdrupal.org/.

Finally, that site is snapshotted and sanitized for building dev sites. For those with access to util, please have a look through /var/dumps/mysql/groups_7_database_snapshot.dev-current.sql.bz2 for private user data. Add queries to http://drupalcode.org/project/infrastructure.git/blob/refs/heads/master:... to remove that data. When sanitized we can have dev sites of both D6 and D7 groups.drupal.org.

Ezra – I gave you access to create and destroy dev sites, so you can make D6 dev sites as a reference. And D7 dev sites when the snapshots are good. Documentation is at http://drupal.org/node/1903094.

See you at DrupalCon!

This issue is resolved as titled.