-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Add a new wrapper runtime-wasm.yml
to be used from azdo
#65032
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
Conversation
Currently, we have `runtime-wasm` in azdo pointing to `runtime-extra-platforms.yml`, which has some scheduled triggers defined. azdo seems to use these for running `runtime-wasm` too. Instead, in azdo use a new `runtime-wasm.yml` for `runtime-wasm` pipeline, so we can explicitly avoid the scheduled triggers. This yml just uses the existing `runtime-extra-platforms-wasm.yml`.
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsCurrently, we have Instead, in azdo use a new
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@safern do we need to wait for the builds to complete before merging this one? |
It seems like |
Ah, you need to import the variables template 😄 |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
Failures are unrelated. |
Currently, we have
runtime-wasm
in azdo pointing toruntime-extra-platforms.yml
, which has some scheduled triggersdefined. azdo seems to use these for running
runtime-wasm
too.Instead, in azdo use a new
runtime-wasm.yml
forruntime-wasm
pipeline, sowe can explicitly avoid the scheduled triggers. This yml just uses the
existing
runtime-extra-platforms-wasm.yml
.