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
workflows: disable scheduled runs for 1.10 workflows #17023
workflows: disable scheduled runs for 1.10 workflows #17023
Conversation
With the current setup, the scheduled runs on 1.10 workflows are testing exactly the same as the regular workflows. Since this doubles the amount and cost of testing for no reason, we disable schedule runs on 1.10 workflows. We can always re-enable them later on when we actually rework them to use the v1.10 branches instead. Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
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.
Does this mean that v1.10 is only having CI 3.0 tests run as part of backport PR jobs?
Makes sense to remove workflows if they're duplicate with no additional value.
At the moment, yes. |
Marking as |
We missed this one in cilium#17023. Fixes: e6287ba Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
We missed this one in cilium#17023. Fixes: e6287ba Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
With the current setup, the scheduled runs on 1.10 workflows are testing exactly the same as the regular workflows. Since this doubles the amount and cost of testing for no reason, we disable schedule runs on 1.10 workflows.
We can always re-enable them later on when we actually rework them to use the v1.10 branches instead.