Skip to content

[Stress] Scheduled runs take definition from YML in main#128134

Closed
ManickaP wants to merge 1 commit into
dotnet:mainfrom
ManickaP:stress-schedule
Closed

[Stress] Scheduled runs take definition from YML in main#128134
ManickaP wants to merge 1 commit into
dotnet:mainfrom
ManickaP:stress-schedule

Conversation

@ManickaP
Copy link
Copy Markdown
Member

We're not running on staging branches right now. Apparently, the scheduled runs take the definition from main and not their respective branches.

@dotnet-policy-service
Copy link
Copy Markdown
Contributor

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

Copy link
Copy Markdown
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 updates the Azure Pipelines scheduled branch filters for the HTTP and SSL stress pipelines so that nightly schedules also run for release/*.0-staging branches (in addition to main and release/*.0).

Changes:

  • Add release/*.0-staging to the scheduled branches.include list in the SSL stress pipeline.
  • Add release/*.0-staging to the scheduled branches.include list in the HTTP stress pipeline.

Reviewed changes

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

File Description
eng/pipelines/libraries/stress/ssl.yml Extends the nightly schedule branch include filter to cover release/*.0-staging.
eng/pipelines/libraries/stress/http.yml Extends the nightly schedule branch include filter to cover release/*.0-staging.

@rzikm
Copy link
Copy Markdown
Member

rzikm commented May 13, 2026

weird, I removed these lines recently exactly because it seemed that the defintions are taken from the respective branches :D

@rzikm
Copy link
Copy Markdown
Member

rzikm commented May 13, 2026

#121802

@rzikm
Copy link
Copy Markdown
Member

rzikm commented May 13, 2026

From https://learn.microsoft.com/en-us/azure/devops/pipelines/process/scheduled-triggers?view=azure-devops&tabs=yaml&pivots=pipelines-yaml

Now consider that a branch named release is created based off main, and then release is added to the branch filters in the YAML file in the main branch, but not in the newly created release branch.

# YAML file in the release branch
schedules:
- cron: '0 0 * * *'
  displayName: Daily midnight build
  branches:
    include:
    - main

# YAML file in the main branch with release added to the branches list
schedules:
- cron: '0 0 * * *'
  displayName: Daily midnight build
  branches:
    include:
    - main
    - release

Because release was added to the branch filters in the main branch, but not to the branch filters in the release branch, the release branch won't be built on that schedule. Only when the release branch is added to the branch filters in the YAML file in the release branch will the scheduled build be added to the scheduler.

@ManickaP
Copy link
Copy Markdown
Member Author

I'm asking in FR channel, cause I based this PR on their reply there.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants