The localize.drupal.org staging process is not as automated as I'd love it to be. Now that we have alippai approved as a google summer of code student to make great improvements to the site, we'll need a more automated process I think built based on what we have for drupal.org. Can someone help out figuring out what to clone and adapt from the Jenkins jobs, how to make the staging copy of the site functional in a more automated way, and so on?

We also need alippai bzr access, I've opened #1151694: Give alippai bzr access so he can work on localize.drupal.org for this.

Comments

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

I think the hardest task is making a script to scrub private information from the database.

You can see the existing scripts in bzr checkout bzr+ssh://YOURNAME@util.drupal.org/bzr/scripts/

alippai’s picture

alippai commented
Issue tags: +gsoc

Following thread...

drumm’s picture

drumm
he/him
Location NY, US
commented
Status: Active » Closed (duplicate)

Sorry, didn't see this issue, #1181818: Review localize database sanitization replaces it.

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Project: Drupal.org infrastructure » localize.drupal.org
Component: localize.drupal.org » Infrastructure

Moving to new queue (sorry for issue-bombing).