1
0
mirror of https://github.com/tektoncd/catalog.git synced 2024-11-21 05:55:35 +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
Piyush Garg 658c021e86 Fix image throwing error
This change will fix the issue of client
task giving error on tekton 0.5.0

Also tag the image with pipeline version
inspite of always latest

Fix #78
2019-09-19 10:19:11 -05:00
.github Add any missing basic docs 📝 2019-04-30 02:14:52 -05:00
argocd Fix argocd incorrect usage of ARGOCD_USERNAME/ARGOCD_USERNAME in login step; support parameterizing argocd image version 2019-07-10 03:11:50 -05:00
buildah workingDir typo 2019-07-17 09:48:52 -05:00
buildkit Add BuildKit Task 2019-05-14 13:08:57 -05:00
buildpacks Add compatibility note 2019-07-22 10:16:55 -05:00
conftest Added task for Conftest 2019-09-05 08:57:06 -05:00
golang Support to set go11module in golang task 2019-08-30 07:59:04 -05:00
jib-maven Adding a Task for jib-maven 2019-05-04 09:20:53 -05:00
kaniko Add a specific version and context support for kaniko 2019-05-24 02:41:00 -05:00
kn Fix #73 2019-09-16 09:58:10 -05:00
knctl Initial knctl task definition 🌮 2019-06-06 11:52:06 -05:00
kubeval Added task for Kubeval 2019-08-19 03:39:59 -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 Fix image throwing error 2019-09-19 10:19:11 -05:00
openwhisk OpenWhisk on Knative 2019-08-27 12:19:03 -05:00
s2i s2i/Dockerfile run yum update in docker image 2019-09-03 10:47:06 -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 Bump tektoncd/plumbing with latest fixes 2019-06-05 03:56:06 -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 Bump tektoncd/plumbing with latest fixes 2019-06-05 03:56:06 -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 Add bobcatfish to owners 👼 2019-09-11 14:54:08 -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