mirror of
https://github.com/nubenetes/awesome-kubernetes.git
synced 2026-05-09 10:47:01 +00:00
5.6 KiB
5.6 KiB
Tekton and Tekton Pipelines
Introduction
- ==tekton.dev==
- github.com/tektoncd
- tekton.dev/try: Interactive Tutorials
- Tekton community
- github: Tekton Pipelines
- Tekton Pipelines Docs
- opensource.googleblog.com: The Tekton Pipelines Beta release
- tekline 🌟 tekline is a tekton delegated-pipeline to enable a bring-your-own pipeline configuration.
- Tekton PetClinic Demo
- Tekton PetClinic Demo Youtube
- OpenShift Tekton pipelines
- developers.redhat.com: An introduction to cloud native CI/CD with Red Hat OpenShift pipelines
- blog.openshift.com: cloud native CI/CD with openshift pipelines
- learn.openshift.com/middleware/pipelines
- Easily reuse Tekton and Jenkins X from Jenkins
- lambda.grofers.com: Evolving Continuous Delivery in a Cloud-Native Environment 🌟 In thispost, we’ll discuss the stages through which continuous delivery infrastructure has evolved at Grofers. We’ll start with how we began with Kubernetes and Jenkins and managed itsgrowing adoption. We’ll then discuss why we decided to move from Jenkins to Tekton, how we plan to scale it beyond a few teams, and what kind of challenges we have faced and arecurrently facing.
- We started with Jenkins shared libs, and wrote common implementation for one group of engineering teams. This worked very well because not only were we able to consolidate and refactor all pipelines at once leading to several optimizations, it also made it easy to understand the CI implementation for all similar services and if we were to add common features and bug fixes it was really easy to push it through a common implementation.
- There were benefits of doing this, but what was not desirable is that it took us a lot of effort to build these shared libs and despite our efforts to keep them simple, they ended up looking very complicated. Standard pipeline specs had departed from being declarative in nature and there was a lot of imperative Groovy logic mixed with Pipeline DSL.
- itnext.io: Tekton Pipelines Kickstarter. Cloud Native CI/CD with Tekton — Laying The Foundation
- cd.foundation: Tekton Pipelines Kickstarter. Cloud Native CI/CD with Tekton — Building Custom Tasks
- openshift.com: Running Testcontainers in OpenShift Pipelines With Docker-in-Docker (with Tekton)
- blog.harbur.io: The Seven Steps to build a Cloud Native CI/CD for GitHub repos using Tekton
- itnext.io: Cloud Native CI/CD with Tekton — Building Custom Tasks Learn how to use, buildand deploy custom Tasks for Cloud-Native CI/CD on Kubernetes with Tekton Pipelines…
- ==opensource.com: Write your first CI/CD pipeline in Kubernetes with Tekton== 🌟 Tekton is a Kubernetes-native open source framework for creating continuous integration and continuous delivery (CI/CD) systems.
- opensource.com: Dynamic scheduling of Tekton workloads using Triggers Upgrade your CI/CD pipeline with this Kubernetes-native application. Tekton Triggers is a Tekton component that allows you to detect and extract information from events from various sources and execute TaskRuns and PipelineRuns based on that information. It also enables passing extracted information to TaskRuns and PipelineRuns from events.