Use Github instead of Mozilla SVN server as source for localization on Bedrock (dev, demo, stage, production)

RESOLVED FIXED

Status

www.mozilla.org
Bedrock
RESOLVED FIXED
3 years ago
2 years ago

People

(Reporter: pascalc, Assigned: pmac)

Tracking

Development/Staging

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
The localizations currently live in:

www-dev.allizom.org
https://svn.mozilla.org/projects/mozilla.com/trunk/locales/

www.allizom.org
https://svn.mozilla.org/projects/mozilla.com/tags/stage/locales/

www.mozilla.org
https://svn.mozilla.org/projects/mozilla.com/tags/production/locales/

That repo is included into bedrock in a 'locale' folder:
http://bedrock.readthedocs.org/en/latest/l10n.html#localization

We are going to move the translations to Github and have imported the repository from svn (trunk) to this new repository:
https://github.com/mozilla-l10n/www.mozilla.org

This is the repository where localizers will work (for the moment, we only keep it synced with svn).

L10n-drivers will maintain a separate repo for production files as we don't want localizers to be able to commit to production directly.

The url of this production repo where we will copy the data will be:
https://github.com/mozilla-l10n/bedrock-l10n

I would like to make sure that everything works with a real test on mozilla infrastructure using the new repo, so basically I would like a test server to be set up and reflecting bedrock master branch with the l10n repository from github and not our own svn repository.

I think that just doing this inside the bedrock repository should work:
git clone https://github.com/mozilla-l10n/www.mozilla.org locale

Another option is to use Github svn bridge:
svn co https://github.com/mozilla-l10n/www.mozilla.org/trunk locale

I don't know what option is best and I think it doesn't impact l10n so the choice is yours.

Thanks.
Great! I'll convert one of the demo servers and see how it goes. Using git should be no problem, it's just a matter of updating all of our update scripts to do the git thing instead of the svn thing.
Assignee: nobody → pmac
Status: NEW → ASSIGNED

Comment 2

3 years ago
Commits pushed to master at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/673d66657a426b61d0b512a1a254f8c86d8d0f44
Fix bug 1210368: Update dev to use locales from git.

https://github.com/mozilla/bedrock/commit/df9da60fed2aaf86fa606d7553ca45a7992f34db
Merge pull request #3377 from pmclanahan/get-locales-from-git-1210368

Fix bug 1210368: Update dev to use locales from git.

Updated

3 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED

Comment 3

3 years ago
Commit pushed to master at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/03fd9071f75d581804940862438626bf39627cdf
Revert "Fix bug 1210368: Update dev to use locales from git."

This reverts commit 673d66657a426b61d0b512a1a254f8c86d8d0f44.
I jumped the gun a bit on this, but flod caught it and we reverted the change in the main repo. My impression was that the new github repo was being kept updated via some automation, but that is apparently not the case, so I can't go ahead and convert our existing dev and/or demo servers to use the github repo. But setting up a new environment on our legacy infrastructure (non AWS) is just not something that's going to happen. WebOps just doesn't have the resources. So even though we had to revert the change we did get a successful test of deployment to www-dev.a.o done. So I'm confident we'll be ready whenever you are to use the new git repo on that infrastructure.

I'll also add a kanban card to our board for setting up an instance of bedrock using the github locale files on our new AWS infrastructure so that we can be sure that will work. I'm quite confident it will, but it will be good to have the work done in advance.

My main question after all of this is what your timeline is for transitioning l10n activity from svn to git? Should I get started on the new infra work soon, or will it take weeks?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Reporter)

Comment 5

3 years ago
pmac and myself chatted on IRC, on the l10n side, all our internal tools are ready for the switch as well as Transvision, our translation memory. Pontoon our in-house translation platform can switch this Thursday and Locamotion, an external platform we also work with can make the switch probably on Friday.

So basically, we are technically ready for a move to GitHub for dev environments this week, and we could do a switch for production next week.

Comment 6

3 years ago
Commits pushed to master at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/7622cbdd43a3ec78db40b3312cd60ed92f47d4ac
Bug 1210368: Use git-based locale data on dev/demo servers

https://github.com/mozilla/bedrock/commit/effd9df565e3c6bb51b42c5ceca88f1a4a6415f1
Merge pull request #3418 from pmclanahan/do-git-locales-again

Bug 1210368: Use git-based locale data on dev/demo servers
This is done on www-dev and www-demo*. Will get started on stage and prod on Monday unless there's a holdup w/ the prod git repo.

Comment 8

3 years ago
Commits pushed to master at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/6ff0abdf29c679b27aa0c0648349848395c3d54a
Bug 1210368: Convert legacy infra from svn to git for locales.

https://github.com/mozilla/bedrock/commit/0744c5075c918be61b80c3afe6c99371ffd69d9c
Merge pull request #3421 from pmclanahan/l10n-git-prod

Bug 1210368: Convert legacy infra from svn to git for locales.

Comment 9

2 years ago
Is this fixed?
Yep. Also amending the subject to reflect reality.
Status: REOPENED → RESOLVED
Last Resolved: 3 years ago2 years ago
Resolution: --- → FIXED
Summary: Set up a bedrock test server using the l10n repo from Github instead of mozilla svn server → Use Github instead of Mozilla SVN server as source for localization on Bedrock (dev, demo, stage, production)
You need to log in before you can comment on or make changes to this bug.