Closed Bug 713020 Opened 13 years ago Closed 10 years ago

manage buildbot master buildbot.tac files

Categories

(Release Engineering :: General, enhancement, P4)

Product:
Release Engineering
Component:
General
Platform:
x86
Linux
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jhford, Unassigned)

References

Details

(Whiteboard: [buildmasters][puppet])

We manage buildbot masters with puppet. We don't, however, manage the buildbot.tac file for the master. An instance where this would be great is when setting up a Tegra master. They need to have a special value for MAX_BROKER_REFS. The bug this would have been useful for, and the solution needs to not reverse behaviour from, is bug 708115.
any reason buildbot masters cannot also call into slavealloc and get their tac file from it? going to assign this to me as part of briar patch work
Assignee: nobody → bear
Whiteboard: [briarpatch]
-0 on using slavealloc for this. masters are static end points, there's not much dynamic about them. we also use puppet to manage almost everything else about them. +0 or +1 if you want to integrate with production-masters.json somehow, be it with slavealloc or puppet
Blocks: 729548
Blocks: 786712
Assignee: bear → nobody
Component: Release Engineering → Release Engineering: Automation (General)
OS: Mac OS X → Linux
QA Contact: catlee
Whiteboard: [briarpatch] → [buildmasters]
going to say this should be done with puppet rather than slavealloc.
No longer blocks: 786712
Severity: normal → enhancement
Priority: -- → P4
Whiteboard: [buildmasters] → [buildmasters][puppet]
Product: mozilla.org → Release Engineering
Looks like we do this now: https://github.com/mozilla/build-puppet/blob/master/modules/buildmaster/manifests/buildbot_master/mozilla.pp#L49
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.