Schedule HTTP & SSL stress runs for release/6.0

[antonfirsov]

We need this to make sure that NCL is stable for 6.0.

@dotnet/dncenghot is this the right way to setup this? If not can you please help?

[ghost]

Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer
See info in area-owners.md if you want to be subscribed.

Issue Details

---

We need this to make sure that NCL is stable for 6.0.

@dotnet/dncenghot is this the right way to setup this? If not can you please help?

Author:	antonfirsov
Assignees:	-
Labels:	area-Infrastructure-libraries
Milestone:	-

[lpatalas]

@antonfirsov, I think you should merge it to release/6.0 branch otherwise the trigger won't be added. Your scenario is described at the end of this doc section: Branch considerations for scheduled triggers

It says something like this:

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 feature branch is added to the branch filters in the YAML file in the feature branch will the scheduled build be added to the scheduler.

[antonfirsov]

@lpatalas thank you!

@dotnet/ncl mergig Merging this directly to release/6.0 seems messy to me. I think the best would be to merge & backport this so keep the YAML-s in sync, and have a reminder on main that these pipelines are scheculed against release/6.0.

[ManickaP]

LGTM, but I cannot speak for the infra part (where to merge etc.).
Thanks for this!

[antonfirsov]

HTTP 1.1 CI stress run hasn't finished yet, but from the logs it's clear that the changes have no negative impact, merging.

[antonfirsov]

/backport to release/6.0

[github-actions]

Started backporting to release/6.0: https://github.com/dotnet/runtime/actions/runs/1174924871