[Mono-devel-list] Automated builds

Fawad Halim fawad at fawad.net
Tue Mar 16 10:39:06 EST 2004

Yes, we can chain as many commands as we wish. The steps for a 
particular target are written like:

steps.append((Compile, {'workdir': 'mcs',
    'command': 'make',
    'flunkOnFailure': 1}))

(in the mcs directory, execute the 'make' command, and if it returns 
non-zero, think it's a build failure. The default buildbot comes with a 
couple of Processes (CVS, SVN, shell command, etc.). It's possible to 
define others and whether they should be considered critical to the 
build or not (e.g. make run-test is critical, make doc is not).

One thing I forgot to mention is that it has the ability to be triggered 
on CVS commits using CVSToys.


Jaroslaw Kowalski wrote:

>Would it be possible to include the unit tests from other OS projects, like
>NAnt, NUnit, NDoc and run them on a regular basis against mono/cvs?
>NAnt has extensive unit tests base and makes use of many advanced .NET
>features and it's designed to be portable (i.e. aware of slash-vs-backslash
>issues and so on). This makes NAnt quite good at Mono regression testing. I
>don't know about other tools but their unit tests should be runnable on
>mono, too.
>Recently we've reached a stage where nant is able to rebuild itself on
>mono/linux and it would be a good idea not to lose it because of some mono
>regression (like AppDomain.Unload which we had recently).
>What do you think?
>----- Original Message ----- 
>From: "Nick D" <ndrochak at gol.com>
>To: "'Fawad Halim'" <fawad at fawad.net>; <mono-devel-list at ximian.com>
>Sent: Tuesday, March 16, 2004 1:12 PM
>Subject: RE: [Mono-devel-list] Automated builds
>>>| -----Original Message-----
>>>| From: mono-devel-list-admin at lists.ximian.com [mailto:mono-devel-list-
>>>| admin at lists.ximian.com] On Behalf Of Fawad Halim
>>>| Sent: Tuesday, March 16, 2004 2:33 PM
>>>| To: mono-devel-list at ximian.com
>>>| Subject: [Mono-devel-list] Automated builds
>>>| My question is: is there need for such a tool for mono apps? I know
>>>| that if we were to go for something like this, it'll help out in
>>>| ironing out small edge cases that would otherwise get missed out when
>>>| doing builds on nicely tuned boxes (for instance, I found that
>>>| debugger/frontends/scripting/Makefile.am assumes that mcs src is in
>>>| the same dir as debugger when looking for jay).
>>This would be awesome!  I'd also like it to run the unit tests and report
>>results. Would that be easy to add?
>>Let's please get this running. When we have Build Sheriff(s) this is the
>>perfect monitoring tool for them.
>>Nick D.
>>Mono-devel-list mailing list
>>Mono-devel-list at lists.ximian.com
>Mono-devel-list mailing list
>Mono-devel-list at lists.ximian.com

More information about the Mono-devel-list mailing list