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

Switch to Azure for Windows CI #1838

Open
sgrif opened this Issue Sep 10, 2018 · 4 comments

Comments

Projects
None yet
4 participants
@sgrif
Member

sgrif commented Sep 10, 2018

https://azure.microsoft.com/en-us/blog/announcing-azure-pipelines-with-unlimited-ci-cd-minutes-for-open-source/

Appveyor has consistently been painful and slow for us to use, I'd like to look at whether Azure's CI option is an improvement.

@weiznich

This comment has been minimized.

Contributor

weiznich commented Sep 11, 2018

The first point in the getting started there mentions that we could not just reuse the github org, but have to create a new one there:

You need an Azure DevOps organization. If you don't have one, you can create one for free. If your team already has one, then make sure you're an administrator of the project you want to use.

@RaleighHokie

This comment has been minimized.

RaleighHokie commented Sep 14, 2018

You would still use your GitHub org, no need to migrate that, in that step you are creating an organization in Azure DevOps (our top level container is also called an organization) that you would then use to build your existing GitHub org with Azure Pipelines.

@jeremyepling

This comment has been minimized.

jeremyepling commented Sep 14, 2018

@sgrif / @weiznich , I updated our docs to clarify that an Azure DevOps organization is different than a GitHub organization. People often use the same name for both so there's alignment between then.

Taojunshen pushed a commit to MicrosoftDocs/vsts-docs that referenced this issue Sep 14, 2018

Merged PR 385133: Clarify organizations in our prerequisites
Our mentioning of "organization" in the prerequisite docs make people think they have to create a new GitHub organization instead of an AzDev organization.  See diesel-rs/diesel#1838.  What do you think about clarifying this in the way proposed by this PR?
@weiznich

This comment has been minimized.

Contributor

weiznich commented Oct 12, 2018

I've started playing with this a bit. Got something working here, but it seems like I got not everything setup right in the ci, because "some" jobs fail :(

@weiznich weiznich referenced a pull request that will close this issue Oct 19, 2018

Open

Play with azure-pipeline #1889

2 of 2 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment