Skip to content

🌱 Add jobs for CAPI release 1.9 and remove 1.6 jobs #33816

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Nov 26, 2024
Merged

🌱 Add jobs for CAPI release 1.9 and remove 1.6 jobs #33816

merged 1 commit into from
Nov 26, 2024

Conversation

cahillsf
Copy link
Member

@cahillsf cahillsf commented Nov 19, 2024 •
edited
Loading

@k8s-ci-robot
Copy link
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@k8s-ci-robot k8s-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. area/config Issues or PRs related to code in /config area/jobs area/testgrid size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Nov 19, 2024
@k8s-ci-robot k8s-ci-robot added the sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. label Nov 19, 2024
@k8s-ci-robot k8s-ci-robot added the sig/testing Categorizes an issue or PR as relevant to SIG Testing. label Nov 19, 2024
@cahillsf cahillsf force-pushed the capi-release-1.9-jobs branch from 867f8f6 to 3be8336 Compare November 19, 2024 17:46
@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 19, 2024
@cahillsf cahillsf force-pushed the capi-release-1.9-jobs branch from 3be8336 to 5057352 Compare November 19, 2024 17:59
@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 26, 2024
@cahillsf cahillsf force-pushed the capi-release-1.9-jobs branch from 5057352 to ae57527 Compare November 26, 2024 14:29
@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 26, 2024
@cahillsf cahillsf marked this pull request as ready for review November 26, 2024 16:45
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 26, 2024
Sunnatillo
Sunnatillo reviewed Nov 26, 2024
View reviewed changes
Copy link
Contributor

@Sunnatillo Sunnatillo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@k8s-ci-robot
Copy link
Contributor

@Sunnatillo: changing LGTM is restricted to collaborators

In response to this:

/lgtm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

fabriziopandini
fabriziopandini reviewed Nov 26, 2024
View reviewed changes
Copy link
Member

@fabriziopandini fabriziopandini left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 26, 2024
@cahillsf cahillsf force-pushed the capi-release-1.9-jobs branch from ae57527 to bfae331 Compare November 26, 2024 18:35
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 26, 2024
@cahillsf cahillsf force-pushed the capi-release-1.9-jobs branch from bfae331 to b20c35a Compare November 26, 2024 18:36
@chrischdi
Copy link
Member

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 26, 2024
@chrischdi
Copy link
Member

/approve

1 similar comment
@fabriziopandini
Copy link
Member

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cahillsf, chrischdi, fabriziopandini

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 26, 2024
@k8s-ci-robot k8s-ci-robot merged commit 2b39099 into kubernetes:master Nov 26, 2024
6 of 7 checks passed
@k8s-ci-robot
Copy link
Contributor

@cahillsf: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

  • key cluster-api-prowjob-gen.yaml using file config/jobs/kubernetes-sigs/cluster-api/cluster-api-prowjob-gen.yaml
  • key cluster-api-release-1-6-periodics-upgrades.yaml using file ``
  • key cluster-api-release-1-9-periodics-upgrades.yaml using file config/jobs/kubernetes-sigs/cluster-api/cluster-api-release-1-9-periodics-upgrades.yaml
  • key cluster-api-release-1-6-periodics.yaml using file ``
  • key cluster-api-release-1-9-periodics.yaml using file config/jobs/kubernetes-sigs/cluster-api/cluster-api-release-1-9-periodics.yaml
  • key cluster-api-release-1-6-presubmits.yaml using file ``
  • key cluster-api-release-1-9-presubmits.yaml using file config/jobs/kubernetes-sigs/cluster-api/cluster-api-release-1-9-presubmits.yaml

In response to this:

adds new jobs for release-1.9 branch and drops jobs for release-1.6 per release docs: https://github.com/kubernetes-sigs/cluster-api/tree/main/docs/release/role-handbooks/ci-signal#setup-jobs-and-dashboards-for-a-new-release-branch

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@Sunnatillo Sunnatillo mentioned this pull request Dec 4, 2024
Closed
54 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@chrischdi chrischdi chrischdi left review comments

@fabriziopandini fabriziopandini fabriziopandini left review comments

@Sunnatillo Sunnatillo Sunnatillo left review comments

@JoelSpeed JoelSpeed Awaiting requested review from JoelSpeed

@neolit123 neolit123 Awaiting requested review from neolit123

@justinsb justinsb Awaiting requested review from justinsb

Assignees

@chrischdi chrischdi

@fabriziopandini fabriziopandini

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/config Issues or PRs related to code in /config area/jobs area/testgrid cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@cahillsf @k8s-ci-robot @chrischdi @fabriziopandini @Sunnatillo