[OpenAFS-devel] OpenSUSE tumbleweed build slave
Jason Edgecombe
jason@rampaginggeek.com
Sun, 25 Jan 2015 17:52:07 -0500
On 01/25/2015 02:02 PM, Benjamin Kaduk wrote:
> On Sun, 25 Jan 2015, Jason Edgecombe wrote:
>
>> Hi everyone,
>>
>> opensuse 11 is end-of-life. Christof Hanke has been gracious enough to offer
>> to upgrade the build slave to opensuse 13 or possibly tumbleweed. Tumbleweed
>> is a rolling release that will be the next stable version of opensuse. The
>> advantage of having a tuble weed slave is the automated compilation against
>> failry recent Linux kernels.
>>
>> Are there any objections to going with tumbleweed or having both opensuse 13
>> and tumbleweed?
> This sort of rolling release means that new submissions which do not
> introduce regressions could fail to be verified due to the installed OS
> becoming incompatible with the existing openafs master branch. If we have
> the tumbleweed machine doing periodic builds and someone is watching that
> output for regressions, then this would be a highly useful thing to have.
> Is there a way for someone to get notified when periodic builds begin to
> fail (other than having that person remember to look at the build logs)?
Yes, Buildbot can send emails about failed builds. Out of the box, it
can support notifications to email, IRC, and, HTTP hooks.
emails can be sent for select builders or groups of builders, and based
on the status of the builds (success, fail, warning). Buildbot can also
email when build status state changes, i.e. failing to good or good to
failing.
Ref: http://docs.buildbot.net/current/manual/cfg-statustargets.html
Where should these status emails be sent? Perhaps to
openafs-cvs@openafs.org?
Sincerely,
Jason