78
edits
ReleaseEngineering/Jacuzzis: Difference between revisions
Jump to navigation
Jump to search
→Implementation: Add steps for updating runnable jacuzzi code.
(→Implementation: Add steps for updating runnable jacuzzi code.) |
|||
| Line 9: | Line 9: | ||
The manage_jacuzzis.py script is responsible for managing the specific machines in each jacuzzi, and populating the files. It reads config.json to determine how many of each type of machine should be in each jacuzzi. It also consults the [https://secure.pub.build.mozilla.org/builddata/reports/reportor/daily/machine_sanity/usable_slaves.json usable slaves report] and slavealloc to pick appropriate slaves. | The manage_jacuzzis.py script is responsible for managing the specific machines in each jacuzzi, and populating the files. It reads config.json to determine how many of each type of machine should be in each jacuzzi. It also consults the [https://secure.pub.build.mozilla.org/builddata/reports/reportor/daily/machine_sanity/usable_slaves.json usable slaves report] and slavealloc to pick appropriate slaves. | ||
= Runnable Code = | |||
The runnable scripts: allocate.py and manage_jacuzzis.py live in a separate repository from the static files: https://github.com/mozilla/build-jacuzzi-allocator | |||
So, to modify code, you'll need to submit a pull request to this repository and then run <code>git pull</code> from <code>/data/releng/src/jacuzzi-allocator</code> on the relengwebadm host -- where crontask.sh lives. | |||
= Updating jacuzzis = | = Updating jacuzzis = | ||