Skip to content
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 Pipelines #468

Merged
merged 1 commit into from Jul 4, 2019
Merged

Switch to Azure Pipelines #468

merged 1 commit into from Jul 4, 2019

Conversation

sloria
Copy link
Member

@sloria sloria commented Jul 4, 2019

NOTE: This removes builds against apispec-webframeworks, as there's no way in AP to allow failures yet (microsoft/azure-pipelines-tasks#9302)

NOTE: This removes builds against apispec-webframeworks
@sloria
Copy link
Member Author

sloria commented Jul 4, 2019

The allow_failures in TravisCI was always a half-baked solution for us anyway, since it wasn't apparent when the webframeworks build failed unless you happen to look at the build details.

I think we can get most of the way by running the apispec-webframeworks pipeline on a regular schedule (e.g. nightly).

@lafrech Let me know if you have any issues with this.

@sloria
Copy link
Member Author

sloria commented Jul 4, 2019

Current build failures are expected. I'll fix the marshmallow 3 compatibility in a separate PR.

@sloria sloria merged commit 357023d into dev Jul 4, 2019
@sloria sloria deleted the azure-pipelines branch July 4, 2019 20:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant