Export regions public json files produced by ship-it

RESOLVED FIXED

Status

Release Engineering
Applications: Shipit (backend)
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: sylvestre, Assigned: ericz)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
We have now also the region files in ship-it:
https://ship-it.mozilla.org/json/regions/list.html
(requires vpn)

Currently, we are exporting this list:
https://product-details.mozilla.org/regions/
directly from the svn, this has been implemented in bug 1225693

As we did in bug 1146897, we should have a script which will take https://ship-it.mozilla.org/json/regions/*
and present it in:
https://product-details.mozilla.org/regions/
(Reporter)

Comment 1

2 years ago
Eric, can you help with this one?

I can update list.html for something else if it helps
Flags: needinfo?(eziegenhorn)
(Reporter)

Comment 2

2 years ago
Oups, actually, just like bug 1225693, we should just checkout the git sources from here:
https://github.com/mozilla/ship-it/tree/master/kickoff/static/regions
this will be easier.
(Assignee)

Updated

2 years ago
Assignee: nobody → eziegenhorn
Flags: needinfo?(eziegenhorn)
(Reporter)

Comment 3

2 years ago
Eric, do you have an eta for this? Thanks
Flags: needinfo?(eziegenhorn)
(Reporter)

Updated

2 years ago
Blocks: 733417
(Assignee)

Comment 4

2 years ago
I'll start this today.
Flags: needinfo?(eziegenhorn)
(Assignee)

Comment 5

2 years ago
This is in place now and the cron job to update it has been updated to pull from git.  The git-fu required for that is fairly tricky though so I'd like to prove it works rather than assume.  When the repo is updated someone should check that the site reflects the changes, then we can close this out.
(Assignee)

Comment 6

2 years ago
Closing out, let me know if there are any issues with pulling updates via the cron job.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
(Reporter)

Updated

2 years ago
Blocks: 1288169
You need to log in before you can comment on or make changes to this bug.