Move source-build container to Azure Linux 4 after Arcade trailing-backslash fix
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- azure, csharp, github-actions
- Domain
- build-system, ci-cd
Research direction
Read the fix in dotnet/arcade#17800 and check that it has reached aspnetcore through an Arcade update. Then inspect .azure/pipelines/ci.yml and .azure/pipelines/ci-public.yml and update the source-build containers to the Azure Linux 4 image named in the issue. Done when both source-build jobs use that image and the source-build job no longer fails with the trailing-backslash argument.
Written by the indexing model from the issue text.
Description
dotnet/aspnetcore#70522 moves aspnetcore's build and cross containers to Azure Linux 4. The source-build job stays on azurelinux-3.0-net11.0-cross-amd64 for now because it fails on Azure Linux 4.
Cause: Arcade's eng/common/core-templates/steps/source-build.yml ends the build command with a trailing line continuation ($portableBuildArgs \). Azure Pipelines trims the script, so the generated file ends with a backslash and no newline:
- bash 5.2.15 (Azure Linux 3) drops the backslash.
- bash 5.3.9 (Azure Linux 4) passes a literal
\argument tobuild.sh, and the build fails:
+ ./eng/build.sh --ci --configuration Release --restore --build --pack -bl --source-build --source-build -p:CrossBuild=true '\'
MSBUILD : error MSB1008: Only one project can be specified.
Fix in Arcade: https://github.com/dotnet/arcade/pull/17800 (dotnet/arcade#17800)
Follow-up: after that fix reaches aspnetcore through an Arcade update, move the source-build container to Azure Linux 4:
.azure/pipelines/ci.yml:azureLinuxCrossX64→mcr.microsoft.com/dotnet-buildtools/prereqs:azurelinux-4.0-net11.0-cross-amd64.azure/pipelines/ci-public.yml: the source-build job'scontainer→ same image
[!NOTE]
This issue was generated with the help of GitHub Copilot.
- Dominant language
- C#
- Stars
- 38.5k
- Forks
- 12.3k
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 283
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/aspnetcore
-
[OpenTelemetry] Hosting replaces an Activity.DisplayName that the app set, when a route matchesOpenarea-hosting Regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dotnet/aspnetcore#70516 · 1 comment ·
Maintainers usually reply within 1 day
-
[SSE] ServerSentEventsResult.WrapEvents is missing [EnumeratorCancellation], so RequestAborted never reaches the app's generator on the IAsyncEnumerable<T> overloadPossibly taken @bharatprajapati-coder claimed this today. Openarea-minimal
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dotnet/aspnetcore#70419 · 2 comments ·
Maintainers usually reply within 1 day
-
[Blazor] DefaultInMemoryCircuitPersistenceProvider never disposes the retention CancellationTokenSource when a persist is rejected at capacityPossibly taken @Vinoth2562000 claimed this today. Openarea-blazor
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
dotnet/aspnetcore#70418 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
FieldIdentifier.Create throws ArgumentException when an indexer argument is a captured long, Guid or other non-int value typePossibly taken @Yuvan111 claimed this 1 day ago. Openarea-blazor NativeAOT
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
dotnet/aspnetcore#70406 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dotnet/aspnetcore#70370 ·
Maintainers usually reply within 1 day
All issues in dotnet/aspnetcore
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
openrewrite/rewrite#9835 ·
Maintainers usually reply within 1 day
-
Same-repo PRs never get the required appveyor/pr checkPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 74/100
activescott/lessmsi#309 · 3 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
corvus-dotnet/Corvus.JsonSchema#1068 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100