[issue33522] Enable CI builds on Visual Studio Team Services

Steve Dower added the comment: GitHub has broken CSS everywhere right now :) Their oauth page doesn't show scroll bars either, which means you can't get to the "authorise" button if you're in more than a couple of organisations. --

[issue33522] Enable CI builds on Visual Studio Team Services

Change by Gregory P. Smith : -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker ___

[issue33522] Enable CI builds on Visual Studio Team Services

Gregory P. Smith added the comment: I've emailed support@github on this one. Their UI is horrible, "show all checks" does not show them all. It shows five at most. It is an invisible scrolling region. We're forced to manually mouse over and scroll down in that region in

[issue33522] Enable CI builds on Visual Studio Team Services

Steve Dower added the comment: > I don't think there's a way to make certain checks like VSTS be optional and > not show up with a red cross on Github Most of the failures I've seen have been reproducible, so I suspect they're due to race conditions that rarely

[issue33522] Enable CI builds on Visual Studio Team Services

Steve Dower added the comment: > * is there more computers for the tests on VSTS? I don't know what Travis is giving us, but Microsoft has provided 20 concurrent builds. They also seem to be more powerful machines, though some caching features are missing and many

[issue33522] Enable CI builds on Visual Studio Team Services

Stéphane Wirtel added the comment: Hi Steve I just saw VSTS in action, it's a great job, thank you. Compared to Travis-CI: * is there more computers for the tests on VSTS? * with time, what will be the reference if there is a 'green' build? TravisCI or VSTS? Thank you

[issue33522] Enable CI builds on Visual Studio Team Services

Ammar Askar added the comment: >core-workflow made a premature decision to turn off Travis and AppVeyor and >make VSTS blocking. It looks like AppVeyor and Travis are still running as of the latest PR: https://github.com/python/cpython/pull/6965 Annoyingly, I don't

[issue33522] Enable CI builds on Visual Studio Team Services

Gregory P. Smith added the comment: Your PRs made modifications to code and did not include a useful commit message or appropriate NEWS entries for the code modifications. Further, VSTS is unreliable. core-workflow made a premature decision to turn off Travis and AppVeyor

[issue33522] Enable CI builds on Visual Studio Team Services

Steve Dower added the comment: This is implemented and merged now. I'll leave it to core-workflow to decide whether and when to make the builds required and/or reduce use of Travis/AppVeyor. -- resolution: -> fixed stage: patch review -> resolved

[issue33522] Enable CI builds on Visual Studio Team Services

Steve Dower added the comment: New changeset 0d8f83f59c8f4cc7fe125434ca4ecdcac111810f by Steve Dower in branch '3.6': bpo-33522: Enable CI builds on Visual Studio Team Services (GH-6865) (GH-6925)

[issue33522] Enable CI builds on Visual Studio Team Services

Steve Dower added the comment: New changeset 8965d75c90e80b6983b36f3ae9601d6a257d782b by Steve Dower (Miss Islington (bot)) in branch '3.7': bpo-33522: Enable CI builds on Visual Studio Team Services (GH-6865) (GH-6926)

[issue33522] Enable CI builds on Visual Studio Team Services

Change by miss-islington : -- pull_requests: +6596 ___ Python tracker ___

[issue33522] Enable CI builds on Visual Studio Team Services

Change by Steve Dower : -- pull_requests: +6595 ___ Python tracker ___ ___

[issue33522] Enable CI builds on Visual Studio Team Services

Steve Dower added the comment: New changeset e5f41d2f1e0b8b8e61d5fa427c19bd1ea90fd9a3 by Steve Dower in branch 'master': bpo-33522: Enable CI builds on Visual Studio Team Services (#6865) https://github.com/python/cpython/commit/e5f41d2f1e0b8b8e61d5fa427c19bd1ea90fd9a3

[issue33522] Enable CI builds on Visual Studio Team Services

Change by miss-islington : -- keywords: +patch pull_requests: +6593 stage: -> patch review ___ Python tracker

[issue33522] Enable CI builds on Visual Studio Team Services

Brett Cannon added the comment: https://www.visualstudio.com/team-services/ It's Microsoft's GitHub hosting, issue tracking, and CI/CD platform. -- ___ Python tracker

[issue33522] Enable CI builds on Visual Studio Team Services

Antoine Pitrou added the comment: Can you explain what Visual Studio Team Services is? -- nosy: +pitrou ___ Python tracker ___

[issue33522] Enable CI builds on Visual Studio Team Services

New submission from Steve Dower : We have been provided with https://python.visualstudio.com/cpython and a measure of build machines to help us run continuous integration builds. The benefits are more reliable builds (especially Mac and Windows) and higher parallelism