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.

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

Migrate Integration Tests to use kind + Prow #1263

Open
4 of 8 tasks
chitrangpatel opened this issue Nov 9, 2022 · 11 comments
Open
4 of 8 tasks

Migrate Integration Tests to use kind + Prow #1263

chitrangpatel opened this issue Nov 9, 2022 · 11 comments
Labels
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. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@chitrangpatel
Copy link
Contributor

chitrangpatel commented Nov 9, 2022 •
edited by vdemeester
Loading

Migrate integration tests to used a kind cluster.
We should stop using GKE clusters directly for tests unless really required for some reason.

We might want to create repo specific issues where required.
@abayer
Copy link
Contributor

abayer commented Nov 10, 2022

Pipeline's already moved, and I know @dibyom has been working on this for Triggers, but I don't know the status there.

@chitrangpatel
Copy link
Contributor Author

/priority important

@tekton-robot
Copy link
Contributor

@chitrangpatel: The label(s) priority/important cannot be applied, because the repository doesn't have them.

In response to this:

/priority important

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/test-infra repository.

@chitrangpatel
Copy link
Contributor Author

/priority importantsoon

@tekton-robot
Copy link
Contributor

@chitrangpatel: The label(s) priority/importantsoon cannot be applied, because the repository doesn't have them.

In response to this:

/priority importantsoon

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/test-infra repository.

@chitrangpatel
Copy link
Contributor Author

/priority important-soon

@tekton-robot tekton-robot added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Nov 10, 2022
@dibyom dibyom moved this from Todo to In Progress in Pipeline CI Dogfooding Nov 11, 2022
@AlanGreene
Copy link
Member

AlanGreene commented Nov 24, 2022 •
edited
Loading

Dashboard is already done since ~August/September

edit: #1191

@chitrangpatel chitrangpatel moved this from In Progress to Done in Pipeline CI Dogfooding Jan 19, 2023
@chitrangpatel chitrangpatel moved this from Done to In Progress in Pipeline CI Dogfooding Jan 19, 2023
@vdemeester
Copy link
Member

/area roadmap

@tekton-robot tekton-robot added the area/roadmap Issues that are part of the project (or organization) roadmap (usually an epic) label Feb 15, 2023
@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 Jul 2, 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 Aug 1, 2023
@AlanGreene
Copy link
Member

/lifecycle frozen

@tekton-robot tekton-robot added 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 Aug 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
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. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
Pipeline CI Dogfooding
Status: In Progress
Tekton Community Roadmap
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
5 participants
@vdemeester @abayer @AlanGreene @chitrangpatel @tekton-robot