From: Jeremy Yallop <yallop@gmail.com>
To: Anil Madhavapeddy <anil@recoil.org>
Cc: David Allsopp <dra-news@metastack.com>,
"caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Thoughts on targeting windows
Date: Thu, 9 Oct 2014 10:33:54 +0100 [thread overview]
Message-ID: <CAAxsn=GJZmvnXiAoZ2kc+KJ8AXZwwBjoBwQm1bbUGtmdr2_BgA@mail.gmail.com> (raw)
In-Reply-To: <A12DB78A-2604-4E64-B0FE-64EF6590A120@recoil.org>
On 5 October 2014 23:14, Anil Madhavapeddy <anil@recoil.org> wrote:
> At a recent compiler hacking session in Cambridge, Don Syme pointed out a great Travis-like service for running regular Windows builds called Appveyor(.com). In order to get more familiar with the Windows toolchain, I ported some of Thomas Braibant's instructions for compiling OPAM on Windows using it here:
>
> Cygwin scripts: https://github.com/ocaml/opam/blob/master/appveyor.yml
> Build output: https://ci.appveyor.com/project/avsm/opam/build/1.0.38
>
> Appveyor can be used much like Travis and build every Git checkin on Windows, except that they unfortunately overwrite each other's status flags (the green tick or red cross against each commit), so they cannot be simultaneously used on one GitHub repository right now. I contacted GitHub support and they indicated that they are adding support for multiple CI tools into the UI, but do not have a time estimate for when that would be ready.
I recently learnt of a solution to this issue: there's a third party
application which makes it possible to display both Travis and
AppVeyor build status flags on each commit:
http://help.appveyor.com/discussions/kb/4-show-multiple-statuses-in-github-pull-requests
For example, on the following pull request
https://github.com/yallop/ci-testing/pull/1
the status currently reads
"Waiting to hear about 7e7a1ac — The Travis CI build passed /
Waiting for AppVeyor build to complete"
and links to a page with links to both the Travis and AppVeyor builds:
http://github-multi-status.herokuapp.com/view?owner=yallop&repo=ci-testing&sha=7e7a1ac397a6eb3a5dc8937db4ea875617790280
next prev parent reply other threads:[~2014-10-09 9:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 8:56 William
2014-06-09 9:13 ` Virgile Prevosto
2014-06-09 9:16 ` John Whitington
2014-06-09 12:06 ` Yotam Barnoy
2014-06-09 12:26 ` Matthieu Dubuget
2014-06-09 15:23 ` David Allsopp
2014-06-09 18:59 ` Yaron Minsky
2014-06-09 19:34 ` Sebastien Mondet
2014-06-09 20:06 ` Yaron Minsky
2014-06-10 9:53 ` Thomas Gazagnaire
2014-10-05 22:14 ` Anil Madhavapeddy
2014-10-09 9:33 ` Jeremy Yallop [this message]
2014-12-10 9:57 ` Anil Madhavapeddy
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='CAAxsn=GJZmvnXiAoZ2kc+KJ8AXZwwBjoBwQm1bbUGtmdr2_BgA@mail.gmail.com' \
--to=yallop@gmail.com \
--cc=anil@recoil.org \
--cc=caml-list@inria.fr \
--cc=dra-news@metastack.com \
/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).