Closed
Bug 666407
Opened 10 years ago
Closed 10 years ago
Turn off 3.5 builds
Categories
(Release Engineering :: General, defect, P3)
Release Engineering
General
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: catlee, Assigned: catlee)
References
()
Details
(Whiteboard: [capacity][EOL])
Attachments
(1 file, 1 obsolete file)
20.03 KB,
patch
|
catlee
:
review+
catlee
:
checked-in+
|
Details | Diff | Splinter Review |
Firefox 3.5 is EOLed. Once we get the o.k. from the powers-that-be, let's turn off nightlies, per-checkin builds, repacks and tests in our configs.
Comment 1•10 years ago
|
||
And geriatric?
Comment 2•10 years ago
|
||
those will stop when the builds stop. I dont see any reason to touch the geriatric master to remove a branch that isn't causing much load anyway.
Comment 3•10 years ago
|
||
Agreed - I meant killing the master and slaves. So this bug is just to stop the day-to-day builds, but retains capacity for releases?
Updated•10 years ago
|
Priority: -- → P3
Whiteboard: [capacity][EOL]
Comment 4•10 years ago
|
||
Announced in today's MozillaFoundation, and last week's platform meeting. http://oduinn.com/blog/2011/06/27/stopping-firefox-3-5/
Comment 5•10 years ago
|
||
(In reply to comment #3) > Agreed - I meant killing the master and slaves. So this bug is just to stop > the day-to-day builds, but retains capacity for releases? Not quite. This stops *all* builds, including build-on-checkin, nightly builds and release builds. See details here: http://oduinn.com/blog/2011/06/27/stopping-firefox-3-5/ (In reply to comment #1) > And geriatric? (In reply to comment #2) > those will stop when the builds stop. I dont see any reason to touch the > geriatric master to remove a branch that isn't causing much load anyway. We need to keep geriatric master around until all the PPC and nonSSE2 needs go away. FF3.5 reduces, but does not eliminate, all jobs to geriatric master.
Comment 6•10 years ago
|
||
(In reply to comment #5) > (In reply to comment #1) > > And geriatric? > > (In reply to comment #2) > > those will stop when the builds stop. I dont see any reason to touch the > > geriatric master to remove a branch that isn't causing much load anyway. > We need to keep geriatric master around until all the PPC and nonSSE2 needs > go away. FF3.5 reduces, but does not eliminate, all jobs to geriatric master. Which by my interpretation of our system requirements page, is when we EOL Firefox 3.6. ftr, the reason I have to interpret the sysreqs is that "recommended" is used to describe which CPUs our binaries support for Mac. As we don't actually produce PPC binaries for 4.0, and Intel CPU is only a recommendation for 4.0, I think its reasonable to assert that those recommendations are in fact requirements. http://www.mozilla.com/en-US/firefox/system-requirements.html Windows <snip> Recommended Hardware <snip> Pentium 4 or newer processor that supports SSE2 <snip> Mac <snip> Recommended Hardware Macintosh computer with an Intel x86 processor <snip>
Updated•10 years ago
|
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → catlee
Assignee | ||
Comment 7•10 years ago
|
||
We need to keep mozilla-1.9.1 alive on the build side of things so we can generate refreshed MUs for it.
Attachment #542576 -
Flags: review?(nrthomas)
Attachment #542576 -
Flags: review?(bhearsum)
Comment 8•10 years ago
|
||
Comment on attachment 542576 [details] [diff] [review] Turn off mozilla-1.9.1 Review of attachment 542576 [details] [diff] [review]: -----------------------------------------------------------------
Attachment #542576 -
Flags: review?(nrthomas) → review+
Comment 9•10 years ago
|
||
Comment on attachment 542576 [details] [diff] [review] Turn off mozilla-1.9.1 Whoops, used the wrong field.
Attachment #542576 -
Flags: review?(bhearsum) → review?(nrthomas)
Comment 10•10 years ago
|
||
Comment on attachment 542576 [details] [diff] [review] Turn off mozilla-1.9.1 There's also a 1.9.1 reference in mozilla-tests/production_config.py in BRANCHES that can go.
Attachment #542576 -
Flags: review?(nrthomas) → review+
Assignee | ||
Comment 11•10 years ago
|
||
carrying forward r+ this has mozilla-1.9.1 references removed from master_common.py and mozilla-tests/production_config.py
Attachment #542576 -
Attachment is obsolete: true
Attachment #542872 -
Flags: review+
Assignee | ||
Updated•10 years ago
|
Attachment #542872 -
Flags: checked-in+
Comment 12•10 years ago
|
||
This went into production on July 30th. I've removed the latest from firefox/nightly on ftp: latest-mozilla-1.9.1 latest-mozilla-1.9.1-l10n latest-firefox-3.5.x (symlink) latest-firefox-3.5.x-l10n (symlink) And emptied the nightly check files Firefox_mozilla-1.9.1.txt XULRunner_mozilla-1.9.1.txt in at cvs mozilla/tools/tinderbox-configs/monitoring/ Also removed firefox/tinderbox-builds/mozilla-1.9.1*.
Assignee | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 13•10 years ago
|
||
VERIFIED. When I looked for the Fx mozilla-1.9.1 yesterday (well, earlier today by Mountain View clocks), they were nowhere to be found: the latest-mozilla-1.9.1 and -l10n directories have now disappeared.
Status: RESOLVED → VERIFIED
Updated•8 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•