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

Create a pipeline to validate a released version of a Tekton project #75

Closed
afrittoli opened this issue Sep 30, 2019 · 6 comments
Closed
Assignees
Labels
area/dogfooding Indicates an issue on dogfooding (aka using Pipeline to test Pipeline) area/release Indicates an issue on release (process, tasks). area/test-infra Issues or PRs related to the testing infrastructure

Comments

@afrittoli
Copy link
Member

We need a way to validate releases for various Tekton projects, and we should use a Tekton pipeline for that. Eventually we should be able to automatically trigger the pipeline as a post release job.

The aim is not to validate that the code that we just released works fine, since that is tested before the release as part of our CI, but rather to verify that the release artifacts were correctly generated. We had an issue in the past with .ko.yaml not being generated properly, which caused the wrong base image to be used when building the release.

@afrittoli
Copy link
Member Author

/assign

@afrittoli
Copy link
Member Author

/area test-infra
/area release

@tekton-robot tekton-robot added area/test-infra Issues or PRs related to the testing infrastructure area/release Indicates an issue on release (process, tasks). labels Sep 30, 2019
@bobcatfish bobcatfish added this to the Pipelines 0.8 🐱 milestone Oct 3, 2019
@bobcatfish bobcatfish removed this from the Pipelines 0.9 🐱 milestone Nov 25, 2019
@vdemeester vdemeester added the area/dogfooding Indicates an issue on dogfooding (aka using Pipeline to test Pipeline) label Dec 13, 2019
@tekton-robot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
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.

/lifecycle stale

Send feedback to tektoncd/plumbing.

@tekton-robot
Copy link
Contributor

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

/lifecycle rotten

Send feedback to tektoncd/plumbing.

@tekton-robot
Copy link
Contributor

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 13, 2020
@tekton-robot tekton-robot added the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Aug 13, 2020
@tekton-robot
Copy link
Contributor

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

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.

@afrittoli afrittoli removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Aug 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dogfooding Indicates an issue on dogfooding (aka using Pipeline to test Pipeline) area/release Indicates an issue on release (process, tasks). area/test-infra Issues or PRs related to the testing infrastructure
Projects
None yet
Development

No branches or pull requests

5 participants