-
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
Move CoreCLR community platforms to build with the global build template #91646
Conversation
… leg. This makes our community-supported platform testing story consistent (we do all testing of community-supported targets in the runtime-community pipeline and none in the runtime pipeline) and allows us to remove more custom code from the CoreCLR build-job.yml file.
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsThis makes our community-supported platform testing story consistent (we do all testing of community-supported targets in the runtime-community pipeline and none in the runtime pipeline) and allows us to remove more custom code from the CoreCLR build-job.yml file. Alternatively, we could keep running these legs in the runtime.yml file and just do the move to the global-build-job template.
|
/azp run runtime-community |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-community |
Azure Pipelines successfully started running 1 pipeline(s). |
runtime-community is optional pipeline for targets that are too expensive and/or too flaky to run unconditionally. It includes tests. We have build for linux-x86 and linux-armel in the unconditional pipeline to catch the trivial linux-x86 and linux-armel build breaks. The idea is that the build-only leg for linux-x86 and linux-armel is cheap enough and reliable enough to make it worth run unconditionally - it saves us from having to deal with the boring "fix build break" PRs. |
Sounds good 👍 |
…e OS for tizen, see if that helps.
Jobs have been moved back into the runtime pipeline and fixed to pass. |
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, thanks Jeremy!
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.
Thank you
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.
Thank you 👍
Failures are all known. |
This makes our community-supported platform testing story consistent (we do all testing of community-supported targets in the runtime-community pipeline and none in the runtime pipeline) and allows us to remove more custom code from the CoreCLR build-job.yml file.
Alternatively, we could keep running these legs in the runtime.yml file and just do the move to the global-build-job template.