You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there is no CI guarantee to make sure these projects are not broken. PR #49706 fixed such a regression, but in a few weeks the build got broken again (#51117) with a reason that is far from being obvious.
Edit 1: An alternative could be an agreement to run those pipelines on infrastructure changes. Edit 2: The root cause of #51117 was a library bug (#51141) breaking the SDK, meaning that guarding the infra changes only might be insufficient, but this looks like an exceptional case.
The text was updated successfully, but these errors were encountered:
Currently there is no CI guarantee to make sure these projects are not broken. PR #49706 fixed such a regression, but in a few weeks the build got broken again (#51117) with a reason that is far from being obvious.
Currently there is no CI guarantee to make sure these projects are not broken. PR #49706 fixed such a regression, but in a few weeks the build got broken again (#51117) with a reason that is far from being obvious.
We should consider running build-only variants of
stress/http.yml
,stress/ssl.yml
andenterprise/linux.yml
as a mandatory PR checks.The lack of such an automation makes it really hard to keep these projects functional while the underlying infrastructure is being refactored.
cc @ViktorHofer
Edit 1: An alternative could be an agreement to run those pipelines on infrastructure changes.
Edit 2: The root cause of #51117 was a library bug (#51141) breaking the SDK, meaning that guarding the infra changes only might be insufficient, but this looks like an exceptional case.
The text was updated successfully, but these errors were encountered: