Closed
Bug 537329
Opened 15 years ago
Closed 15 years ago
SeaMonkey L10n repacks not triggered daily
Categories
(SeaMonkey :: Release Engineering, defect)
SeaMonkey
Release Engineering
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kairo, Assigned: kairo)
References
Details
Since the update of our SeaMonkey build infrastructure, we only get L10n builds triggered by L10n commits, but not daily. I need to try and correct that - maybe even together with getting some part or all of L10n updates working.
Assignee | ||
Comment 1•15 years ago
|
||
I refactored the whole buildbot config for SeaMonkey after the current Firefox config in bug 539780 which includes some larger internal changes wrt L10n, let's see if that helped with that as well - ideally, trunk should even gain L10n nightly updates with that.
Assignee | ||
Comment 2•15 years ago
|
||
Builds have now been triggered correctly, but a change from bug 531275 busted our repackaging process. I'll undo it locally on the SeaMonkey build master for now.
Assignee | ||
Comment 3•15 years ago
|
||
After applying the bug 539780 work, builds have been triggered again correctly, but I needed to undo some wrong changes to buildbotcustom, see bug 531275 comment #100 and found that a comm-central bug still causes L10n nightly updates to not work, so I deactivated them again and filed bug 539938 for that. The regular cycles that ran today were all broken, but some test cycles on de went green now, and further builds should get triggered correctly, so this bug is fixed, further issues get tracked in the mentioned other bugs.
Assignee | ||
Updated•14 years ago
|
Component: Project Organization → Release Engineering
Assignee | ||
Updated•14 years ago
|
QA Contact: organization → release
You need to log in
before you can comment on or make changes to this bug.
Description
•