Skip to content

Conversation

@akoeplinger
Copy link
Member

When we moved to assetless builds the time it took for runtime-official to execute got very short, which means we basically now run a build for ~every commit that gets pushed.

We don't need to do a OneLocBuild and SourceIndex all the time since those only update daily anyway, allowing us to save CI resources.

@dotnet-policy-service
Copy link
Contributor

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

@akoeplinger
Copy link
Member Author

/ba-g not tested in public CI, merging

@akoeplinger akoeplinger merged commit 852d2b4 into dotnet:main Jan 23, 2026
17 of 38 checks passed
@akoeplinger akoeplinger deleted the schedule-onelocbuild-sourceindex branch January 23, 2026 11:47
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

This PR optimizes CI resource usage by restricting OneLocBuild and SourceIndex operations to scheduled and manual builds instead of running on every commit to the main branch. Since these operations only update daily anyway, there's no benefit to running them continuously as builds complete faster with assetless builds.

Changes:

  • Added a daily schedule trigger that runs at 9:00 AM UTC for the main branch
  • Modified the condition for the Localization and Source_Index stages to only execute on scheduled or manual builds

Comment on lines +20 to +25
schedules:
- cron: "0 9 * * *"
displayName: Daily OneLocBuild and SourceIndex
branches:
include:
- main
Copy link

Copilot AI Jan 23, 2026

Choose a reason for hiding this comment

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

The schedule definition is missing the always: property. Based on the codebase conventions, all schedule definitions include this property to explicitly control whether the schedule runs unconditionally or only when there are changes since the last successful run.

For localization and source indexing, you likely want always: true to ensure these tasks run on schedule regardless of code changes (since localization data and source indexing may need updates even without code changes). Alternatively, if you want to conserve resources by only running when there are code changes, use always: false with a clarifying comment.

Copilot uses AI. Check for mistakes.
akoeplinger added a commit that referenced this pull request Jan 30, 2026
The OneLoc team reached out to me and told me that we need to run it on
every build, otherwise it will cause alerts in their system. Move
OneLocBuild back and only run SourceIndex daily.

Follow up to #123539
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants