-
Notifications
You must be signed in to change notification settings - Fork 130
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
Ensure Chains works with the v1 version of TaskRuns and PipelineRuns #665
Comments
Context: today chains is only watching |
I wonder if it's possible for Chains to handle both v1beta1 and v1. That would facilitate adoption. |
In fact, we need a spin-off issue around handling cross-version compatibility with pipelines changes. |
So, technically, as long as I think, in a few release (most likely, more or less at the same time 0.47 gets release with a storage version change), We may want to rename this issue to "switch chains controller to watch |
Immediate AIs:
TEP please:
|
@bendory definitely +:100: on your checklist ❤️ |
/area roadmap |
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
/lifecycle frozen |
Here is the proposed action plan for this:
This would completely satisfy The only issue is with Eventually, when |
/assign |
Starting on the work here, made some issues to track the subtasks:
If someone has comment edit access, feel free to make this an [Umbrella Tracking] issue and put this checklist in the top comment |
/assign @aaron-prindle |
Dropping in some notes/info from todays Tekton Chains WG meeting: Open questions
AIs
|
Pipelines APIs have been updated to v1 from v1beta1.
Make sure that these versions work well with Chains.
Starting on the work here, made some issues to track the subtasks: Thanks @aaron-prindle !!
The text was updated successfully, but these errors were encountered: