HomeBlogNicht kategorisiertWhat is Tekton? Tekton vs Jenkins?

What is Tekton? Tekton vs Jenkins?

This site is also available in: Deutsch (German)

Tekton is an open source framework for creating Continuous Integration and Continuous Delivery (CI/CD) systems in Kubernetes environments. It provides a set of Kubernetes Custom Resource Definitions (CRDs) and controllers that allow users to define and run CI/CD pipelines as Kubernetes resources. Tecton  can be distinguished from Jenkins by the following points

Advantages:

  • Native Kubernetes integration: Simple integration into Kubernetes clusters
  • Containerization: Better isolation and portability through container-based pipelines
  • Resource efficiency: Efficient use of resources in Kubernetes clusters
  • Declarative pipeline definition: Simple maintenance and version control through declarative definition with YAML
  • Cloud-native: Suitable for modern application development practices

Disadvantages:

  • Learning curve: familiarization for teams who know Jenkins
  • Extensibility: The store of plugins for Jenkins is large while filling the Tekton Hub
  • Maturity level: Less widespread, therefore less documentation and community support
  • Migration: Complex process for existing Jenkins pipelines

Conclusion:
The choice between Tekton and Jenkins depends on a team’s specific requirements, existing infrastructure and preferences. Tekton offers advantages in terms of Kubernetes integration, containerization, resource efficiency and declaration. Jenkins, on the other hand, has a more established ecosystem and is more widely used.

Additional points:

  • Tekton is open source and is supported by the Cloud Native Computing Foundation (CNCF).
  • Jenkins is also open source and has a large community.
  • Both tools can be used with a variety of languages and frameworks.
Use-cases Tekton pipelines:
  • Creation of various Continues integration pipelines (maven, gradle, npm, go, ..) 
  • Creation of Continues Delivery/Deployment pipelines (ansible-playbook, helm upgrade, …)
  • Use of helper pipelines (automatic skopeo image transfer, automatic api-management integration, …)

Recommendation:

It is important to assess the specific needs and requirements of your team before deciding on a tool.

We would be happy to advise you on choosing the right CI/CD tool for your company!
Also visit the UDEMY course =>
https://www.udemy.com/course/tekton-the-quick-start


Leave a Reply

Your email address will not be published. Required fields are marked *