-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
[mono] Create separate yml that can trigger full test runs on demand #61132
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to this area: @directhex Issue DetailsSince a large share of the mono configurations are now running only smoke tests on each PR, we need to have a way to manually trigger running all tests. A copy of runtime.yml that can only be manually triggered is probably the easiest option, but I'm sure there are others. An engineer should be able to trigger a full test run via
|
Can it be nested like |
Yeah you can nest templates, basically like we use the |
The jobs can now be triggered via |
Since a large share of the mono configurations are now running only smoke tests on each PR, we need to have a way to manually trigger running all tests. A copy of runtime.yml that can only be manually triggered is probably the easiest option, but I'm sure there are others.
An engineer should be able to trigger a full test run via
/azp run <yet-to-be-named.yml>
The text was updated successfully, but these errors were encountered: