Uh oh!
There was an error while loading. Please reload this page.
Add a new wrapper runtime-wasm.yml to be used from azdo - #65032
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`.
ghost
commented
Feb 8, 2022
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. |
radical
commented
Feb 8, 2022
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
ghost
commented
Feb 8, 2022
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsCurrently, we have Instead, in azdo use a new
|
radical
commented
Feb 8, 2022
@safern do we need to wait for the builds to complete before merging this one? |
safern
commented
Feb 9, 2022
It seems like |
safern
commented
Feb 9, 2022
Ah, you need to import the variables template 😄 |
radical
commented
Feb 9, 2022
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
radical
commented
Feb 9, 2022
Failures are unrelated. |
Currently, we have
runtime-wasmin azdo pointing toruntime-extra-platforms.yml, which has some scheduled triggersdefined. azdo seems to use these for running
runtime-wasmtoo.Instead, in azdo use a new
runtime-wasm.ymlforruntime-wasmpipeline, sowe can explicitly avoid the scheduled triggers. This yml just uses the
existing
runtime-extra-platforms-wasm.yml.