From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 286E87F02D for ; Thu, 9 Oct 2014 11:33:55 +0200 (CEST) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of yallop@gmail.com) identity=pra; client-ip=209.85.212.179; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="yallop@gmail.com"; x-sender="yallop@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of yallop@gmail.com designates 209.85.212.179 as permitted sender) identity=mailfrom; client-ip=209.85.212.179; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="yallop@gmail.com"; x-sender="yallop@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-wi0-f179.google.com) identity=helo; client-ip=209.85.212.179; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="yallop@gmail.com"; x-sender="postmaster@mail-wi0-f179.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AnIBAKVVNlTRVdSzm2dsb2JhbABfg2FYBIMCyAYOh0kCfwgWAREBAQEBAQYLCwkULIQEAQEEAQIPER0BGx0BAwwGBQsNAgImAgIiAREBBQEOAQ0GExsHiAcBAxENpQluizCBcoMQiAsKGScNZ4YEAREBBQ6BHo5lMweCd4FUBZY1gkKEToFqkjEYKYUVPC8BAQOCRQEBAQ X-IPAS-Result: AnIBAKVVNlTRVdSzm2dsb2JhbABfg2FYBIMCyAYOh0kCfwgWAREBAQEBAQYLCwkULIQEAQEEAQIPER0BGx0BAwwGBQsNAgImAgIiAREBBQEOAQ0GExsHiAcBAxENpQluizCBcoMQiAsKGScNZ4YEAREBBQ6BHo5lMweCd4FUBZY1gkKEToFqkjEYKYUVPC8BAQOCRQEBAQ X-IronPort-AV: E=Sophos;i="5.04,683,1406584800"; d="scan'208";a="100180677" Received: from mail-wi0-f179.google.com ([209.85.212.179]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 09 Oct 2014 11:33:54 +0200 Received: by mail-wi0-f179.google.com with SMTP id d1so1183923wiv.6 for ; Thu, 09 Oct 2014 02:33:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=vJ5Qbvpzb0eKoDXPFBAawQsBFmJioPZE9EkCarj9IiM=; b=JcoXj2sqGDmG3CaPrMA3xPciKXm868gc7iTuCiQcF924htJ/zgjYkNORdSBkSgjEfk vxTLgIlrvHPW9tjb4noilfgod5Nxu6iHav9niVWQ+m473SSkkfMIjZcmayAWUThY5hAE 860eLFsMKjVGfJZuQl/4m29aWGuTyze9CtT+k4cV7Pw53I33E0FAqSi4hEQOhFiKVpR9 UJfm0DnVVF4FhRQ+GJLw7tmW/W48APkmSJMwK+R6NyOZE4CewzK+vziHK3EET/k92zXU meZLZzk2l8C0DUfzbjb/ZkcpSK5Zb/4VmUrrdCAQB3LJUrbB6ibs0eBerADohV6M2q6z 3Vpg== MIME-Version: 1.0 X-Received: by 10.180.20.46 with SMTP id k14mr108705wie.26.1412847234667; Thu, 09 Oct 2014 02:33:54 -0700 (PDT) Received: by 10.217.129.194 with HTTP; Thu, 9 Oct 2014 02:33:54 -0700 (PDT) In-Reply-To: References: Date: Thu, 9 Oct 2014 10:33:54 +0100 Message-ID: From: Jeremy Yallop To: Anil Madhavapeddy Cc: David Allsopp , "caml-list@inria.fr" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Caml-list] Thoughts on targeting windows On 5 October 2014 23:14, Anil Madhavapeddy wrote: > At a recent compiler hacking session in Cambridge, Don Syme pointed out a= great Travis-like service for running regular Windows builds called Appvey= or(.com). In order to get more familiar with the Windows toolchain, I port= ed some of Thomas Braibant's instructions for compiling OPAM on Windows usi= ng 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 Wind= ows, except that they unfortunately overwrite each other's status flags (th= e green tick or red cross against each commit), so they cannot be simultane= ously 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-gith= ub-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 =E2=80=94 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=3Dyallop&repo=3Dci-t= esting&sha=3D7e7a1ac397a6eb3a5dc8937db4ea875617790280