Senior DevOps Engineer at Simplify3x Software Private Limited
Real User
Top 5
2024-11-11T16:10:05Z
Nov 11, 2024
Tekton is used as a Kubernetes native tool for creating CI/CD pipelines. It is used for creating multiple tasks that can run as pipeline runs for several services. This helps in reducing time wastage and has several benefits. I work mostly on creating tasks and pipelines while my colleague handles the initial setup and login.
We mostly use Tekton to run all of our pipelines. We create unit tests and also use it for Jira build messages as well as the Docker build application. We check the logs within Tekton itself and create a manifest to deploy in our development, test, and other environments.
DevOps Developer at Ibm India Software Lab Private Limited
Real User
Top 20
2024-09-13T09:28:00Z
Sep 13, 2024
We are using Tekton for building some of our CI pipeline, continuous integration pipeline, as well as integrating some of our other pipelines, such as test pipelines.
Self Employed at Deguene Cloud Adoption Consulting
Real User
Top 20
2024-09-02T18:55:47Z
Sep 2, 2024
I use the product primarily for CI/CD in application cloud-native environments. It helps us build code, and occasionally, it is also used for deployment.
I use the platform to manage development pipelines. Our infrastructure is integrated with Kubernetes, and we utilize it within an OpenShift environment for automation. I have developed various pipelines and plugins for both front-end and back-end applications, including Angular for the front end and Quarkus, a Java framework for microservices, for the back end. The platform supports tasks such as code cloning, testing, and deployment by integrating SonarQube, Argo, and Nexus tools.
The CI solution of the team I worked for was based on Tekton. Since Tekton is a Kubernetes native framework, we can easily configure it within a Kubernetes cluster, which has many benefits.
We have our automation pipeline in Tekton. We create pipelines, basically pipelines, to run automated customer scenarios through our automation, Bash scripts, and Golang. To execute these tests routinely, we have implemented those pipelines in Tekton.
I installed Tekton as an operator in OpenShift. Tekton is a pipeline tool. It operates within OpenShift, which is similar to how Kubernetes resources are managed. With Tekton, we utilize CRDs to define pipelines. Using the Tekton dashboard, we can create CI integrations for our applications. For instance, I used Tekton to manage CI for a Cloud-based Java application and an ongoing frontend application. Tekton's form-based approach is convenient for declaring variables and commands, handling secrets, and authentication. Overall, Tekton's ease of use and competitiveness compared to tools like Jenkins or GitHub Actions made it the preferred choice.
It is an open-source tool initially developed by Google for internal use, later open-sourced, and widely adopted for building and deploying applications in Kubernetes environments. When deployed in a Kubernetes cluster, Tekton seamlessly integrates with the environment, streamlining the application pipeline delivery process. It automatically triggers when code is merged into the main branch, operating natively within Kubernetes without requiring additional external components. The automated pipeline, initiated by Tekton, builds the application, deploys it to specified container registries, and then to the Kubernetes cluster. Tekton's versatility shines in multi-environment setups like staging, testing, and production, efficiently managing the continuous integration (CI) part by triggering processes linked to code merges. Users often integrate Argo CD to complement Tekton in the continuous deployment (CD) phase. Argo CD pulls and deploys the latest application image within the Kubernetes cluster, creating a comprehensive and automated CI/CD workflow.
Tekton is the orchestration engine within OpenShift, which is our on-premise platform. Since we are not on the cloud yet, OpenShift plays a strategic role, and Tekton is a significant part of it. It serves as an orchestrator. In my experience of the last two years using Tekton and OpenShift pipelines, I haven't encountered many issues. As an orchestrator, Tekton works best. It's just one component of the larger OpenShift platform. Tekton consists of multiple components like events, trigger bindings, and more. However, when it comes to the overall OpenShift platform, being a platform as a service, most aspects are taken care of.
Cloud Architect at a financial services firm with 10,001+ employees
Real User
Top 20
2023-02-10T12:11:36Z
Feb 10, 2023
We are utilizing Tekton as a pipeline tool for their CI/CD process, which involves connecting GitLab to Nexus, then Nexus to Argo CD, and ultimately to Kubernetes.
Tekton is a powerful yet flexible Kubernetes-native open-source framework for creating continuous integration and delivery (CI/CD) systems. It lets you build, test, and deploy across multiple cloud providers or on-premises systems by abstracting away the underlying implementation details.
Tekton is used as a Kubernetes native tool for creating CI/CD pipelines. It is used for creating multiple tasks that can run as pipeline runs for several services. This helps in reducing time wastage and has several benefits. I work mostly on creating tasks and pipelines while my colleague handles the initial setup and login.
I am using Tekton for continuous integration in our project.
We mostly use Tekton to run all of our pipelines. We create unit tests and also use it for Jira build messages as well as the Docker build application. We check the logs within Tekton itself and create a manifest to deploy in our development, test, and other environments.
I use Tekton generally for CI purposes and automation APIs.
We are using Tekton for building some of our CI pipeline, continuous integration pipeline, as well as integrating some of our other pipelines, such as test pipelines.
I use the product primarily for CI/CD in application cloud-native environments. It helps us build code, and occasionally, it is also used for deployment.
I mostly use it for application deployments, it's a CI/CD tool. We use it for Kubernetes application deployment.
I use the platform to manage development pipelines. Our infrastructure is integrated with Kubernetes, and we utilize it within an OpenShift environment for automation. I have developed various pipelines and plugins for both front-end and back-end applications, including Angular for the front end and Quarkus, a Java framework for microservices, for the back end. The platform supports tasks such as code cloning, testing, and deployment by integrating SonarQube, Argo, and Nexus tools.
The CI solution of the team I worked for was based on Tekton. Since Tekton is a Kubernetes native framework, we can easily configure it within a Kubernetes cluster, which has many benefits.
We have our automation pipeline in Tekton. We create pipelines, basically pipelines, to run automated customer scenarios through our automation, Bash scripts, and Golang. To execute these tests routinely, we have implemented those pipelines in Tekton.
We use the solution in CI/CD pipelines for application deployment.
I installed Tekton as an operator in OpenShift. Tekton is a pipeline tool. It operates within OpenShift, which is similar to how Kubernetes resources are managed. With Tekton, we utilize CRDs to define pipelines. Using the Tekton dashboard, we can create CI integrations for our applications. For instance, I used Tekton to manage CI for a Cloud-based Java application and an ongoing frontend application. Tekton's form-based approach is convenient for declaring variables and commands, handling secrets, and authentication. Overall, Tekton's ease of use and competitiveness compared to tools like Jenkins or GitHub Actions made it the preferred choice.
It is an open-source tool initially developed by Google for internal use, later open-sourced, and widely adopted for building and deploying applications in Kubernetes environments. When deployed in a Kubernetes cluster, Tekton seamlessly integrates with the environment, streamlining the application pipeline delivery process. It automatically triggers when code is merged into the main branch, operating natively within Kubernetes without requiring additional external components. The automated pipeline, initiated by Tekton, builds the application, deploys it to specified container registries, and then to the Kubernetes cluster. Tekton's versatility shines in multi-environment setups like staging, testing, and production, efficiently managing the continuous integration (CI) part by triggering processes linked to code merges. Users often integrate Argo CD to complement Tekton in the continuous deployment (CD) phase. Argo CD pulls and deploys the latest application image within the Kubernetes cluster, creating a comprehensive and automated CI/CD workflow.
Tekton is the orchestration engine within OpenShift, which is our on-premise platform. Since we are not on the cloud yet, OpenShift plays a strategic role, and Tekton is a significant part of it. It serves as an orchestrator. In my experience of the last two years using Tekton and OpenShift pipelines, I haven't encountered many issues. As an orchestrator, Tekton works best. It's just one component of the larger OpenShift platform. Tekton consists of multiple components like events, trigger bindings, and more. However, when it comes to the overall OpenShift platform, being a platform as a service, most aspects are taken care of.
We are utilizing Tekton as a pipeline tool for their CI/CD process, which involves connecting GitLab to Nexus, then Nexus to Argo CD, and ultimately to Kubernetes.