You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 20, 2020. It is now read-only.
Instructions proposed by Peter Mayo in Ozone mailing list:
To own maintain and operate a builder is particularly easy if you also have the code to the master and it looks like one of chromium's own.
To start I would:
A) check out chromium's tools
.gclient:
[{ "name": "build", "url": ".../trunk/tools/build...", "deps_file": "DEPS" (or.git) }]
B) get the OZONE FYI builder up and going locally:
i) echo "secret" >build/site_config/.bot_password
ii) pretend to be the slave:
after the imports in build/slave/run_slave.py add
os.environ['TESTING_MASTER'] = 'ChromiumFYI'
os.environ['TESTING_MASTER_HOST'] = 'localhost'
os.environ['TESTING_SLAVENAME'] = 'vm951-m1'
iii) run the master : in build/masters/master.chromium.fyi "make start"
iv) run the slave : in build/slave "make start"
v) go to <hostname>:8011/waterfall?show=Ozone%20ECS%20Linux
C) copy the interesting parts to a new master that you checkout for your own repo
gclient:
[{ "name": "build", ...},{"name": "intel", ...}]
where the DEPS adds a directory like build/masters/master.intel.wayland
D) change the slaves portion around in a corresponding fashion
E) edit the recipes to be what you want to watch:
especially like scripts/slave/recipes/ozone_ecs.py
F) scale out to more slaves - check out slave.DEPS in the tools repo to see how it can be pruned down,
don't forget to share the same secret for the bot password.
This way gclient sync should keep you up to date with us, but not break you too often.
We now pin to a specific chromium checkout always. This task is to set up a build bot for Ozone-Wayland.
Usage:
The text was updated successfully, but these errors were encountered: