Closed
Bug 488372
Opened 16 years ago
Closed 16 years ago
production-master should notify talos pool of builds
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: catlee, Assigned: catlee)
References
Details
Attachments
(1 file)
1.01 KB,
patch
|
bhearsum
:
review+
catlee
:
checked-in+
|
Details | Diff | Splinter Review |
Once the new talos pool master is running, production-master should notify it of new builds. This requires a change to mozilla2/config.py in buildbot-configs, as well as another port opened in the firewall.
Assignee | ||
Updated•16 years ago
|
Assignee: nobody → catlee
Assignee | ||
Comment 1•16 years ago
|
||
Do sendchange from build masters to new talos pool masters.
I'm leaving warnings off for the sendchange to talos-master for now. Once we make the new pool live, then warnings should be enabled.
Attachment #374271 -
Flags: review?(bhearsum)
Updated•16 years ago
|
Attachment #374271 -
Flags: review?(bhearsum) → review+
Assignee | ||
Comment 2•16 years ago
|
||
Comment on attachment 374271 [details] [diff] [review]
Do sendchange from build masters to talos pool masters
changeset: 1107:b20e0ffd3830
Attachment #374271 -
Flags: checked‑in+
Assignee | ||
Comment 3•16 years ago
|
||
production-master reconfigured with this.
Assignee | ||
Comment 4•16 years ago
|
||
and new builds are showing up on talos-staging-master.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•