New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add Azure Pipelines #868
add Azure Pipelines #868
Conversation
@vtbassmatt Thanks Matt! I was literally today considering adding an issue to do this, because I'll be mentoring a sprint this weekend. Of course, now the sprinters don't get to do it. I'll look over this when I have a bit of time, but I appreciate that you've done this. In case you were looking at doing the same thing for setuptools please hold off until after this weekend, since I'd like to offer that as an option for the sprinters. |
@vtbassmatt Is there any way to test the azure pipelines out before landing it in master? I prefer to keep a clean history and if there are any bugs I'd like to fix them before merge. If not, I'll just do the same thing I usually do when setting up new CI - land it in master on a fork and point the CI there until all the tests are passing. |
Er, sorry for the spam, actually I realize now that the demo pipeline is basically already my forked version. One last question - is there no way for me to install the app as the |
@vtbassmatt No worries about "robbing" the sprinters, it will actually probably be good that we're starting with a known-good template, because the I had two more questions:
I will hang out in the gitter in case you want to have a conversation about this in real time, or if you shoot me an e-mail with a phone number, I can call you and we can talk about it. Also, this contribution is already great as is, if you don't have time to go through this stuff with me just let me know and I can figure it out myself. |
Jumping into the Gitter right now |
📣 |
Summary of changes
Hi! I'm a product manager on Azure Pipelines. We've been helping a lot of Python projects move over to Azure Pipelines for continuous integration. There are a few key benefits we offer:
I'm hoping you'll give us a try! The easiest way to get started is to let azure-pipelines.yml land in master, then install the Azure Pipelines app. If that's a bit too much, you can install the app, let it put a dummy azure-pipelines.yml in a branch, then go in and try out the build against this PR's branch. Even even that's too much, you can preview what the output looks like in the demo pipeline I set up.
We offer GitHub Checks integration, build badges , and all the other stuff you'd expect from a CI system. I didn't try to put those into this PR, since you'd want them to go against your actual Azure Pipelines organization rather than my demo.