bloodhound-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Martin <>
Subject Re: RAT builds
Date Thu, 09 Aug 2012 08:41:34 GMT
Hi Gav,

That is excellent. I will try adjusting .rat-ignore to be a bit more 
sensible about our copy of the trac vendor branch. I will ask if I can't 
work out how to do anything fancy if we need it.

I am also interested in adding new builders to the config so I will 
examine your approach to that. I have found the master.cfg and so I can 
see a list of the available buildslaves. Are there any rules for which 
slaves I should select when we want to cover more platforms?


On 08/09/2012 08:56 AM, Gavin McDonald wrote:
> Hi All,
> I've created and enabled a RAT build for the bloodhound trunk. This is on a
> per commit basis.
> Updates to the output [1] and [2] are hourly.
> The way to get the license check down is to add ASL license headers in all
> files except those deemed
> To be exclusionary. To exclude files/dirs. From the RAT report is to add
> path patterns to the
> .rat-ignore file in bloodhound trunk svn [3]
> The Buildbot config file for Bloodhound [4] is editable by any committer so
> feel free to re-use
> The file to add code tests etc. Try and stick to the conventions used,
> (f_bh_2 would be your next factory)
> Manual triggers are possible via the bloodhound-bot on IRC #bloodhound.
> Any questions please yell, no cc required as I am subbed to this list.
> Gav...
> [1] -
> [2] -
> [3] -
> [4] -
> /master1/projects/bloodhound.conf

View raw message