[Mesa-dev] CI job for Android builds

Jose Fonseca jfonseca at vmware.com
Tue May 17 22:14:40 UTC 2016

On 17/05/16 22:43, Rob Clark wrote:
> On Tue, May 17, 2016 at 5:13 PM, Rob Herring <robherring2 at gmail.com> wrote:
>> I'm in the process of setting up a CI job to track Android builds of
>> mesa master (ATM merging in a branch of commits needed to build which
>> are not yet upstream). It is mostly working now though I'm still
>> tweaking the setup a bit. It is built on AOSP master branch as well.
>> Build errors/warnings are published here:
>> https://ci.linaro.org/job/robher-aosp/lastBuild/parsed_console/
>> I can add anyone who would like to get emails of errors.
> Great idea!
> I think appveyor (windows CI build) just spams all of mesa-dev for
> build breaks.. and I guess I don't see a reason not to do that for
> android CI builds as well.

What do you mean by "spams"?  Do you mean to say the AppVeyor traffic is 
too much?

FYI, the notification settings are set such that AppVeyor does _not_ 
email for _every_ failure.  It emails when the build goes from passing 
-> failed, or failed -> passed.

So, if the Windows build breaks while all Windows maitainers are on 
vacation, there should be no spam.

The only situation where there's spam is when there are intermetting 
build failures.  We've seen a few of those (due to infrastructure 
issues), but thankfully not too often.

I recommend similar notification settings.  Too many emails: everybody 
ignores, or will setup rules to hide those emails.  No emails: nobody 


More information about the mesa-dev mailing list