[Buildbot-devel] Hello to the list and checkconfig question
Thomas Fletcher
thomas at cranksoftware.com
Sat Jan 24 03:04:14 UTC 2009
Ian Peters-Campbell wrote:
> Hey all,
[ Introduction snipped ]
> The current situation is that I have Buildbot installed on a CentOS
> server and working at least to the point that I can get the version
> number out of it and have created a buildmaster under its own account on
> the machine. I wanted to test the default configuration file to make
> sure I had a good starting point but I get the following error (stack
> trace removed)
>
> File
> "/usr/local/lib/python2.5/site-packages/buildbot/steps/python_twisted.py",
> line 392, in __init__
>
> raise ValueError("Must either set testChanges= or provide tests=")
>
> ValueError: Must either set testChanges= or provide tests=
Congratulations, buildbot is an excellent choice. Just to let you
know, I'm running it under CentOS 5.2 without any difficulty (or
special configurations).
I don't know that the default build configuration actually does
anything, since you will need to set-up a build factory and
populate it with some build steps.
> As sort of an expansion to that question, does anyone have advice
> regarding a sane, step-wise setup for BUildbot? Now that I have a build
> master sort of set up is my next step to get a slave set up on the
> machine with the ARM compiler, or is there some set of configuration and
> testing that can be performed purely within the buildmaster before
> setting up slaves?
For my initial configurations, I used set-up slaves on the master and
would work through creating the build-steps in small increments doing
exactly the same things that I would do by hand (ie put in a checkout
step .. verify it works, add a configure step .. verify it works etc).
Once it was working locally, it made it easier to dispatch it out to
real slave machines.
Hope this helps,
Thomas
--
Thomas Fletcher
Crank Software Inc.
www.cranksoftware.com
More information about the devel
mailing list