From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Ed Maste <emaste@freebsd.org>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Hosted CI for FreeBSD - Cirrus CI
Date: Fri, 7 Dec 2018 09:54:17 +0000 [thread overview]
Message-ID: <20181207095417.GF13784@redhat.com> (raw)
In-Reply-To: <CAPyFy2CWKEmYoYrDY=pHQVxXjMZnPts5qKVHL94yx0smTjx9bA@mail.gmail.com>
On Wed, Dec 05, 2018 at 03:43:07PM -0500, Ed Maste wrote:
> I'd very much like to have CI coverage for QEMU on FreeBSD, and as of
> yesterday there's a hosted CI service that supports FreeBSD: Cirrus
> CI. They also offer free service for OSS projects. I created a
> .cirrus.yml (shown below) in a QEMU GitHub fork and successfully
> executed a build test.
Looking at this more generally I see they support Linux containers,
native Windows containers, macOS and FreeBSD. IOW, they offer more
platforms than our current Travis setup does and aren't stuck on an
amcient Ubuntu version.
Thus I wonder if we could in fact switch all our travis setup over to
use Cirrus CI, and stop using Travis entirely.
One key thing I can't find out is what, if any, limitations they put
on resources used by the free service for OSS projects. Does anyone
know if they limit the number of concurrent build jobs like Travis
does ? Do they put a fixed time limit on execution of a single job ?
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2018-12-07 9:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 20:43 [Qemu-devel] Hosted CI for FreeBSD - Cirrus CI Ed Maste
2018-12-05 21:01 ` Kamil Rytarowski
2018-12-05 21:58 ` Ed Maste
2018-12-06 1:08 ` Kamil Rytarowski
2018-12-06 10:23 ` Daniel P. Berrangé
2018-12-06 18:25 ` Ed Maste
2018-12-07 9:54 ` Daniel P. Berrangé [this message]
2018-12-14 14:57 ` Ed Maste
2019-01-15 18:32 ` Ed Maste
2019-01-15 18:47 ` Peter Maydell
2019-01-15 18:58 ` Ed Maste
2019-01-15 21:23 ` Ed Maste
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=20181207095417.GF13784@redhat.com \
--to=berrange@redhat.com \
--cc=emaste@freebsd.org \
--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).