1
0
mirror of https://github.com/tektoncd/catalog.git synced 2024-11-22 06:02:51 +00:00
This is a mirror of https://github.com/tektoncd/catalog.git because the tekton git resolver does not support caching of git repositories so each CI build is firing off many fetches of to github. By maintaining a mirror, I have a locally cached copy on the same physical machine as my CI jobs.
Go to file
2019-05-17 10:33:58 -05:00
.github Add any missing basic docs 📝 2019-04-30 02:14:52 -05:00
buildah Use image output instead of IMAGE param 2019-05-04 06:04:53 -05:00
buildkit Add BuildKit Task 2019-05-14 13:08:57 -05:00
buildpacks Use run image as image in export step 2019-05-07 17:25:55 -05:00
jib-maven Adding a Task for jib-maven 2019-05-04 09:20:53 -05:00
kaniko kaniko: set DOCKER_CONFIG 2019-05-10 09:12:56 -05:00
makisu Add a basic Task CRD validation test for all Tasks in the catalog. 2019-05-16 10:32:59 -05:00
openshift-client Use consistent naming openshift-client 2019-05-17 10:33:58 -05:00
test Add a basic Task CRD validation test for all Tasks in the catalog. 2019-05-16 10:32:59 -05:00
vendor/github.com/tektoncd/plumbing Use tektoncd/plumbing instead of knative/test-infra 2019-05-15 09:42:57 -05:00
code-of-conduct.md Initial commit with OWNERS, CONTRIBUTING.md and code-of-conduct.md. 2019-04-25 15:05:49 -05:00
CONTRIBUTING.md Add any missing basic docs 📝 2019-04-30 02:14:52 -05:00
DEVELOPMENT.md Add more documentation on development/contributing new submissions. 2019-05-03 10:00:53 -05:00
Gopkg.lock Use tektoncd/plumbing instead of knative/test-infra 2019-05-15 09:42:57 -05:00
Gopkg.toml Remove comments from Gopkg.toml and refer to the documentation 2019-05-15 10:34:57 -05:00
LICENSE Initial commit 2019-04-25 14:54:27 -05:00
OWNERS Initial commit with OWNERS, CONTRIBUTING.md and code-of-conduct.md. 2019-04-25 15:05:49 -05:00
README.md Update README.md 2019-04-26 18:25:51 -05:00

Tekton Catalog

This repository contains a catalog of Task resources (and someday Pipelines and Resources), which are designed to be reusable in many pipelines.

Each Task is provided in a separate directory along with a README.md and a Kubernetes manifest, so you can choose which Tasks to install on your cluster.

Task Kinds

There are two kinds of Tasks:

  1. ClusterTask with a Cluster scope, which can be installed by a cluster operator and made available to users in all namespaces
  2. Task with a Namespace scope, which is designed to be installed and used only within that namespace.

Tasks in this repo are namespace-scoped Tasks, but can be installed as ClusterTasks by changing the kind.

Using Tasks

First, install a Task onto your cluster:

$ kubectl apply -f bazel.yaml
task.tekton.dev/bazel created

You can see which Tasks are installed using kubectl as well:

$ kubectl get tasks
NAME    AGE
bazel   3s

OR

$ kubectl get clustertasks
NAME            AGE
cluster-bazel   3s

With the Task installed, you can define a TaskRun that runs that Task, being sure to provide values for required input parameters and resources:

apiVersion: tekton.dev/v1alpha1
kind: TaskRun
metadata:
  name: example-run
spec:
  taskRef:
    name: bazel
  inputs:
    params:
    - name: TARGET
      value: //path/to/image:publish
    resources:
    - name: source
      resourceSpec:
        type: git
        params:
        - name: url
          value: https://github.com/my-user/my-repo

Next, create the TaskRun you defined:

$ kubectl apply -f example-run.yaml
taskrun.tekton.dev/example-run created

You can check the status of the TaskRun using kubectl:

$ kubectl get taskrun example-run -oyaml
apiVersion: tekton.dev/v1alpha1
kind: TaskRun
metadata:
  name: example-run
spec:
  ...
status:
  completionTime: "2019-04-25T18:10:09Z"
  conditions:
  - lastTransitionTime: "2019-04-25T18:10:09Z"
    status: True
    type: Succeeded
...

Contributing and Support

If you want to contribute to this repository, please see our contributing guidelines.

If you are looking for support, enter an issue or join our Slack workspace