[Buildbot-devel] custom buildstem

[Philippe McLean]

I think there is a pattern in here... it seems a bit like MVC

On Tue, Mar 29, 2011 at 8:58 AM, Philippe McLean
<philippe.mclean at gmail.com>wrote:

> Over time, buildbot config files naturally grow in complexity.
> It is good to avoid this complexity if possible, especially if your
> environment makes use of branching.
>
> some choices I try to make:
>
> - above all else, simplicity
> - pass/fail steps that report verbosely
> - standalone buildbot steps, that can be tested outside without re-building
> - keep build scripts and test scripts in the branch code itself, not in the
> master.cfg
> - minimize master restarts/master.cfg updates
> - your buildbot installation should be more reliable than the build it is
> testing
>
>
>
>  On Tue, Mar 29, 2011 at 8:11 AM, <mp3 at hello.lv> wrote:
>
>> Thank You, Dustin, for the explanation. I thought that would be a trivial
>> task, because buildbot itself is written in python. I'll use an external
>> script. Maybe it is worth mentioning this somewhere in buildbot manual.
>>
>> On Tue, 29 Mar 2011 09:53:02 -0500, "Dustin J. Mitchell"
>> <dustin at v.igoro.us> wrote:
>> > For the record, we've historically resisted putting "execute this
>> > arbitrary Python" support into Buildbot, for two reasons:
>> >
>> >  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.
>> >
>> >  2. it's generally the wrong solution to the problem you're trying to
>> solve
>> >
>> > In particular, keep in mind that with this approach, if you want to
>> > make *any* change to how you prepare VXWorks 6.6, you need to do a
>> > complete redeployment of your buildslave installation across all
>> > slaves.  That's far harder than adjusting a script in your source-code
>> > repository or reconfiguring your master.
>> >
>> > Of course, you're absolutely free to do whatever you'd like on your
>> > own system.  Benoît mentioned merging into Buildbot, and I wanted to
>> > make sure you had the full picture there.
>> >
>> > Dustin
>>
>>
>> ------------------------------------------------------------------------------
>> Enable your software for Intel(R) Active Management Technology to meet the
>> growing manageability and security demands of your customers. Businesses
>> are taking advantage of Intel(R) vPro (TM) technology - will your software
>> be a part of the solution? Download the Intel(R) Manageability Checker
>> today! http://p.sf.net/sfu/intel-dev2devmar
>> _______________________________________________
>> 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/20110329/6ba9fcd1/attachment.html>