Closed
Bug 785767
Opened 13 years ago
Closed 13 years ago
8/27: Please disable Aurora updates in preparation for the merge
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: akeybl, Unassigned)
Details
(Whiteboard: [buildduty])
Attachments
(1 file)
|
1.40 KB,
patch
|
rail
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
Please disable Aurora updates in preparation for the merge on 8/27. We expect to re-enable Aurora updates on Friday.
Updated•13 years ago
|
Component: Release Engineering → Release Engineering: Automation (General)
QA Contact: catlee
Whiteboard: [buildduty]
Comment 1•13 years ago
|
||
Attachment #655620 -
Flags: review?(rail)
Updated•13 years ago
|
Attachment #655620 -
Flags: review?(rail) → review+
Comment 2•13 years ago
|
||
Comment on attachment 655620 [details] [diff] [review]
shunt aurora to auroratest
This landed in production already.
Attachment #655620 -
Flags: checked-in+
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 4•13 years ago
|
||
Disabled update tests for Aurora builds in Mozmill CI:
https://github.com/mozilla/mozmill-ci/commit/dd3d12ffb261a20f73377c06d7d6efb00f99aa5e
Comment 5•13 years ago
|
||
Comment on attachment 655620 [details] [diff] [review]
shunt aurora to auroratest
I don't know what happened, but this didn't make it to production yesterday. Until a few minutes ago Aurora updates were live =(. This is now checked in for real, and I'll reconfig for it in a bit.
Comment 6•13 years ago
|
||
Additional note: we need to chmod /opt/aus2/incoming/2/Firefox/mozilla-aurora to 755 when we turn them back on.
| Reporter | ||
Comment 7•13 years ago
|
||
(In reply to Ben Hearsum [:bhearsum] from comment #5)
> I don't know what happened, but this didn't make it to production yesterday.
> Until a few minutes ago Aurora updates were live =(. This is now checked in
> for real, and I'll reconfig for it in a bit.
Not the end of the world, but we'll discuss in the channel meeting how best to test in the future.
(In reply to Alex Keybl [:akeybl] from comment #7)
> Not the end of the world, but we'll discuss in the channel meeting how best
> to test in the future.
Just to get in front of this, my recommendation would be to add the VERIFYME keyword and assign me as the QA Contact in the future. It shouldn't take me more then 10-15 minutes to spotcheck a couple of platforms.
Comment 9•13 years ago
|
||
This made it to production (for real) today.
| Assignee | ||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
| Assignee | ||
Updated•7 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•