Changes between Version 23 and Version 24 of MetaBuildbotConfig


Ignore:
Timestamp:
Jan 4, 2017, 2:04:58 AM (18 months ago)
Author:
rutsky
Comment:

update "slave" with "worker"

Legend:

Unmodified
Added
Removed
Modified
  • MetaBuildbotConfig

    v23 v24  
    11= Master =
    2 The buildbot master is configured in {{{~/metabuildbot}}}.  It runs a slaveport on port 9989 and web on port 8010.  It is set up to run from the source checkout in {{{~/metabuildbot/src}}}.
     2The buildbot master is configured in {{{~/metabuildbot}}}.  It runs a workerport on port 9989 and web on port 8010.  It is set up to run from the source checkout in {{{~/metabuildbot/src}}}.
    33
    44To start/stop/restart the master, use e.g.,
     
    88The Buildbot config itself is contained in https://github.com/buildbot/metabbotcfg, checked out at ~/metabuildbot/metabbotcfg, with a {{{master.cfg}}} symlink pointing into the directory.  Note that passwords are contained in the metabbotcfg directory, but are not stored in the git repository.
    99
    10 The builder configuration flows from the slaves.  There are three types of builders: compatibility, slave-specific, and purpose-specific.  The compatibility builders run a particular version of Python and Twisted to check compatibility.  Slaves are tagged with the versions of Python they support, and the builders use virtualenv to install various versions of Twisted.  For most of these builders, several slaves are available, allowing better parallelism for faster results.
     10The builder configuration flows from the workers.  There are three types of builders: compatibility, worker-specific, and purpose-specific.  The compatibility builders run a particular version of Python and Twisted to check compatibility.  Workers are tagged with the versions of Python they support, and the builders use virtualenv to install various versions of Twisted.  For most of these builders, several workers are available, allowing better parallelism for faster results.
    1111
    12 The slave-specific builders attempt to build on a specific slave.  This is usually to identify issues unique to that slave, e.g., certain versions of Windows or older SQLite versions in enterprise linux distributions.
     12The worker-specific builders attempt to build on a specific worker.  This is usually to identify issues unique to that worker, e.g., certain versions of Windows or older SQLite versions in enterprise linux distributions.
    1313
    1414Finally, the purpose-specific builders do things like generate documentation, run lint-like tools, or create a coverage analysis.
     
    1818Most of the builds use a virtualenv to contain the Buildbot install; these use a custom step (defined in builders.py) as well as a cache of Python packages at http://buildbot.net/pkgs.
    1919
    20 = Slaves =
    21 == Cygwin slave setup ==
     20= Workers =
     21== Cygwin worker setup ==
    2222
    2323  1. Installed cygwin 1.7 with:
     
    5151    * easy_install pysqlite
    5252    * easy_install mock
    53   1. Create and start slave
    54     * mkdir ~/slave
    55     * cd ~/slave
    56     * buildbot create-slave . host:port slavename pwd
     53  1. Create and start worker
     54    * mkdir ~/worker
     55    * cd ~/worker
     56    * buildbot-worker create-worker . host:port workername pwd
    5757    * make start
    5858  1. If you want to have the user auto-login
    5959    1. run "control userpasswords2"
    6060    1. Uncheck "User must enter username and password to use this computer", click OK and enter the user credentials
    61     1. Add a shortcut in startup to 'c:cygwininash.exe --login -c "cd slave && make start log"'
     61    1. Add a shortcut in startup to 'c:cygwininash.exe --login -c "cd worker && make start log"'
    6262    1. Reboot
    6363
     
    115115    1. run "control userpasswords2"
    116116    1. Uncheck "User must enter username and password to use this computer", click OK and enter the user credentials
    117     1. Add a shortcut in startup to 'c:slaveuild_slave.bat' with this script containing 'buildbot start'
     117    1. Add a shortcut in startup to 'c:\start-worker.bat' with this script containing 'buildbot-worker start'
    118118    1. Reboot
    119119  1. install sqlalchemy and sqlalchemy-migrate, checking that the buildbot user has permission to access them