Re: [PATCH 0/9] Offer to run CI/PR builds in Visual Studio Team Services

From: Sebastian Schuberth <sschuberth@gmail.com>
Date: Sep 5, 2018, 19:01 UTC
Message-ID: <25914342-ff35-90b2-860e-6aff5c109f14@gmail.com>
In-Reply-To: <pull.31.git.gitgitgadget@gmail.com>

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.

-- 
Sebastian Schuberth

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.