Skip to main content


Tekton is used in Otomi for the Builds self-service. When a Build is created, Otomi generates the Tekton Pipeline and Pipelinerun resources. There are 2 types op pipelines:

  • Docker for building images based on a Dockerfile
  • Buildpacks for building images using buildpacks

When Tekton is activated, Otomi will add 3 Tekton tasks to the team's namespace:

  1. Buildpacks
  2. git-clone
  3. kaniko

and use them in the pipelines.


  • When activated, the Tekton Helm chart will be installed
  • When a team is created and Tekton is active, Tekton tasks used by the pipelines will be added to the team namespace
  • When a build is created, the required pipeline and pipelinerun resources are created


When Otomi generates the manifest resources for the pipeline and the pipelinerun, the pipelinerun will automatically run the pipeline once. Use the following command to check if the status of the pipelinerun:

tkn pipelineruns logs  <name-of-the-pipelinerun> -n team-<team name>

If the build is changed in Otomi, the pipelinerun will not be re-started. Use the following command to start the pipeline after a change:

tkn pipeline start <name-of-the-pipeline>  --use-pipelinerun <name-of-the-pipelinerun>  -n team-<team name>

We will soon add the option to restart the pipeline after the build has been changed in Otomi.