[ci] Add inflight/current to the schedule triggers for daily builds#30656
Merged
[ci] Add inflight/current to the schedule triggers for daily builds#30656
Conversation
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR updates the internal CI pipeline configuration to include the inflight/current branch in the daily build schedule and cleans up a stray dash in the post-build steps.
- Add
inflight/currentto the scheduled triggers underschedules.include - Remove an extraneous dash before the post-build template
Comments suppressed due to low confidence (1)
eng/pipelines/azure-pipelines-internal.yml:30
- Indentation for the new schedule entry should match the existing entries (two spaces before
-). This ensures the YAML parser reads it correctly.
- inflight/current
rmarinho
added
the
area-infrastructure
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of Change
The only change is adding the inflight/current to the list of schedule on the internal pipeline. The other changes is VSCODE cleaning up the file
Heads up when we force push we will need to force push the mirror.
Why do we need this building ? because we want the packages to be pushed to the dotnet9 feed for CSI to use