Skip to content

[NET] Add a new pipeline for PR trigger on top of the existing stress pipelines#126474

Merged
ManickaP merged 1 commit intodotnet:mainfrom
ManickaP:stress-pr-trigger
Apr 9, 2026
Merged

[NET] Add a new pipeline for PR trigger on top of the existing stress pipelines#126474
ManickaP merged 1 commit intodotnet:mainfrom
ManickaP:stress-pr-trigger

Conversation

@ManickaP
Copy link
Copy Markdown
Member

@ManickaP ManickaP commented Apr 2, 2026

The PR trigger with file path filter for the pipelines must be separated into its own pipeline. Otherwise, azp run ... would stop working for them and we need that to manually run stress on HTTP / SSL product code changes.

  • *-stages.yml contain the original "meat" of the pipelines.
  • PR triggers from http.yml and ssl.yml are moved to new pipelines *-pr.yml

This will also need help from engineering services to actually create and enable the new pipelines.

This is a follow-up on #126358 that didn't work.

@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.

@ManickaP
Copy link
Copy Markdown
Member Author

ManickaP commented Apr 2, 2026

@akoeplinger does this look reasonable for the option number 3 from our earlier discussion today in FR?
It was created with the help of copilot as I'm not AzDO YAML expert.

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 splits path-filtered PR triggers for the HTTP/SSL stress pipelines into dedicated *-pr.yml pipelines, while keeping the original scheduled (nightly) pipelines intact by extracting the shared stage definitions into *-stages.yml templates.

Changes:

  • Removed pr: triggers from http.yml and ssl.yml and replaced the inline stage definitions with references to new shared stage templates.
  • Added http-pr.yml and ssl-pr.yml to host PR triggers with path filters while reusing the shared stages.
  • Added http-stages.yml / ssl-stages.yml to hold the previous “meat” of each pipeline.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 3 comments.

Show a summary per file
File Description
eng/pipelines/libraries/stress/http.yml Nightly pipeline now references shared HTTP stress stages; PR trigger removed.
eng/pipelines/libraries/stress/http-stages.yml New shared HTTP stress stage template (extracted from old http.yml).
eng/pipelines/libraries/stress/http-pr.yml New PR-triggered HTTP stress pipeline with path filters.
eng/pipelines/libraries/stress/ssl.yml Nightly pipeline now references shared SSL stress stages; PR trigger removed.
eng/pipelines/libraries/stress/ssl-stages.yml New shared SSL stress stage template (extracted from old ssl.yml).
eng/pipelines/libraries/stress/ssl-pr.yml New PR-triggered SSL stress pipeline with path filters.

Comment thread eng/pipelines/libraries/stress/http-stages.yml
Comment thread eng/pipelines/libraries/stress/ssl-stages.yml
Comment thread eng/pipelines/libraries/stress/http-stages.yml
@ManickaP
Copy link
Copy Markdown
Member Author

ManickaP commented Apr 2, 2026

/azp run runtime-libraries stress-http

@ManickaP
Copy link
Copy Markdown
Member Author

ManickaP commented Apr 2, 2026

/azp run runtime-libraries stress-ssl

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

1 similar comment
@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@akoeplinger
Copy link
Copy Markdown
Member

looks approximately correct to me, Copilot may be right about the stages though from your triggered pipeline it seems to work?

@ManickaP
Copy link
Copy Markdown
Member Author

ManickaP commented Apr 7, 2026

Yeah, the azp run ran the pipeline without an issue. So it should be OK I assume. Unless it rather picks up the pipeline from main branch instead of the PR...

@akoeplinger
Copy link
Copy Markdown
Member

Unless it rather picks up the pipeline from main branch instead of the PR...

hmm could be. I guess we'll have to try

@ManickaP ManickaP merged commit cb07167 into dotnet:main Apr 9, 2026
120 checks passed
@ManickaP ManickaP deleted the stress-pr-trigger branch April 9, 2026 07:41
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.

3 participants