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

Migrate e2e tests on kind #1774

Closed
vdemeester opened this issue Nov 4, 2022 · 4 comments · Fixed by #2259
Closed

Migrate e2e tests on kind #1774

vdemeester opened this issue Nov 4, 2022 · 4 comments · Fixed by #2259
Labels
area/roadmap Issues that are part of the project (or organization) roadmap (usually an epic) area/test-infra Issues or PRs related to the testing infrastructure kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@vdemeester
Copy link
Member

tektoncd/pipeline and probably other migrated to use kind for e2e tests.

  • It's easier to run the same environment locally and on the cluster
  • It's less flaky and it's quicker to provision
  • It's less costly (and can allow us to run multiple e2e tests on different k8s version, …)
@vdemeester vdemeester added kind/feature Categorizes issue or PR as related to a new feature. area/test-infra Issues or PRs related to the testing infrastructure labels Nov 4, 2022
@ehudyonasi
Copy link

Would like to take it if it's possible.

@tekton-robot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 5, 2023
@tekton-robot
Copy link
Contributor

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 5, 2023
@vdemeester
Copy link
Member Author

/lifecycle frozen
/area roadmap

@tekton-robot tekton-robot added area/roadmap Issues that are part of the project (or organization) roadmap (usually an epic) lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels May 5, 2023
piyush-garg added a commit to piyush-garg/cli that referenced this issue Mar 1, 2024
This will prepare the setup for moving e2e tests to
run on kind instead of gcp

Fix tektoncd#1774
piyush-garg added a commit to piyush-garg/cli that referenced this issue Mar 1, 2024
This will prepare the setup for moving e2e tests to
run on kind instead of gcp

Fix tektoncd#1774
tekton-robot pushed a commit that referenced this issue Mar 1, 2024
This will prepare the setup for moving e2e tests to
run on kind instead of gcp

Fix #1774
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/roadmap Issues that are part of the project (or organization) roadmap (usually an epic) area/test-infra Issues or PRs related to the testing infrastructure kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants