-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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 runtime-wasm
pipeline
#64830
Add runtime-wasm
pipeline
#64830
Conversation
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries Issue DetailsThis adds support for a When
When
On rolling builds,
|
This is the new state:
PR:
Rolling build:
There is an existing inconsistency in rolling builds:
|
/azp run wasm-only |
Azure Pipelines failed to run 1 pipeline(s). |
/azp run wasm-only |
Azure Pipelines failed to run 1 pipeline(s). |
/azp run wasm-only |
Azure Pipelines failed to run 1 pipeline(s). |
/azp run wasm-only |
Azure Pipelines failed to run 1 pipeline(s). |
/azp run wasm-only |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run wasm-only |
Azure Pipelines failed to run 1 pipeline(s). |
/azp run wasm-only |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run wasm-only |
Azure Pipelines failed to run 1 pipeline(s). |
/azp run wasm-only |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run wasm-only |
Azure Pipelines successfully started running 1 pipeline(s). |
May I suggest that we name it |
/azp run runtime-wasm,runtime-extra-platforms |
Azure Pipelines failed to run 2 pipeline(s). |
@@ -13,7 +13,7 @@ variables: | |||
- template: /eng/pipelines/common/variables.yml | |||
|
|||
- ${{ if eq(variables.isNotSpecificPlatformOnlyBuild, true) }}: |
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.
I don't think expand time conditions work for schedules. We would have to go to the AzDo UI for this pipeline and override the CI triggers/schedule.
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.
I don't think it'll work either.
If you want such a behavior and not use AzDo UI, I think you'd have to make a template and then have two pipelines. One with a schedule and one w/o.
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.
I disabled it from the UI for runtime-wasm
specifically.
/azp run runtime-wasm,runtime-extra-platforms |
Azure Pipelines successfully started running 2 pipeline(s). |
Merging main to pick up some test fixes for Android. |
/azp run runtime-extra-platforms |
Azure Pipelines successfully started running 1 pipeline(s). |
Anything else needed for this PR? |
@radical love the table overview! |
Does it need to be reflected in somewhere in docs, e.g. https://github.com/dotnet/runtime/blob/main/docs/pr-builds.md ? |
I can add it in a follow up PR. |
This adds support for a
runtime-wasm
pipeline, which usesruntime-extra-platforms.yml
.The wasm jobs have been moved to
runtime-extra-platforms-wasm.yml
, andthe rest to
runtime-extra-platforms-other.yml
. And the two files areincluded conditionally.
Effectively, this still runs all these jobs when
runtime-extra-platforms
is run (same as before). But it allows runningjust the wasm jobs, triggered manually with:
When
runtime-wasm
is manually run:When
runtime-extra-platforms
is manually run:On rolling builds,
runtime-extra-platforms
runs by default:With feedback from @steveisok, and @safern.