Le 08/11/2013 15:13, Thomas Zimmermann a écrit :
>
>> Also - what do we think about getting Travis to use the b2g-inbound
>> builds rather than mozilla-central? (In order to reduce the cycle time
>> when needing to make gecko changes)
> I think b2g-inbound breaks too often. How would Travis know which
> version is not broken and contains the necessary changes to Gecko?

Do inbound unsuccessful builds generate binaries?

If it does not, or if there is a clear way to tell that it's an
unsuccessful build, we could filter only successful builds from inbound.
If it's possible, it would be a great idea. I could even do the patch
for Travis if you tell me what I should know :)

-- 
Julien

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g

Reply via email to