You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
New pipelines - runtime-ioslike-coreclr, and runtime-ioslike-mono were added in #87260 . But they are missing any conditions for running, which means they run on PRs with no related changes.
For example on a wasm-only PR, like #88980 .
We control the jobs running on wasm-only PRs tightly through conditions based on path triggers in eng/pipelines/common/evaluate-default-paths.yml. Similar checks, and conditions can be used for the new pipelines too. Or at least to not trigger in case for wasm-only PRs. I can also help with picking the conditions for this.
Tagging subscribers to this area: @directhex
See info in area-owners.md if you want to be subscribed.
Issue Details
New pipelines - runtime-ioslike-coreclr, and runtime-ioslike-mono were added in #87260 . But they are missing any conditions for running, which means they run on PRs with no related changes.
For example on a wasm-only PR, like #88980 .
We control the jobs running on wasm-only PRs tightly through conditions based on path triggers in eng/pipelines/common/evaluate-default-paths.yml. Similar checks, and conditions can be used for the new pipelines too. Or at least to not trigger in case for wasm-only PRs. I can also help with picking the conditions for this.
New pipelines -
runtime-ioslike-coreclr
, andruntime-ioslike-mono
were added in #87260 . But they are missing any conditions for running, which means they run on PRs with no related changes.For example on a wasm-only PR, like #88980 .
We control the jobs running on wasm-only PRs tightly through conditions based on path triggers in
eng/pipelines/common/evaluate-default-paths.yml
. Similar checks, and conditions can be used for the new pipelines too. Or at least to not trigger in case for wasm-only PRs. I can also help with picking the conditions for this.cc @kotlarmilos @steveisok @lewing
The text was updated successfully, but these errors were encountered: