[release/6.0] Add runtime-community.yml pipeline and add s390x job #62808
Conversation
(cherry picked from commit 5f3062d)
This was a copy-paste mistake, see dotnet#60255 (comment) (cherry picked from commit 49cf05c)
|
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries Issue DetailsBackport of #60255 and #60351 to release/6.0 Customer ImpactIBM have released .NET 6 on IBM Z (s390x architecture) as part of the RHEL 8 release, but currently have no way to CI the 6.0 branch, only main. This change enables them to test changes in time for fixes to happen TestingIt enables a whole CI lane, so lots of testing. RiskLow, this should only affect IBM (and add a small overhead for building the additional lane). The runtime-community lanes should fail green so it shouldn't risk breaking our builds if a test run fails.
|
|
@akoeplinger I think I missed something, the s390x branch was skipped by runtime-community.yml. Any obvious signs? |
|
@directhex when ready could you please send mail direct to tactics for approval? since M2's are on vac in some cases. |
|
Yeah, held off on sending an email until I got the yml figured |
dotnet#60552) It was missed where we set a default value for that variable. (cherry picked from commit 157a8b5)
) Co-authored-by: Stefan Schulze Frielinghaus <[email protected]> (cherry picked from commit 616ace3)
This allows consuming the dotnet host that was just built instead of relying on a downloaded one. We need to move the `host` subset build before the `libs` subset so that the artifacts are available before externals.csproj runs. (cherry picked from commit cab3a63)
|
/azp run runtime-community |
|
Azure Pipelines successfully started running 1 pipeline(s). |
directhex
added
Servicing-approved
|
Approved by Steve Carroll via email |
ghost
locked as resolved and limited conversation to collaborators
Backport of #60255, #60351, #60552, #57566, #58952 to release/6.0
/cc @uweigand
Customer Impact
IBM have released .NET 6 on IBM Z (s390x architecture) as part of the RHEL 8 release, but currently have no way to CI the 6.0 branch, only main. This change enables them to test changes in time for fixes to happen
Testing
It enables a whole CI lane, so lots of testing.
Risk
Low, this should only affect IBM (and add a small overhead for building the additional lane). The runtime-community lanes should fail green so it shouldn't risk breaking our builds if a test run fails.