Closed
Bug 507961
Opened 15 years ago
Closed 15 years ago
Disable partner repack in 3.0.x release automation
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nthomas, Assigned: nthomas)
References
Details
Attachments
(1 file)
5.01 KB,
patch
|
coop
:
review+
nthomas
:
checked-in+
|
Details | Diff | Splinter Review |
Now that Firefox 3.5 has shipped the partner repacks based on 3.0.x are no longer required. We should remove the buildbot config for calling the repacking code in Bootstrap.
Assignee | ||
Comment 1•15 years ago
|
||
This should do the trick.
Updated•15 years ago
|
Attachment #392204 -
Flags: review?(ccooper) → review+
Comment 2•15 years ago
|
||
agreed that 3.0.x should be disabled and that this makes sense.
Assignee | ||
Updated•15 years ago
|
Attachment #392204 -
Flags: checked-in+
Assignee | ||
Comment 3•15 years ago
|
||
Comment on attachment 392204 [details] [diff] [review] staging and production buildbot config Checking in production-1.9/master.cfg; /cvsroot/mozilla/tools/buildbot-configs/automation/production-1.9/master.cfg,v <-- master.cfg new revision: 1.56; previous revision: 1.55 done Checking in staging-1.9/master.cfg; /cvsroot/mozilla/tools/buildbot-configs/automation/staging-1.9/master.cfg,v <-- master.cfg new revision: 1.55; previous revision: 1.54 done
Assignee | ||
Comment 4•15 years ago
|
||
Both production and staging masters reconfig'd.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•