11–20 of 21 posts
Earlier quoted context omitted.
https://argoproj.github.io/argo-cd/
Yeah, pretty similar overall. Tho Tekton is also the underlying technology for Jenkins X. With Jenkins being such a common system in the CI/CD space, I think we'll see Tekton preferred going forward. https://jenkins-x.io/
Earlier quoted context omitted.
Yeah, pretty similar overall. Tho Tekton is also the underlying technology for Jenkins X. With Jenkins being such a common system in the CI/CD space, I think we'll see Tekton preferred going forward. https://jenkins-x.io/
That...is an interesting dependency direction? Isn't Tekton MUCH newer? Are they developed by similar people?
Interesting but is it another argocd?
A closer comparison would be to Argo Workflow. Tekton and Argo Workflow provide ways to declare workflow pipelines for execution on Kubernetes. Tekton focuses on source based workflows, while Argo is more general purpose. We've been working with the Argo team to make sure Argo CD works well with Tekton, and we now have a first-class integration in the tekton catalog, contributed by that team. Disclosure: one of the l…
Earlier quoted context omitted.
A closer comparison would be to Argo Workflow. Tekton and Argo Workflow provide ways to declare workflow pipelines for execution on Kubernetes. Tekton focuses on source based workflows, while Argo is more general purpose. We've been working with the Argo team to make sure Argo CD works well with Tekton, and we now have a first-class integration in the tekton catalog, contributed by that team. Disclosure: one of the l…
How much, if at all, has the investment from Google in open source projects like Tekton changed at all with the post-Diane Greene leadership?
Interesting but is it another argocd?
A closer comparison would be to Argo Workflow. Tekton and Argo Workflow provide ways to declare workflow pipelines for execution on Kubernetes. Tekton focuses on source based workflows, while Argo is more general purpose. We've been working with the Argo team to make sure Argo CD works well with Tekton, and we now have a first-class integration in the tekton catalog, contributed by that team. Disclosure: one of the l…
What is the plan here?
The focus on source based flows is the right product decision here --- wonder if it unnaturally constrains the market and effectively cede ubiquity to a more generic tool What is the plan here?
My 2c is that we'll see more and more things become source-based over time. We're already seeing it with infra as code, gitops, git-ml, etc.
If the scope of Tekton expands, it will be because more things become source-based. And that would be great for everyone.
Disclosure: one of the leads and founders of Tekton, at Google.
Earlier quoted context omitted.
This handles the ci part. Argo handles the cd. I use them both together now.
I'd love to hear more about how you're using them if you don't mind sharing. I work on Tekton at Google.
Earlier quoted context omitted.
Yeah, pretty similar overall. Tho Tekton is also the underlying technology for Jenkins X. With Jenkins being such a common system in the CI/CD space, I think we'll see Tekton preferred going forward. https://jenkins-x.io/
Even the Argo team isn’t investing much effort into Argo workflows and Argo ci.