-
Notifications
You must be signed in to change notification settings - Fork 165
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 "simple ci" to run in all branches, full deployment tests only on specific scenarios. #90
Comments
@hosungsmsft -- I think having a ENV is a good option. We could define a envbar with comma-separated list of branches where full-ci should run. Is that your idea? Just pitching an idea: the main usecase I see for myself would be wanting to run the deployment test at some specific points during the development. To address that, we could even implement detecting "[full ci]" in the commit, similar to what [skip ci] does -- see https://docs.travis-ci.com/user/customizing-the-build#Skipping-a-build |
Yes, having an env var specifying all branches where full CI should be run was what I had in mind. Your "[full ci]" idea feels also useful, and if it's not too hard to implement that, yes, we'd like that too. Thanks for your great suggestion! |
…igger Full CI tests.
Derived form comments on #77
A full CI is expensive to run for every commit/push in any branch, but it is interesting to still run other tests (linting/validation).
The text was updated successfully, but these errors were encountered: