582939 - Decouple the buildslave names from the machines that they run on

Status: VERIFIED FIXED

(Tamarin Graveyard :: Build Config, defect)

Description

[Brent Baker]

Currently all of the build slaves that connect to the build master are named based on the machine that they were originally running on. This makes it extremely confusing when we move the build slave to another machine. The build slaves should be named based on the builder that they attach to and NOT the machine that they are currently running on.

Example:
The build slave that connects and handles the 'windows' builder is currently called 'asteamwin2', since that is the machine that it runs on. The build slave should instead just be called 'windows' to make the builder that it is connecting to.

Comment 1

[Brent Baker]

Attachment: change build slave names to match builder and NOT host

Comment 2

[Chris Peyer]

Comment on attachment 461217 [details] [diff] [review]
change build slave names to match builder and NOT host

Looks good - just need to make sure when updating each buildslave that the host info file is up to date and contains the correct machine name and ip address.  For the beagleboards maybe we should place a link to the ip table in zerowing?

Comment 3

[Brent Baker]

(In reply to comment #2)
> Looks good - just need to make sure when updating each buildslave that the host
> info file is up to date and contains the correct machine name and ip address. 
> For the beagleboards maybe we should place a link to the ip table in zerowing?

Good idea, I will update the host files on the beagleboards to show their name and then a link to the wiki page to find their IP

Comment 4

[Brent Baker]

Comment on attachment 461217 [details] [diff] [review]
change build slave names to match builder and NOT host

patches pushed as:
4970:7804cb4738e5
4971:b153bd2ad55b