Lines Matching refs:worker

9 buildbot-worker to private worker builder to LLVM Buildbot Infrastructure.
70 #. Install buildbot-worker (currently we are using buildbot version 2.8.5).
71    Depending on the platform, buildbot-worker could be available to download and
75 #. Create a designated user account, your buildbot-worker will be running under,
78 #. Choose the buildbot-worker root directory (all builds will be placed under
79    it), buildbot-worker access name and password the build master will be using
80    to authenticate your buildbot-worker.
82 #. Create a buildbot-worker in context of that buildbot-worker account. Point it
84    Creating a worker
85    <http://docs.buildbot.net/current/tutorial/firstrun.html#creating-a-worker>`_
90        $ buildbot-worker create-worker <buildbot-worker-root-directory> \
92                     <buildbot-worker-access-name> \
93                     <buildbot-worker-access-password>
95    This will cause your new worker to connect to the staging buildmaster
96    which is silent by default.  Only once a new worker is stable, and
100 #. Fill the buildbot-worker description and admin name/e-mail.  Here is an
101    example of the buildbot-worker description::
111 #. Make sure you can actually start the buildbot-worker successfully. Then set
112    up your buildbot-worker to start automatically at the start up time.  See the
116 #. Send a patch which adds your build worker and your builder to
140 #. Send the buildbot-worker access name and the access password directly to
145 #. Check the status of your buildbot-worker on the `Waterfall Display (Staging)
149    contact and worker information are correct.
161    To move a worker to production (once approved), stop your worker, edit the
240   well, and that having local per-worker caches gets most of the benefit