1266055 - L10n deploy should not depend on the Kitsune code deploy

Status: RESOLVED FIXED

(support.mozilla.org :: Localization, task, P4)

Description

[Michal Stanke (Mozilla.cz) [:mstanke][:MikkCZ]]

I think the localizers should not depend on the Kitsune deploy (this is mostly visible when Kitsune development has stopped now). We have some update to the UI strings, but they won't appear until the next deploy happen. This also applies to new strings - in the current flow they appear in the repository after the Nth deploy, but their translations won't appear in production until the next deploy (N+1).

To prevent this in the future and give localizers an opportunity to push new translation to production without waiting for the N+1 deploy, I propose to setup an automated l10n-only deploy at least once a week.

Comment 1

[vesper]

If this can be set up in a safe way that doesn't break anything upon problems that could pop up here https://postatus.herokuapp.com/p/SUMO/postatus (or in any other deploy-breaking place, for that matter), I'm all for that.

Comment 2

[vesper]

Cleaning up before the migration. This will not be relevant to the new platform.

Comment 3

[Tim Casey]

Reopening now that we've moved back to Kitsune for the time being.

Comment 4

[vesper]

Hi Giorgos,

Per your estimate, how hard would it be to automate the process you're taking care of right now for us? (and thank you for that!)

Do you think there are any technical blockers for this process to be automated?

Alternatively, if that's not a bother (and the automation is hard), having someone do it manually (I can do it if I get instructions I am able to follow) is definitely a feasible workaround at this stage.

Comment 5

[Giorgos Logiotatidis [:giorgos]]

This is a nice thing to have. With the current deployment process we can't automate reasonably. When we move to AWS and to docker / k8s deployments this can be automated along with the required automated testing and rollback plans. 

 I'll continue to manually update strings every Monday for the foreseeable future. (Heads up: not for the next 2 mondays though)

Comment 6

[Michal Stanke (Mozilla.cz) [:mstanke][:MikkCZ]]

Hi Giorgos.

If you can push the localization updates regularly even if there are no changes to the code, I would consider this as fixed. The original issue was mostly about a long time for newly translated strings to reach production. Feel free to reach out to me about the scripts in bug 1271132 when you want to start with the regular deploys. Just note in two weeks I may be off for a few days. :/

Comment 7

[Giorgos Logiotatidis [:giorgos]]

Hi Michal, 

As I mentioned in #5 I plan to continue manually pushing every Monday.