Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Building CI/CD Systems Using Tekton
  • Table Of Contents Toc
  • Feedback & Rating feedback
Building CI/CD Systems Using Tekton

Building CI/CD Systems Using Tekton

By : Joel Lord
5 (3)
close
close
Building CI/CD Systems Using Tekton

Building CI/CD Systems Using Tekton

5 (3)
By: Joel Lord

Overview of this book

Tekton is a powerful yet flexible Kubernetes-native open source framework for creating continuous integration and continuous delivery (CI/CD) systems. It enables you to build, test, and deploy across multiple cloud providers or on-premise systems. Building CI/CD Systems Using Tekton covers everything you need to know to start building your pipeline and automating application delivery in a cloud-native environment. Using a hands-on approach, you will learn about the basic building blocks, such as tasks, pipelines, and workspaces, which you can use to compose your CI/CD pipelines. As you progress, you will understand how to use these Tekton objects in conjunction with Tekton Triggers to automate the delivery of your application in a Kubernetes cluster. By the end of this book, you will have learned how to compose Tekton Pipelines and use them with Tekton Triggers to build powerful CI/CD systems.
Table of Contents (20 chapters)
close
close
1
Section 1: Introduction to CI/CD
4
Section 2: Tekton Building Blocks
12
Section 3: Tekton Triggers
15
Section 4: Putting It All Together

Adding a finally task

So far, all the pipelines that you built did not persist any data. Once the pods were terminated everything was taken down with them, and the next run always started from a fresh environment.

This won't always be the case. Most of the time, you will clone a code repository and store it on a PersistentVolumeClaim (PVC) for all tasks to access it. This exact scenario will be introduced in Chapter 7, Sharing Data with Workspaces. When you start using workspaces, you will need to clean up your persisted data to start with a clean environment each time. This is where finally tasks will come into play.

Those tasks will always be executed, even after there was a task that failed in the pipeline. Let's demonstrate this:

  1. Create a new file called cleanup.yaml and create a task called cleanup:
    apiVersion: tekton.dev/v1beta1 
    kind: Task 
    metadata: 
      name: cleanup 
    spec: 
  2. This task has a single step named clean. It uses a UBI to execute...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech

Create a Note

Modal Close icon
You need to login to use this feature.
notes
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Delete Note

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Edit Note

Modal Close icon
Write a note (max 255 characters)
Cancel
Update Note

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY