tekton-kickstarter VS catalog

# https://github.com/MartinHeinz/tekton-kickstarter/blob/master/misc/config.yaml apiVersion: v1 kind: ConfigMap metadata: name: repo-app-mapping data: repo-app-mapping.yaml: | '[email protected]:kelseyhightower/nocode.git': 'nocode' '[email protected]:MartinHeinz/blog-frontend.git': 'blog-backend' '[email protected]:MartinHeinz/game-server-operator.git': 'game-server-operator' '[email protected]:MartinHeinz/python-project-blueprint.git': 'sample-python-app' --- # https://github.com/MartinHeinz/tekton-kickstarter/blob/master/tasks/get-application-name/get-application-name.yaml apiVersion: tekton.dev/v1beta1 kind: ClusterTask metadata: name: get-application-name spec: params: - name: repository-url type: string - name: mapping-file type: string steps: - name: get-application-name image: mikefarah/yq script: | #!/usr/bin/env sh set -xe yq e '."$(params.repository-url)"' /config/$(params.mapping-file) | tr -d '\012\015' > /tekton/results/application-name results: - name: application-name # Can be accessed by other Tasks with $(tasks.get-application-name.results.application-name) workspaces: - name: config mountPath: /config

Tekton is a versatile tool that can get quite complicated and therefore one short article definitely isn't enough to go over every piece of it in detail. This introduction should give you enough to get up and running with all the configurations in place. In the following articles in these series, we will explore how to use and build your own custom Tasks and Pipelines, deal with event handling - both HTTP events and scheduled with cron and much more. So, stay tuned for next article and in the meantime you can have a sneak peek at files in tekton-kickstarter repository where all the resources from this and following articles are already available. And in case you have some feedback or suggestion feel free to open an issue in the repository or just star it if like you the content. 😉

Article: https://itnext.io/cloud-native-ci-cd-with-tekton-laying-the-foundation-a377a1b59ac0 Repository: https://github.com/MartinHeinz/tekton-kickstarter

May be this https://github.com/tektoncd/catalog/issues/1052 bug…

The most obvious way would be copying and pasting the steps, but for more complex scenarios, where there are n tasks, this becomes error prone. Using a template engine like helm could help, but learning another templating engine, plus having to change the contents of said tasks also becomes a burden. Instead, kustomize has a set of tools to make this job easier, while enjoying reutilizing tasks from the tektoncd/catalog.

Another common thing that you might need in your Tasks is some kind of a storage where you can write data that can be used by subsequent steps in the Task or by other Tasks in the pipeline. The most common use case for this would be a place to fetch git repo. This kind of a storage is called workspace in Tekton and the following example shows a Tasks that mounts and clears the storage using rmdir: