ReleaseEngineering/How To/Manage Buildbot with Fabric: Difference between revisions

ReleaseEngineering/How To/Manage Buildbot with Fabric (view source)

16 bytes added , 7 July 2011

m

Confirmed users

4,293

edits

@@ Line 44: / Line 44: @@
 Fabric works on individual hosts, and supports organizing these hosts into groups.  This is mostly a good fit for how we need to work, except we often have multiple buildbot masters on a single host, so there is a bit of hacking in master_fabric.py to pick out the right hosts to operate on depending on what the user has selected.
-Hosts are selected with the -H flag, and roles are selected with the -R flag.  Hosts correspond to the 'name' field in the masters json file, and are short abbreviations to refer to each master, e.g. pm01-bm, pm01-sm, pm02-try.  We have 4 roles defined: 'build', 'scheduler', 'try', and 'tests'.  Selecting a role will restrict fabric to only operate on masters that operate on that role.
+Hosts are selected with the -H flag, and roles are selected with the -R flag.  Hosts correspond to the 'name' field in the masters json file, and are short abbreviations to refer to each master, e.g. pm01-bm, pm01-sm, pm02-try.  We have 4 roles defined: '''build''', '''scheduler''', '''try''', and '''tests'''.  Selecting a role will restrict fabric to only operate on masters that operate on that role.
 The string 'all' when specified via -H or -R means that all masters in the masters file will be operated on.