Closed
Bug 763029
Opened 12 years ago
Closed 12 years ago
Please use product-details to update bedrock download links for 15.0a2
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task, P1)
Infrastructure & Operations Graveyard
WebOps: Other
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: akeybl, Assigned: afernandez)
References
Details
Same needs to happen for the 15.0a2 push. I pushed revisions 106147 and 106150 to mozilla.com, but haven't seen the links update yet. https://www.mozilla.org/en-US/firefox/channel/#aurora +++ This bug was initially created as a clone of Bug #759577 +++ I just pushed the latest beta product-details for FF13 beta 6. I believe we need to manually run the update of the bedrock download links. +++ This bug was initially created as a clone of Bug #759564 +++ Please use product-details to update bedrock download links regularly. This will prevent us from needing to request that links are updated whenever we release a new version of Firefox or Fennec. This cron job should happen very regularly - as regularly as production rollouts upon checkin (once every ~15min). James should have more details if necessary.
Reporter | ||
Updated•12 years ago
|
Priority: -- → P1
Reporter | ||
Updated•12 years ago
|
Severity: normal → blocker
Reporter | ||
Comment 1•12 years ago
|
||
Given https://bugzilla.mozilla.org/show_bug.cgi?id=759564#c14 this may fix itself in the next 15min.
Assignee | ||
Comment 2•12 years ago
|
||
I pushed manually, see http://www.mozilla.org/media/product_details_finished.txt
Assignee: server-ops → afernandez
Reporter | ||
Comment 3•12 years ago
|
||
https://www.mozilla.org/en-US/firefox/channel/#aurora still does not appear to be updated.
Assignee | ||
Comment 4•12 years ago
|
||
It's showing up correctly now. The web team will correct any discrepancies in the previous cron (bug 759564).
Assignee | ||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 5•12 years ago
|
||
Due to the code which reads the .json files needing to be reloaded to notice the files are updated, a full site push was actually run to get live. I confirmed with :jlongster no changes to master were pushed that would cause any issues. Further discussion on the final resolution of this work flow is happening on bug 759564
Updated•11 years ago
|
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•