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

chore(ci): do not run e2e tests triggered by label on GKE clusters #4235

Merged
merged 1 commit into from
Jun 27, 2023

Conversation

programmer04
Copy link
Member

What this PR does / why we need it:

Currently label ci/run-e2e runs GKE-based tests with a nightly image (instead of one from PR). It is pointless because you want to test the PR code. Change in this PR ensures that only KIND-based clusters are used for tests and proper comment

E2E (targeted) tests with KIND-based clusters were started at ${URL}

is added. For implementing it for GKE clusters (building image from PR and loading it to a cluster) separate issue exists Kong/kubernetes-testing-framework#587.

@programmer04 programmer04 added area/ci area/tests ci/run-e2e Trigger e2e test run from PR labels Jun 27, 2023
@programmer04 programmer04 self-assigned this Jun 27, 2023
@programmer04 programmer04 requested a review from a team as a code owner June 27, 2023 07:57
@programmer04 programmer04 enabled auto-merge (squash) June 27, 2023 07:57
@team-k8s-bot
Copy link
Collaborator

E2E (targeted) tests with KIND-based clusters were started at https:/Kong/kubernetes-ingress-controller/actions/runs/5387421798

@team-k8s-bot team-k8s-bot removed the ci/run-e2e Trigger e2e test run from PR label Jun 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants