Closed Bug 730251 Opened 13 years ago Closed 13 years ago

Prepare for domain change of l10n dashboard, possible redirects

Categories

(Release Engineering :: General, defect, P4)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Pike, Assigned: armenzg)

References

Details

(Whiteboard: waiting on dependent bug)

Attachments

(1 file)

We're going to claim the l10n.mozilla.org domain for the dashboard soon, and would ask you to verify what works and what needs to change in the release automation for that. l10n-stage-sj.m.o is likely going to redirect once we take the new domain, so the existing links don't break immediately, but I don't know if all customers of the dashboard URLs properly follow redirects? Also, once we have the new domain, we should switch the links over to l10n.m.o so that we can rip out the redirects of the old domain after the transition period.
We have two parts: 1) grab changesets manually from the dashboard 2) before kicking the release we have a script that compares data on the dashboard with what we grabbed from #1 (just in case) What would a URL like this look like? https://l10n-stage-sj.mozilla.org/shipping/l10n-changesets?ms=fx11_beta_b4 Once you have the new domain up we can switch our documentation and our scripts.
https://l10n.mozilla.org/shipping/l10n-changesets?ms=fx11_beta_b4 would be the new url. Just the host name changes.
It redirects to https://l10n.mozilla-community.org should we use that? or would the redirection from l10n.m.o to l10n.m-c.o work?
Assignee: nobody → armenzg
Status: NEW → ASSIGNED
Attachment #602026 - Flags: review?(rail)
Attachment #602026 - Flags: review?(l10n)
(In reply to Armen Zambrano G. [:armenzg] - Release Engineer from comment #3) > It redirects to https://l10n.mozilla-community.org should we use that? or > would the redirection from l10n.m.o to l10n.m-c.o work? This is just for the transition phase. Once elmo takes over l10n.m.o, it won't redirect.
Filed bug 732092 to have a tracker of the elmo side to block this one. We shouldn't land the changes here before we did the upstream changes to elmo. Do you guys need a particular heads-up notice, and what's the timing of landing a change like this?
Depends on: 732092
Comment on attachment 602026 [details] [diff] [review] change L10n dahsboard url Review of attachment 602026 [details] [diff] [review]: ----------------------------------------------------------------- This looks good from the URL POV, but there's a chunk in this patch I find surprising. Leaving that up for Rail's review. Also, see my previous comments, this shouldn't land before we're through with the upstream change of elmo actually serving the content on l10n.m.o. ::: buildfarm/maintenance/manage_masters.py @@ +69,5 @@ > masters.append(m) > elif m['role'] in options.roles: > masters.append(m) > + elif len(options.roles) == 1 and m["name"].endswith(options.roles[0]): > + masters.append(m) is this part of this patch?
Attachment #602026 - Flags: review?(l10n) → review+
That wasn't part of the patch. We need this just before it goes live or soon after. We normally trigger a release on Tuesday night/ Wednesday morning.
Comment on attachment 602026 [details] [diff] [review] change L10n dahsboard url r+ for the first hunk.
Attachment #602026 - Flags: review?(rail) → review+
Priority: -- → P4
Whiteboard: waiting on dependent bug
When can we land this?
We're ready on the l10-dashboard side.
Comment on attachment 602026 [details] [diff] [review] change L10n dahsboard url tools repo: 589d386799d9
Attachment #602026 - Flags: checked-in+
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: