Changes between Version 24 and Version 25 of FAQ


Ignore:
Timestamp:
Jan 4, 2017, 2:15:11 AM (11 months ago)
Author:
rutsky
Comment:

update "slave" with "worker"

Legend:

Unmodified
Added
Removed
Modified
  • FAQ

    v24 v25  
    2222== Why don't wildcards work in my !ShellCommand? ==
    2323
    24 Probably because your build slave is running a Unix variant and you wrote your command as a list (the recommended way):
     24Probably because your worker is running a Unix variant and you wrote your command as a list (the recommended way):
    2525{{{
    2626factory.addStep(ShellCommand(
     
    5454Most people feel that their build proces is "normal", "obvious", or "common".  It's not.  No two buildbot users have the same build process, nor do they organize their code in the same way.  You can believe this now, or watch the mailing list and IRC channel for a week or so and believe it later.
    5555
    56 == My Mac Buildslave can't resolve domain names ==
     56== My Mac worker can't resolve domain names ==
    5757
    58 Macs use "security contexts", so if you start a buildslave via an SSH connection, then once that connection disappears, the context does, too.  See UsingLaunchd or UsingStartupItemContext for workarounds.
     58Macs use "security contexts", so if you start a worker via an SSH connection, then once that connection disappears, the context does, too.  See UsingLaunchd or UsingStartupItemContext for workarounds.
    5959
    6060== I'm getting errors about overly-long filenames ==
    6161
    62 This is surprisingly common, especially on Windows and, to a lesser extent, Mac buildslaves, when you have tests that create lots of nested directories.  There's not a lot that Buildbot can do, but here are some ideas:
    63  * set up your buildslave root directories in a short top-level directory, e.g.,
     62This is surprisingly common, especially on Windows and, to a lesser extent, Mac workers, when you have tests that create lots of nested directories.  There's not a lot that Buildbot can do, but here are some ideas:
     63 * set up your worker root directories in a short top-level directory, e.g.,
    6464   {{{
    65    buildslave create-slave /B master:9989 botname botpass
     65   buildbot-worker create-worker /B master:9989 botname botpass
    6666   }}}
    6767 * use abbreviated builddirs in your builder configurations:
     
    109109This happens with version-control systems that do not use integers for revisions (that is, most everything but SVN).  You'll need to add {{{order_console_by_time=True}}} to your !WebStatus constructor in {{{master.cfg}}}.
    110110
    111 == I'd like to run arbitrary Python code on the slave ==
     111== I'd like to run arbitrary Python code on the worker ==
    112112
    113113We've historically resisted putting "execute this
    114114arbitrary Python" support into Buildbot, for two reasons:
    115115
    116  1. it's more complex than it sounds: It boils down to sending a string on which the remote system calls exec(), but with blocking and potentially damaging ramifications for the running buildslave instance.  Steer clear of thoughts of sending compiled Python bytecode across the wire, too.
     116 1. it's more complex than it sounds: It boils down to sending a string on which the remote system calls exec(), but with blocking and potentially damaging ramifications for the running worker instance.  Steer clear of thoughts of sending compiled Python bytecode across the wire, too.
    117117 1. it's generally the wrong solution to the problem you're trying to solve: If the functionality is so complex that it cannot be represented in a few lines of shell script, then most likely that functionality will need to be revision-controlled and tested outside of Buildbot.  Which means that it should be in a Python script in version-control somewhere, and Buildbot should be running the code from there.
    118118
     
    133133== My custom step seems to be executing on the master! ==
    134134
    135 Yep.  Buildbot doesn't magically execute Python written on the master on the slave, or vice versa.  All it does is send instructions to the slave, and often those instructions involve invoking some other program via the shell.
     135Yep.  Buildbot doesn't magically execute Python written on the master on the worker, or vice versa.  All it does is send instructions to the worker, and often those instructions involve invoking some other program via the shell.