-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't run ssl/http stress on release/6.0 and release/7.0 #103572
Conversation
Tagging subscribers to this area: @dotnet/ncl |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, should this also be merged into existing release branches?
Don't know, I was under the impression that those pipelines definitions are always taken from main. I will check after merging and port them if needed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pipelines definitions are always taken from main
I also think this is the case.
Follow up from #103572. Seems like the schedule must be disabled in the particular branch (see https://learn.microsoft.com/en-us/azure/devops/pipelines/process/scheduled-triggers?view=azure-devops&tabs=yaml)
* Remove release/6.0 from HttpStress Follow up from #103572. Seems like the schedule must be disabled in the particular branch (see https://learn.microsoft.com/en-us/azure/devops/pipelines/process/scheduled-triggers?view=azure-devops&tabs=yaml) * Update ssl.yml
.NET 7.0 is out of support
.NET 6.0 fails to build (except http stress on Linux)
And we are not monitoring either of them regularly.