-
Notifications
You must be signed in to change notification settings - Fork 265
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
Update release pipeline to use workspaces and results #1969
Comments
Also need to update template for nightly release: https://github.com/tektoncd/plumbing/blob/2c1808d75b38d6fcaae0a37f5a9dda50545af4c8/tekton/resources/nightly-release/overlays/dashboard/template.yaml See Pipelines / Triggers equivalent for reference. |
/assign |
/unassign |
Hey @nikhil-thomas, have you had a chance to look at updating the Dashboard release pipeline yet? No worries if you haven't, I was just wondering if you had run into any problems or had any questions about it. |
hi, i haven't started on it yet. I shall definitely pick it up this week. 🧑💻 👍 |
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
This is done. Nightly releases are successfully using the new pipeline and are signed with Chains 🎉 The v0.22 release (due next week) will also use this new pipeline and be signed. |
Remove use of PipelineResources, switching to Tasks with workspaces and results instead.
See tektoncd/pipeline and tektoncd/operator release pipelines for example.
It may also make sense to adopt some of the other improvements to the release pipeline such as using
crane cp
instead ofgcloud images add-tag
.Also see
https://github.com/tektoncd/triggers/pull/1000
The text was updated successfully, but these errors were encountered: