Skip to content

Disable scheduled builds for release/9.4#14448

Open
Copilot wants to merge 3 commits intorelease/9.4from
copilot/disable-scheduled-builds-release-9-4
Open

Disable scheduled builds for release/9.4#14448
Copilot wants to merge 3 commits intorelease/9.4from
copilot/disable-scheduled-builds-release-9-4

Conversation

Copy link
Contributor

Copilot AI commented Feb 11, 2026

Description

Scheduled builds for release/9.4 branch consume CI resources unnecessarily. This branch is old and should not trigger weekly builds.

Changes:

  • eng/pipelines/azure-pipelines-public.yml: Completely removed the schedules: section to disable all scheduled builds
  • eng/pipelines/azure-pipelines-codeql.yml: Completely removed the schedules: section to disable all scheduled builds

Manual and PR-triggered builds remain functional.

Checklist

  • Is this feature complete?
    • Yes. Ready to ship.
    • No. Follow-up changes expected.
  • Are you including unit tests for the changes and scenario tests if relevant?
    • Yes
    • No
  • Did you add public API?
    • Yes
      • If yes, did you have an API Review for it?
        • Yes
        • No
      • Did you add <remarks /> and <code /> elements on your triple slash comments?
        • Yes
        • No
    • No
  • Does the change make any security assumptions or guarantees?
    • Yes
      • If yes, have you done a threat model and had a security review?
        • Yes
        • No
    • No
  • Does the change require an update in our Aspire docs?
Original prompt

Repository: dotnet/aspire

Task: Disable scheduled builds for Azure DevOps (AzDO) pipelines for branch release/9.4.

Context:

  • These branches are old and should no longer produce new scheduled builds.
  • We need to disable scheduled builds (cron/scheduled triggers) for AzDO pipelines affecting this branch.

Requirements:

  1. Identify AzDO pipeline YAML definitions in the repository that define scheduled triggers (e.g., schedules: or trigger:/pr: with schedules) that apply to the release/9.4 branch.
  2. Update the relevant pipeline YAML so that scheduled triggers do not run for release/9.4.
    • Prefer adding branch exclusions under schedules or removing the branch from schedule include lists.
    • Ensure normal CI triggers (manual/PR) remain unaffected unless they are also obsolete for this branch; only scheduled builds must be disabled.
  3. Ensure the change is made on branch release/9.4 and create a pull request targeting release/9.4.
  4. Include a clear PR title and description explaining that scheduled builds are disabled for this old branch.

Deliverables:

  • A PR against dotnet/aspire with changes that disable scheduled builds for branch release/9.4.
  • Mention which pipeline file(s) were changed and how schedules were disabled.

Notes:

  • This request is specifically about AzDO scheduled builds; do not modify GitHub Actions schedules unless they are used to trigger AzDO pipelines in this repository.

This pull request was created from Copilot chat.


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Co-authored-by: radical <1472+radical@users.noreply.github.com>
Copilot AI changed the title [WIP] Disable scheduled builds for release/9.4 branch Disable scheduled builds for release/9.4 Feb 11, 2026
Copilot AI requested a review from radical February 11, 2026 20:40
@radical
Copy link
Member

radical commented Feb 11, 2026

@copilot remove the scheduled runs for this branch completely.

Co-authored-by: radical <1472+radical@users.noreply.github.com>
Copy link
Contributor Author

Copilot AI commented Feb 11, 2026

@copilot remove the scheduled runs for this branch completely.

Done. Removed the entire schedules: sections from both pipeline files in commit 5cd0858.

Changes:

  • eng/pipelines/azure-pipelines-public.yml: Removed weekly Monday build schedule completely
  • eng/pipelines/azure-pipelines-codeql.yml: Removed weekly CodeQL schedule completely

The pipelines now have no scheduled builds on this branch. Manual and PR-triggered builds remain functional via the trigger: none and pr: configurations.

@github-actions
Copy link
Contributor

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 14448

Or

  • Run remotely in PowerShell:
iex "& { $(irm https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 14448"

@radical radical marked this pull request as ready for review February 11, 2026 21:19
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Disables Azure DevOps scheduled (cron) runs on the release/9.4 branch to avoid consuming CI resources for an old release branch, while keeping non-scheduled execution paths unchanged.

Changes:

  • Removed the schedules: trigger from the public pipeline YAML on release/9.4.
  • Removed the schedules: trigger from the CodeQL pipeline YAML on release/9.4.
  • Left existing trigger: none / PR behavior as-is.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
eng/pipelines/azure-pipelines-public.yml Removes weekly schedule so the public pipeline no longer runs on a timer on release/9.4.
eng/pipelines/azure-pipelines-codeql.yml Removes weekly schedule so CodeQL is no longer run on a timer on release/9.4.

@joperezr
Copy link
Member

Is this the right way to disable the builds? I thought this change needed to go to main, given the azdo pipeline looks at the yaml at that branch for triggers. Can you double check just to make sure we actually need to chage every release branch? (I want to avoid rebuilding a branch in ADO we have declared as dead as that could carry SFI items.

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