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
We should instead run more stuff here, in particular costly stuff we don't run on PRs.
For example, a full matrix run of OS * container manager * network plugin (but migth be an overkill)
Why is this needed
It's easier to catch regression when you can narrow down the time (and subsequently, the commit range) which introduced it.
We could also consider using some of kubernetes methologies on "release-blocking" CI (aka, jobs needs to run, if not we fix it before releasing).
The text was updated successfully, but these errors were encountered:
What would you like to be added
We run many setups in CI on Pull Request, but not in the daily-ci
https://gitlab.com/kargo-ci/kubernetes-sigs-kubespray/-/pipelines/1631813327/ => most of the packets jobs are not run.
We should instead run more stuff here, in particular costly stuff we don't run on PRs.
For example, a full matrix run of OS * container manager * network plugin (but migth be an overkill)
Why is this needed
It's easier to catch regression when you can narrow down the time (and subsequently, the commit range) which introduced it.
We could also consider using some of kubernetes methologies on "release-blocking" CI (aka, jobs needs to run, if not we fix it before releasing).
The text was updated successfully, but these errors were encountered: