Re: [PATCH] travis: add initial Travis CI script to do builds

[Doug Goldstein <cardoe@cardoe.com>]

[-- Attachment #1.1: Type: text/plain, Size: 1599 bytes --]

On 2/5/16 10:33 AM, Ian Campbell wrote:
> On Fri, 2016-02-05 at 08:48 -0600, Doug Goldstein wrote:
>>
>> The goal here is not to replace osstest by any means but to augment it by
>> providing some easy to do build tests on every revision and reporting back. It
>> should be possible in the future to potentially tie this into osstest to
>> allow this to build and if the tree for some reason failed to build not kick
>> off a test flight on osstest. Just some thoughts, I know I'm getting a bit
>> ahead of myself.
> 
> IMHO Free Software projects like Xen Project should be very wary of tying
> their infrastructure and workflows to services which are backed by non-free 
> software (which I know github is and AFAICT Travis CI also is).
> 
> IOW while augmenting things to provide extra/non-critical data about the
> state of the world might be ok or at least tolerable, projects should be
> wary of inserting these tools into the "critical path" of their workflows.
> I think inserting Travis CI before osstest would be just such a mistake.
> 
> https://mako.cc/writing/hill-free_tools.html is a good essay on the
> subject.
> 
> Ian.
> 

That's fine. I was throwing out some ideas, we definitely don't have to
do the things I said. My stated just trying to use existing services to
provide some extra testing of Xen and not replace osstest, similarly to
Xen using Coverity which itself is not open source. I've been tinkering
with using llvm's scan-build to provide similar analysis but currently
the tree doesn't build cleanly with llvm.

-- 
Doug Goldstein


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 959 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel