Closed
Bug 397285
Opened 18 years ago
Closed 18 years ago
Make tinderbox locale repackaging more flexible
Categories
(Webtools Graveyard :: Tinderbox, defect)
Webtools Graveyard
Tinderbox
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kairo, Assigned: kairo)
Details
Attachments
(1 file)
|
3.32 KB,
patch
|
rhelmer
:
review+
|
Details | Diff | Splinter Review |
I know that this will be done by some buildbot stuff in the future but I hear it's not there yet, so I did a test setup for SeaMonkey locale repackaging on my private tinderbox.
I ran into two problems there:
1) It tried to report to inexisting tinderbox trees because we hardcode the tree names.
2) It stopped uploading en-US builds because it assumes we never do real builds on repackaging machines.
I applied temporary hacks to that machine's tinderbox script for the time being to work around those problems.
As I don't know if we can get separate machines for SeaMonkey locale repackaging any time soon (bug 391656), I'm pondering to set up the main SeaMonkey tinderboxen for locale repackaging as well until we have a better solution.
For this, we really should have the flexibility we need in the trunk tinderbox scripts, though, so I created a patch that:
1) Enables us to report to a different tinderbox tree [scheme] for locales
2) Only deletes the en-US build if we are not building ourself
For the currently running tinderboxen, everything should work unchanged also with the patch.
| Assignee | ||
Updated•18 years ago
|
Attachment #282038 -
Flags: review?(rhelmer)
Updated•18 years ago
|
Attachment #282038 -
Flags: review?(rhelmer) → review+
| Assignee | ||
Comment 1•18 years ago
|
||
Thanks, checked this in.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•