Skip to content

feat: trigger fresh vhd build on component update - #10028

Open
lilypan26 wants to merge 1 commit into
mainfrom
lily/trigger-vhd-build-on-component-update
Open

lilypan26 wants to merge 1 commit into
mainfrom
lily/trigger-vhd-build-on-component-update

Conversation

@lilypan26

Copy link
Copy Markdown
Contributor

What this PR does / why we need it:
trigger fresh vhd build upon updates to components.json so e2es do not fail validation when expecting newest component version with stale vhd build

Which issue(s) this PR fixes:

Fixes #

@lilypan26
lilypan26 requested review from a team as code owners November 10, 2026 00:27
Copilot AI balanced review requested due to automatic review settings November 10, 2026 00:27
@github-actions

Copy link
Copy Markdown
Contributor

Windows Unit Test Results

  3 files   21 suites   51s ⏱️
789 tests 789 ✅ 0 💤 0 ❌
815 runs  815 ✅ 0 💤 0 ❌

Results for commit faeeab0.

@github-actions

Copy link
Copy Markdown
Contributor

Code Coverage

Package Line Rate Health
test 0% ❌
windows 27% ❌
staging_cse_windows Package 1 71% ➖
debug 0% ❌
provisioningscripts 2% ❌
parts_windows Package 1 73% ➖
Summary 39% (1983 / 7220) ❌

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🟢 Approval recommended

No active review issues are recorded for the component-triggered VHD builds and related documentation changes.

No open issues 🎉

What changed in this PR

This PR triggers fresh VHD builds when component definitions change on main, reducing stale-image mismatches in standalone E2E validation.

Changes:

  • Enables the VHD release pipeline trigger for changes to parts/common/components.json on main.
  • Documents the component-triggered builds and the daily 09:00 UTC build schedule.
File Description
e2e/​README.md Documents when images used by standalone E2E jobs are refreshed.
.pipelines/​.vsts-vhd-builder-release.yaml Adds branch and path filters to trigger builds on component updates.

Review effort: Balanced

@github-actions

Copy link
Copy Markdown
Contributor

Code Coverage

Package Line Rate Health
shellspec spec 30% ❌
Summary 30% (4912 / 16591) ❌

@github-actions

Copy link
Copy Markdown
Contributor

Code Coverage

Package Line Rate Health
github.com/Azure/agentbaker/aks-node-controller 73% ➖
github.com/Azure/agentbaker/aks-node-controller/common 100% ✔
github.com/Azure/agentbaker/aks-node-controller/helpers 68% ➖
github.com/Azure/agentbaker/aks-node-controller/parser 88% ✔
github.com/Azure/agentbaker/aks-node-controller/pkg/gpu 100% ✔
github.com/Azure/agentbaker/aks-node-controller/pkg/nodeconfigutils 92% ✔
github.com/Azure/agentbaker/aks-node-controller/utils 0% ❌
github.com/Azure/agentbaker/apiserver 24% ❌
github.com/Azure/agentbaker/cmd 0% ❌
github.com/Azure/agentbaker/cmd/starter 0% ❌
github.com/Azure/agentbaker/fuzz/api 0% ❌
github.com/Azure/agentbaker/hotfix/render-nodecustomdata 35% ❌
github.com/Azure/agentbaker/pkg/agent 79% ➖
github.com/Azure/agentbaker/pkg/agent/datamodel 77% ➖
github.com/Azure/agentbaker/pkg/agent/toggles 0% ❌
github.com/Azure/agentbaker/pkg/vhdbuilder/datamodel 87% ✔
Summary 76% (6093 / 8041) ➖

This branch has not been deployed

No deployments
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.

2 participants