ReleaseEngineering/PuppetAgain/Modules/runner: Difference between revisions
< ReleaseEngineering | PuppetAgain | Modules
Jump to navigation
Jump to search
Ianconnolly (talk | contribs) No edit summary |
Ianconnolly (talk | contribs) (→Tasks) |
||
| Line 7: | Line 7: | ||
=Tasks= | =Tasks= | ||
To add a task to be managed by Runner, the script should be added to runner/files and an instance of the runner::task class should be created (see the existing tasks in runner::tasks for examples) | To add a task to be managed by Runner, the script should be added to runner/files and an instance of the runner::task class which manages this script should be created (see the existing tasks in runner::tasks for examples). The tasks desired on a particular machine should be included in the toplevel class for that machine type (eg. toplevel::slave::releng::build for build slaves) | ||
Revision as of 16:37, 24 June 2014
The runner module installs Runner, which runs pre-buildbot tasks on slaves (currently CentOS build slaves only). It also manages the tasks to be run by runner.
Runner
Documentation and usage for Runner itself can be found in its repository.
Tasks
To add a task to be managed by Runner, the script should be added to runner/files and an instance of the runner::task class which manages this script should be created (see the existing tasks in runner::tasks for examples). The tasks desired on a particular machine should be included in the toplevel class for that machine type (eg. toplevel::slave::releng::build for build slaves)