[python-committers] Visual Studio Team Services checks on pullrequests (original) (raw)

Antoine Pitrou antoine at python.org
Thu May 17 10:14:55 EDT 2018

Le 17/05/2018 à 16:07, Steve Dower a écrit :

Okay, now that it's morning and I have coffee, here's a full update on what I've been doing (those at the language summit have heard some of this already).

Visual Studio Team Services is Microsoft's integrated code/build/release infrastructure service. The official marketing page is https://www.visualstudio.com/team-services/ but you can think of it as github code+github issues+Travis but engineered for huge teams (i.e. Microsoft keeps all of Windows in git, all the millions of issues they have, and all the builds they do, are in VSTS and it scales to thousands of developers just fine). I've been working with the team to improve their Python support and generally raise awareness of the new service, and one of the things they agreed to is to provide a free set of build machines for CPython. These allow us to run up to 20 simultaneous Windows, macOS and Linux builds with no other limits.

That sounds cool. Which builds are you looking to migrate to VSTS? macOS sounds like a no-brainer as the Travis-CI macOS infrastructure is known to be very lacking (though it has been a bit better lately). Windows may be reasonable since AppVeyor doesn't provide any parallelism AFAIK. As for Linux, I think it may be better to keep some of our CI on Travis (if only not to depend entirely on a donated service).

Also a concern: currently the Travis-CI and AppVeyor configurations also work, transparently, on user's forks as long as they activated those (free) services on their fork. What about VSTS, though? If CPython were to migrate all of its CI to VSTS, would I still get CI on my CPython fork?

Regards

Antoine.

More information about the python-committers mailing list