Closed
Bug 1343700
Opened 8 years ago
Closed 8 years ago
Linux desktop staging 53b1 on jamun
Categories
(Release Engineering :: Release Automation, enhancement, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: coop, Assigned: rail)
References
Details
Some of the generic work for this is already done, or is being tracking as part of bug 1343393.
This bug covers the desktop-specific pieces to run staging nightlies for Linux32 and Linux64.
Reporter | ||
Updated•8 years ago
|
Assignee: nobody → rail
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•8 years ago
|
||
Yesterday I ran a more or less successful staging release \o/
https://tools.taskcluster.net/task-group-inspector/#/-j02D7c1SRSl2Bh-5Gp19A
https://ftp.stage.mozaws.net/pub/firefox/candidates/53.0b1-candidates/build5/
I manually resolved the following tasks:
* updates: it requires more tweaking for a staging release, but I'm not worried about this builder, it's unaffected by the TC migration
* snap generation: the failure has been fixed and requires an extra rebase of my branch. not worried at all
* bouncer submission: never worked as expected in staging, meh
The rest is not that important:
* update verification depends on the updates builder
* snap deps don't block a release nor automation in any way
Assignee | ||
Updated•8 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•