1
0
mirror of https://github.com/tektoncd/catalog.git synced 2024-11-23 06:08:46 +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
Vincent Demeester 5c2ab7d6c3 Linting yamls with yamllint 🏷
Next update of plumbing will enable `yamllint` check, so this make
sure we have linted yaml before 👼

Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
2019-11-15 09:39:31 -06:00
.github Add any missing basic docs 📝 2019-04-30 02:14:52 -05:00
ansible-tower-cli Linting yamls with yamllint 🏷 2019-11-15 09:39:31 -06:00
argocd Linting yamls with yamllint 🏷 2019-11-15 09:39:31 -06:00
buildah Linting yamls with yamllint 🏷 2019-11-15 09:39:31 -06:00
buildkit Linting yamls with yamllint 🏷 2019-11-15 09:39:31 -06:00
buildkit-daemonless Linting yamls with yamllint 🏷 2019-11-15 09:39:31 -06:00
buildpacks Linting yamls with yamllint 🏷 2019-11-15 09:39:31 -06:00
conftest Linting yamls with yamllint 🏷 2019-11-15 09:39:31 -06:00
gcloud Add gcloud Task 2019-10-02 09:59:15 -05:00
gke-deploy Removed numbered list from Install Tekton Pipelines CLI section. 2019-11-13 15:13:31 -06:00
golang Linting yamls with yamllint 🏷 2019-11-15 09:39:31 -06:00
jib-maven Add Taskrun e2e testing 2019-11-14 08:10:31 -06:00
kaniko Linting yamls with yamllint 🏷 2019-11-15 09:39:31 -06:00
kn References latest kn release v0.10.0 in task 2019-11-07 10:28:29 -06:00
knctl Linting yamls with yamllint 🏷 2019-11-15 09:39:31 -06:00
kubeval Linting yamls with yamllint 🏷 2019-11-15 09:39:31 -06:00
makisu Update templating to use $(…) instead of ${…} 2019-09-24 08:36:12 -05:00
openshift-client Add initial OWNERS to some folders 📄 2019-10-23 04:53:23 -05:00
openwhisk Linting yamls with yamllint 🏷 2019-11-15 09:39:31 -06:00
s2i Linting yamls with yamllint 🏷 2019-11-15 09:39:31 -06:00
test Add Taskrun e2e testing 2019-11-14 08:10:31 -06:00
vendor/github.com/tektoncd/plumbing Bump tektoncd/plumbing dependency 2019-10-17 10:39:20 -05:00
.yamllint Linting yamls with yamllint 🏷 2019-11-15 09:39:31 -06: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 Update README and CONTRIBUTING with some submission guidelines 📖 2019-10-23 04:53:23 -05:00
DEVELOPMENT.md Add Taskrun e2e testing 2019-11-14 08:10:31 -06:00
Gopkg.lock Bump tektoncd/plumbing dependency 2019-10-17 10:39:20 -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 @chmouel as an OWNER 2019-11-15 09:04:31 -06:00
README.md Set slack link to contact info section for slack 2019-10-31 09:02:27 -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. A directory can hold more than one task (e.g. golang).

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

Status of the Project

This project is still under active development, so you might run into issues. If you do, please don't be shy about letting us know, or better yet, contribute a fix or feature. Its folder structure is not yet set in stone either.