Re: [PATCH 0/9] Offer to run CI/PR builds in Visual Studio Team Services
- From
Stefan Beller <sbeller@google.com>
- Date
- Sep 5, 2018, 19:08 UTC
- Message-ID
- <CAGZ79kZiA+0R6QB5qgVDUSZBZp_Nv+Yi-SQC5yHeWTzJnw1y8w@mail.gmail.com>
- In-Reply-To
- <25914342-ff35-90b2-860e-6aff5c109f14@gmail.com>
On Wed, Sep 5, 2018 at 12:02 PM Sebastian Schuberth <sschuberth@gmail.com> wrote:
Show 11 quoted lines
> > On 9/3/2018 11:10 PM, Johannes Schindelin via GitGitGadget wrote: > > > The one sad part about this is the Windows support. Travis lacks it, and we > > work around that by using Visual Studio Team Services (VSTS) indirectly: one > > phase in Travis would trigger a build, wait for its log, and then paste that > > log. > > I'm sorry if this has been discussed before, but as this recap doesn't > mention it: Has AppVeyor been considered as an option? It seems to be > the defacto standard for Windows CI for projects on GitHub.
There was https://public-inbox.org/git/BAY169-W30CD27F2F7606F4DF52944A78F0@phx.gbl/ and https://public-inbox.org/git/alpine.DEB.2.20.1703241242210.17768@tvnag.unkk.fr/