Closed
Bug 1272390
Opened 9 years ago
Closed 9 years ago
Export regions public json files produced by ship-it
Categories
(Release Engineering :: Applications: Shipit, defect)
Release Engineering
Applications: Shipit
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Sylvestre, Assigned: ericz)
References
Details
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•9 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•9 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•9 years ago
|
Assignee: nobody → eziegenhorn
Flags: needinfo?(eziegenhorn)
Reporter | ||
Comment 3•9 years ago
|
||
Eric, do you have an eta for this? Thanks
Flags: needinfo?(eziegenhorn)
Assignee | ||
Comment 5•9 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•9 years ago
|
||
Closing out, let me know if there are any issues with pulling updates via the cron job.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Reporter | ||
Updated•9 years ago
|
Blocks: ship-it-source-of-truth
Updated•3 years ago
|
Component: Applications: ShipIt (backend) → Applications: ShipIt
You need to log in
before you can comment on or make changes to this bug.
Description
•