Closed Bug 520727 Opened 15 years ago Closed 14 years ago

new buildslaves shouldn't require manual buildbot.tac creation

Categories

(Release Engineering :: General, defect, P3)

Product:
Release Engineering
Component:
General
Platform:
x86
All
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: joduinn, Assigned: bhearsum)

References

Details

(Whiteboard: [automation][talos][buildslaves]) 

This builds upon earlier work setting up new slaves using config management software and/or ref iamges. 

Once this bug is done, we should be able to power up new slaves, and get them running in staging with no manual intervention.(known exception: for opsi users, still need to re-install opsi because of key generation) 

Once a slave is seen to run correctly in staging, it can be moved to production when deemed safe to do so.
Putting into future bin as this is exploratory.
Component: Release Engineering → Release Engineering: Future
Expanding this to also pull in latest version of buildbot from hg, as outlined here?

https://wiki.mozilla.org/ReferencePlatforms/Mac-10.5#Install_Buildbot

This should simplify initial setup, and also make sure all slaves refresh to newer versions of buildbot as we move the hg tag forward.
Summary: Use config mgmt to install and configure buildbot.tac on new buildslaves → Use config mgmt to install buildbot and configure buildbot.tac on new buildslaves
(In reply to comment #2)
> Expanding this to also pull in latest version of buildbot from hg, as outlined
> here?
> 

Isn't that a separate bug? For the record, we already have that on Linux and Windows.
(In reply to comment #3)
> (In reply to comment #2)
> > Expanding this to also pull in latest version of buildbot from hg, as outlined
> > here?
> > 
> 
> Isn't that a separate bug? For the record, we already have that on Linux and
> Windows.

I think it is, so I filed bug 524097.
Summary: Use config mgmt to install buildbot and configure buildbot.tac on new buildslaves → Use config mgmt to configure buildbot.tac on new buildslaves
(In reply to comment #4)
> (In reply to comment #3)
> > (In reply to comment #2)
> > Isn't that a separate bug? For the record, we already have that on Linux and
> > Windows.
> I think it is, so I filed bug 524097.

Ah, didnt realise linux/puppet was already doing buildbot install that way, or that win32/opsi was written-but-not-enabled. Thanks for clarifying (and fixing 524097).
bhearsum: hey, can this now be closed?
It's done on the build machines at this point, but not on Talos. I still have the final bits of documentation to update for the win32 ref platform page, too.
Mass move of bugs from Release Engineering:Future -> Release Engineering. See
http://coop.deadsquid.com/2010/02/kiss-the-future-goodbye/ for more details.
Component: Release Engineering: Future → Release Engineering
Priority: -- → P3
Whiteboard: [automation][puppet][opsi][talos][buildslaves]
(In reply to comment #7)
> It's done on the build machines at this point, but not on Talos. I still have
> the final bits of documentation to update for the win32 ref platform page, too.

We've got this on Talos now, too, except for Windows 7. Getting closer!

Updating the summary/tags to match reality.
Summary: Use config mgmt to configure buildbot.tac on new buildslaves → new buildslaves shouldn't require manual buildbot.tac creation
Whiteboard: [automation][puppet][opsi][talos][buildslaves] → [automation][talos][buildslaves]
The last part of this (support for Windows 7, 32-bit) is getting done in bug 584271. Grabbing this bug so I can close it when that one is done.
Assignee: nobody → bhearsum
Depends on: 584271
Last platform to do here is win7 32-bit, tracked in bug 584271. Not holding this open just for that.
Status: NEW → RESOLVED
Closed: 14 years ago
No longer depends on: 584271
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.