Skip to content

Remove Appveyor and add Azure build status branch protection #268

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

Closed
gusmith opened this issue Jul 4, 2019 · 3 comments
Closed

Remove Appveyor and add Azure build status branch protection #268

gusmith opened this issue Jul 4, 2019 · 3 comments
Assignees

Comments

@gusmith
Copy link
Contributor

gusmith commented Jul 4, 2019

Currently, a commit can be merged if it receives the appveyor build status continuous-integration/appveyor/pr.
But we are not replacing appveyor with Azure Build pipeline (merged in master with PR #262), so we should change the branch protection and change the appveyor configuration not to build the project anymore.

@hardbyte
Copy link
Collaborator

hardbyte commented Aug 5, 2019

I've added the Azure checks and removed the requirement for appveyor:

image

This issue is therefore to remove the appveyor configuration then?

gusmith pushed a commit that referenced this issue Aug 7, 2019
@MehdiGol
Copy link

MehdiGol commented Oct 7, 2021

Hello, Can I ask a question?
Why did you migrate from AppVeyor to Azure?

@gusmith
Copy link
Contributor Author

gusmith commented Oct 8, 2021

Hi @MehdiGol
I can only mentioned what I remember, which is not that much as it happened a few years ago now, but at the time, Azure had really great offers for open source projects to run CI and CD (number of parallel jobs, time to get a worker, etc).
From memory, we found that AppVeyor was quite slow (e.g. #121) but I do not remember well the details... was it time to get a worker? Was it the worker resources which were a bit small?
Hoping that help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants