-
Notifications
You must be signed in to change notification settings - Fork 787
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 to Native Tekton #8589
Comments
when is this planned to happen? |
Sometime this year, we need to create a more intelligent git resolver within tekton. The one at the minute will just eat your rate limit, so we need to build one with some caching and also make a shorthand syntax for referencing your specified build packs, at the minute it's got a branch, a git provider, a organisation name, a repository name and a file / dir name for every pipeline step. So it's quite a substantial file and it's kinda hard to see the wood for the trees in terms of understanding your pipelines. So there's a bit to do, but this was the major step to get to the latest version of tekton, we'll start looking this year. We're priorotising the ESO migration at my end, as that seems to be the worst situation at the moment. If someone wants to look at a tekton caching git resolver, that would be great. |
We've had issues with upgrading Tekton and K8s versions stemming from lighthouse flattening pipelineRuns with the
uses:
syntax.Ideally, we'd like to remove this functionality from lighthouse and rely solely on native Tekton. Tekton now has its own git resolver that works in a similar way to lighthouse, but after investigation, it's not quite ready to replace lighthouse's syntax.
The text was updated successfully, but these errors were encountered: