On 04/16/2013 07:12 AM, Alex wrote:
> A thought. You might try having a tag (aka branch) which you apply to
> any revision and essentially state "this is the one I'd like to have
> automated build check against please" for the benefit of non-human
> release candidate checks. Anybody with build automation is asked to
> try head all the time of course ... but if there is a 'BC' tag that
> hasn't been built then do that one before simply following head. this
> maximizes the number of build automation hits on the revision you're
> thinking of converting into a release candidate. This isn't the same
> as a release candidate because you're not asking for any human
> involvement. Just that the distributed tooling across the whole
> community gives your release tool a pass/fail indication before even
> bothering to cut a candidate.
>
> You can probably use email-to-human as the back channel for when a BC
> happens to FTBFS, at least initially, but it would be better in the
> long term if you integrate that with normal build automation reporting.
>
Completely agree about the need for more automation. There are lots of
different dimensions to this. Right now, I don't have a formal network
of people doing this.
I would love for someone to step up and own this for the project. The
more of this I do, the slower the progress towards the features people
really need/want. At least that's how it is at the moment...
Anyone want to volunteer to coordinate a build network?
--
Alan Robertson <[email protected]> - @OSSAlanR
"Openness is the foundation and preservative of friendship... Let me claim
from you at all times your undisguised opinions." - William Wilberforce
_______________________________________________
Assimilation mailing list - Discovery-Driven Monitoring
[email protected]
http://lists.community.tummy.com/cgi-bin/mailman/listinfo/assimilation
http://assimmon.org/
