Skip to content
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

Merged

Conversation

nbusseneau
Copy link
Member

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.

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>
@nbusseneau nbusseneau added area/CI Continuous Integration testing issue or flake release-note/ci This PR makes changes to the CI. labels Jul 30, 2021
@nbusseneau nbusseneau requested review from a team as code owners July 30, 2021 15:15
Copy link
Member

@joestringer joestringer left a 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.

@nbusseneau
Copy link
Member Author

Does this mean that v1.10 is only having CI 3.0 tests run as part of backport PR jobs?

At the moment, yes.

@nbusseneau nbusseneau added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Jul 30, 2021
@nbusseneau
Copy link
Member Author

Marking as ready-to-merge because this PR does not need to run any CI jobs.

@vadorovsky vadorovsky merged commit e6287ba into cilium:master Aug 1, 2021
nbusseneau added a commit to nbusseneau/cilium that referenced this pull request Aug 4, 2021
We missed this one in cilium#17023.

Fixes: e6287ba

Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
aanm pushed a commit that referenced this pull request Aug 4, 2021
We missed this one in #17023.

Fixes: e6287ba

Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
krishgobinath pushed a commit to krishgobinath/cilium that referenced this pull request Oct 20, 2021
We missed this one in cilium#17023.

Fixes: e6287ba

Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/CI Continuous Integration testing issue or flake ready-to-merge This PR has passed all tests and received consensus from code owners to merge. release-note/ci This PR makes changes to the CI.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants