GitXplorerGitXplorer
j

tekton-catalog

public
1 stars
0 forks
0 issues

Commits

List of commits on branch main.
Unverified
22bc1f795e8cdd9f4a63a30d88754a0e19db4288

Adding useful go commands.

committed 2 years ago
Unverified
3b7d56ce4bd0952393bc0ca3fff33da4aef09882

Add dev container support

committed 2 years ago
Unverified
a7bfc223c59a0578f459c07be38c94fdad977189

Ignore sensitive info

committed 2 years ago
Unverified
d76aeae00852009ed4135efebc8d3a6a3310d033

LFS tracking PNG in case I need images for documentation

committed 2 years ago
Verified
6e6629cdda0b812e7974ec51fd809f8ff2a3b147

Initial commit

jjkamenik committed 2 years ago

README

The README file for this repository.

tekton-catalog

My own personal catalog of tekton tasks

Local Development

Clone the repo git clone git@github.com:jkamenik/tekton-catalog.git

Open it in VSCode

cd tekton-catalog
code .

Containers

Tekton tasks are containers. All containers here are written in either go or bash.

They should be in the ./containers/<task name>/<major>.<minor> directories

This directory should contain a Dockerfile that builds the source from that directory. Any source or vendored libraries should be stored there as well.

The bin/build command can be used to build containers easily with a consistent name: [<repo path>]<task name>:<major>.<minor>-<date>. For example:

  1. matrix:1.1
  2. jkamenik/matrix:1.1

The following LABEL adjust how the tags are generated:

  1. Repo - adds a prefix (the repo path) to the container name (i.e., gcr.io/foo/). Don't forget the trailing /.
  2. Tag - A static tag to use as well. Often a -latest or something similar gcr.io/foo/matrix:1.1-latest.

When in doubt use the bin/tags command to get a new line separated list of tags for the container.

Tasks

Tekton tasks are yaml files that can be applied to a K8s cluster that has tekton installed. They pair with a container that is built from the ./container directory.