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

Move APIScan to its own pipeline #256

Open
AArnott opened this issue Feb 21, 2024 · 1 comment
Open

Move APIScan to its own pipeline #256

AArnott opened this issue Feb 21, 2024 · 1 comment

Comments

@AArnott
Copy link
Owner

AArnott commented Feb 21, 2024

APIScan is very slow and nowadays is (suitably) non-blocking to PRs and CIs. We should move it to its own pipeline (as I've done in vs-green already) that has a schedule trigger.

@AArnott
Copy link
Owner Author

AArnott commented Feb 21, 2024

Alternatively to make failures more noticeable, leave it turned on for signed builds, since folks don't usually wait for those to complete, but they definitely notice when they malfunction.

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

1 participant