Closed
Bug 745968
Opened 13 years ago
Closed 9 years ago
Pulse notifications for l10n beta candidate builds should include 'l10n' instead of 'repack'
Categories
(Release Engineering :: Release Automation, defect, P3)
Release Engineering
Release Automation
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: whimboo, Unassigned)
References
Details
Recently I have setup our Mozmill CI system to run the BFT tests against beta candidate builds of Firefox. This works fine for en-US builds by watching the 'release-mozilla-beta' branch.
What I have noticed is that I don't get any notification for localized beta candidate builds. Those notification should be send out for the same branch like the en-US builds.
Comment 1•13 years ago
|
||
we are sending out the notifications for release repacks, they're just structured differently.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 2•13 years ago
|
||
As talked with Chris on IRC a change from 'repack' to 'l10n' should be possible. But it's probably not a good idea to make this change now. We should wait until separate notifications can be send out by the repack machines for each individual locale. I will file this bug shortly.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Summary: Missing Pulse notification for l10n beta candidate builds → Pulse notifications for l10n beta candidate builds should include 'l10n' instead of 'repack'
Comment 3•13 years ago
|
||
This probably means renaming the builders. I suspect this is a low risk change that would involve:
* String changes in a few places:
** https://github.com/mozilla/buildbotcustom/blob/6901146c9d3349772a9f9b175a91974af4ebb102/process/release.py#L271
** https://github.com/mozilla/buildbotcustom/blob/6901146c9d3349772a9f9b175a91974af4ebb102/process/release.py#L714
** https://github.com/mozilla/buildbotcustom/blob/6901146c9d3349772a9f9b175a91974af4ebb102/process/release.py#L753
** https://github.com/mozilla/buildbotcustom/blob/6901146c9d3349772a9f9b175a91974af4ebb102/process/release.py#L774
** https://github.com/mozilla/buildbotcustom/blob/6901146c9d3349772a9f9b175a91974af4ebb102/process/release.py#L1652
I think that's it, but it would need a test in staging before we can land it.
In any case, this isn't high priority.
Priority: -- → P3
Updated•12 years ago
|
Assignee: nobody → sbruno
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Comment 4•11 years ago
|
||
The plan is to work on this next week (16-20 September).
Updated•11 years ago
|
Assignee: sbruno → nobody
Comment 5•10 years ago
|
||
We might get this for free with release promotion.
Blocks: release-promotion
Reporter | ||
Comment 7•9 years ago
|
||
I feel that we are stuck with the repack term also in release promotion. So lets keep it and don't worry about this minor thing.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 9 years ago
Flags: needinfo?(hskupin)
Resolution: --- → WONTFIX
Comment 8•9 years ago
|
||
Thank you!
You need to log in
before you can comment on or make changes to this bug.
Description
•