From: Stefan Hajnoczi <stefanha@redhat.com>
To: alex.bennee@linaro.org
Cc: kwolf@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 0/0] .travis and minor compile fixes
Date: Tue, 24 Sep 2013 13:41:33 +0200 [thread overview]
Message-ID: <20130924114133.GE27882@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1379952450-29640-1-git-send-email-alex.bennee@linaro.org>
On Mon, Sep 23, 2013 at 05:07:27PM +0100, alex.bennee@linaro.org wrote:
> Given I found a couple of issues while doing this I think this is
> useful alongside the existing buildbot efforts. It allows developers
> to run simple smoke-tests without access to the buildbot
> infrastructure (but of course needing github/travis access, free for
> FLOSS projects). I can see further development possibilities in the
> future, one example would be a tree that auto-generates branches with
> testing results for each patch series as they come into the mailing
> list.
This is looking very interesting. Buildbot is centralized and can be
hard to debug. As a result not many people triage and fix configuration
issues.
Travis CI allows individual developers to modify the build
configuration. This is much more friendly.
Can you explain the limitations of Travis CI? For example, does it
start costing money at some point?
Stefan
next prev parent reply other threads:[~2013-09-24 11:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 16:07 [Qemu-devel] [PATCH v2 0/0] .travis and minor compile fixes alex.bennee
2013-09-23 16:07 ` [Qemu-devel] [PATCH 1/3] .travis.yml: basic compile and check recipes alex.bennee
2013-09-23 16:07 ` [Qemu-devel] [PATCH 2/3] .travis.yml: greatly expand the coverage + more builds alex.bennee
2013-09-23 16:07 ` [Qemu-devel] [PATCH 3/3] block/stream.c: ensure copy always set alex.bennee
2013-09-24 12:06 ` Stefan Hajnoczi
2013-09-24 14:27 ` Alex Bennée
2013-09-25 8:41 ` Stefan Hajnoczi
2013-09-24 11:41 ` Stefan Hajnoczi [this message]
2013-09-24 14:19 ` [Qemu-devel] [PATCH v2 0/0] .travis and minor compile fixes Alex Bennée
2013-09-25 8:33 ` Stefan Hajnoczi
2013-09-24 12:07 ` Stefan Hajnoczi
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=20130924114133.GE27882@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).