From: Ian Campbell <ian.campbell@citrix.com>
To: Doug Goldstein <cardoe@cardoe.com>, xen-devel@lists.xen.org
Cc: Keir Fraser <keir@xen.org>, Tim Deegan <tim@xen.org>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH] travis: add initial Travis CI script to do builds
Date: Fri, 5 Feb 2016 16:33:12 +0000 [thread overview]
Message-ID: <1454689992.8672.106.camel@citrix.com> (raw)
In-Reply-To: <1454683729-13601-1-git-send-email-cardoe@cardoe.com>
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.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-02-05 16:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 14:48 [PATCH] travis: add initial Travis CI script to do builds Doug Goldstein
2016-02-05 15:09 ` Wei Liu
2016-02-05 15:19 ` Doug Goldstein
2016-02-05 15:24 ` Wei Liu
2016-02-05 16:33 ` Ian Campbell [this message]
2016-02-05 16:41 ` Doug Goldstein
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1454689992.8672.106.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=cardoe@cardoe.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.