3 ms·
Speaking as someone whose spent the last 18 months building out Tekton pipelines, I can confidently disagree that it’s architecture (or general ethos) is built
by halfmatthalfcat 6y ago
Speaking as someone whose spent the last 18 months building out Tekton pipelines, I can confidently disagree that it’s architecture (or general ethos) is built around CI/CD. The docs might allude to a lot of CI/CD use cases but the framework is very general in that you have the building blocks for any event driven workflow: Tasks, Pipelines and Events.
- rektide 6y agoTekton was very high in my runnings, very attractive. I liked the models they built around, they seemed like a good structure. Everything built very "cloud-native" (system state stored as Kubernetes objects). But the project did explicitly pivot, sometime in the last 12 months, to explicitly declare themselves/think of themselves as a CI/CD system. They're also under the Continuous Delivery Foundation now. I spent 5 minutes looking for the specific event, where this was determined/declared, & will try to follow up; hope I find it. I don't think it precludes Tekton from still being used more generally, thought of more generally. But now, doing so puts one out of alignment with the stated goals, with the project itself. I'm quite sad about this development: I think it radically undershoots the relevance of Tekton & what role it ought to fill. We have all this wonderful new cloud based pieces of state, but in terms of how one piece actuates another, how we can make systems that behave autonomically: we direly need some core Event Driven Architecture logic, and Tekton definitely has some really good tools for doing that. I want very much for Tekton to meet it's potential head on.