canmove, Confirmed users
1,394
edits
ReferencePlatforms: Difference between revisions
→Tracking ref images being refreshed
| Line 63: | Line 63: | ||
Every time we do a relevant change to [http://hg.mozilla.org/build/tools/log/tip/buildbot-helpers/buildbot-tac.py buildbot-tac.py] we have to update the '''build-tools''' repo on the ref images (through puppet on linux/darwin builders and manually on all others) and then ask IT to refresh the images (either builders or testers). | Every time we do a relevant change to [http://hg.mozilla.org/build/tools/log/tip/buildbot-helpers/buildbot-tac.py buildbot-tac.py] we have to update the '''build-tools''' repo on the ref images (through puppet on linux/darwin builders and manually on all others) and then ask IT to refresh the images (either builders or testers). | ||
NOTE: Do not ask to refresh the linux/windows ref VMs. | *NOTE: Do not ask to refresh the linux/windows ref VMs. | ||
NOTE: Make sure that /builds/slave and ~talos-slave (or equivalent) is empty on the ref machine for the buildbot-tac.py generator to work (TODO: test that this is true for testing machines) | *NOTE: Make sure that /builds/slave and ~talos-slave (or equivalent) is empty on the ref machine for the buildbot-tac.py generator to work (TODO: test that this is true for testing machines) | ||
*NOTE: before imaging a fedora system, empty out ''/etc/udev/rules.d/70-persistent-net.rules''. Note that this file will be re-filled at every boot, so this will need to happen before each image is taken. | |||
Please keep track of when we ask IT to refresh the images. | Please keep track of when we ask IT to refresh the images. | ||