[Buildbot-devel] Best practices for testing buildbot config?

[Philippe McLean]

suggestions:

- set up a second test buildbot server
- reduce complexity in buildbot config (move functionality into build tree
scripts)
- do your testing when people aren't working/let them know

On Tue, Jul 19, 2011 at 10:21 AM, William Deegan
<bill at baddogconsulting.com>wrote:

> Greetings,
>
> As my buildbot config gets more complex, I find it's more desirable to have
> some way to fully test changes, both to the config and with newer versions
> of Buildbot.
>
> I'm wondering if anyone has some suggestions on how best to do this?
>
> Currently I detect if an environment variable is set when I launch
> buildbot, and that reassign's the ports used by buildbot.
> I'm thinking this could also be used to switch from using active BuildSteps
> to ones which mock out their functionality.
>
> Once I have this configured, it would be trivial to have a meta-buildbot
> pull the latest buildbot/master code and run it against my config so I can
> file bugs on buildbot..
>
> Thanks,
> Bill
>
>
>
> ------------------------------------------------------------------------------
> Magic Quadrant for Content-Aware Data Loss Prevention
> Research study explores the data loss prevention market. Includes in-depth
> analysis on the changes within the DLP market, and the criteria used to
> evaluate the strengths and weaknesses of these DLP solutions.
> http://www.accelacomm.com/jaw/sfnl/114/51385063/
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20110719/792d15e8/attachment.html>