Confirmed users
2,456
edits
ReleaseEngineering/How To/Manage Buildbot with Fabric: Difference between revisions
ReleaseEngineering/How To/Manage Buildbot with Fabric (view source)
Revision as of 03:44, 7 December 2010
, 7 December 2010→Hosts and role groups
No edit summary |
|||
| Line 35: | Line 35: | ||
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. | |||
Fabric relies on being able to ssh to the masters without password authentication, so be sure to have your ssh keys set up! | Fabric relies on being able to ssh to the masters without password authentication, so be sure to have your ssh keys set up! | ||