8000 Reintroduce support for building VMR from repo PR/CI by NikolaMilosavljevic · Pull Request #548 · dotnet/dotnet · GitHub
[go: up one dir, main page]

Skip to content

Reintroduce support for building VMR from repo PR/CI #548

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

Conversation

NikolaMilosavljevic
Copy link
Member
@NikolaMilosavljevic NikolaMilosavljevic commented May 14, 2025

Contributes to: dotnet/arcade-services#4539

This PR is basically bringing back support for VMR builds that are launched from individual repos, and not from VMR. It essentially reverts the removal of isBuiltFromVmr property and associated logic, that was done with: #226

Additionally there are few tweaks:

  • We only use a single template now for vmr-sync steps: vmr-pull-updates.yml. The template is referenced using @self and resolved from repo sources.
  • I've removed 2 usages of @self, in template references, as they were unnecessary

Vmr syncing template and scripts will live in repo sources, under eng/common and will be provided to all repos via arcade updates.

Full verification build: https://dev.azure.com/dnceng/internal/_build/results?buildId=2708573&view=results There is a known failure in source-build poison tests, that exists in the baseline as well.

@NikolaMilosavljevic NikolaMilosavljevic requested review from a team as code owners May 14, 2025 14:35
@@ -68,7 +68,7 @@ function InstallDarcCli {
fi
fi

local arcadeServicesSource="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-tools/nuget/v3/index.json"
local arcadeServicesSource="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-eng/nuget/v3/index.json"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes to eng/common must not be made in the VMR. You probably want to make this change in src/arcade/eng/common/darc-init.sh (which probably is already done). That's the location that flows to repos in and outside of the VMR.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK. I'll remove this. Yeah, the change is already in arcade.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed with 0734954

@ViktorHofer ViktorHofer requested review from premun and a team May 14, 2025 15:24
@@ -311,6 +322,13 @@ jobs:
sbomEnabled: false

steps:
- ${{ if not(parameters.isBuiltFromVmr) }}:
# Synchronize new content in the VMR during PRs (we expect this to come
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This comment doesn't seem complete.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, it was the original comment I brought back along with the surrounding code. I'll remove the content in parenthesis as it doesn't add any value.

Here's the same comment in P4 branch:

# Synchronize new content in the VMR during PRs (we expect this to come

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixes with 9981a4f

@NikolaMilosavljevic
Copy link
Member Author

PR checks are hitting known NuGet Audit errors - will likely need to wait until #546 is merged before rerunning checks.

@NikolaMilosavljevic NikolaMilosavljevic merged commit 094631c into dotnet:main May 15, 2025
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
0