1
0
mirror of https://github.com/tektoncd/catalog.git synced 2024-11-27 06:27:23 +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
pratap0007 4b981548a2 This patch splits gke-deploy task from the gke-deploy directory
Changes include:
  - moves the gke-deploy task to the task directory
  - copies and modifies readme file for gke-deploy from gke-deploy directory
  - copies example directory from gcs directory

Issue: #386

Signed-off-by: Shiv Verma <shverma@redhat.com>
2020-07-13 13:41:58 +01:00
.github Fix yaml lint errors and warnings 2020-06-25 17:20:59 +01:00
git Modifies git-cli task from git directory according to the new reorg proposal 2020-07-10 22:06:57 +01:00
gke-deploy This patch splits gke-deploy task from the gke-deploy directory 2020-07-13 13:41:58 +01:00
golang Modifies golangci-lint task from golang directory according to the new reorg proposal 2020-07-10 22:06:57 +01:00
helm Modifies helm-upgrade-from-source task from helm directory 2020-07-10 22:06:57 +01:00
openshift-client Modifies openshift-client task from openshift-client directory according to the new reorg proposal 2020-07-10 22:06:57 +01:00
task This patch splits gke-deploy task from the gke-deploy directory 2020-07-13 13:41:58 +01:00
test Enables the yamllint job 2020-06-25 17:20:59 +01:00
vendor/github.com/tektoncd/plumbing Bump plumbing to recent master 👼 2020-05-06 18:56:36 +01: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 Handle TaskRun as well as PipelineRun tests 2020-04-08 23:15:01 +01:00
DEVELOPMENT.md Combine DEVELOPMENT.md and CONTRIBUTING.md 2020-03-03 10:51:45 -06:00
Gopkg.lock Bump plumbing to latest changes 🔗 2019-11-15 09:52:31 -06: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 README.md: update v1alpha1/v1beta1 header 2020-06-19 16:08:03 +02:00
recommendations.md Add a "Run as non root" recommandation… 2020-06-10 09:02:55 +01:00
roadmap.md Add 2020 roadmap 🛣️ 2020-04-07 06:59:00 +01:00

Tekton Catalog

If you want v1alpha1 resources, you need to go to the v1alpha1 branch. The master branch is synced with v1beta1 since 2020, 19th June.

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).

See our project roadmap.

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 golang/build.yaml
task.tekton.dev/golang-build created

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

$ kubectl get tasks
NAME           AGE
golang-build   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/v1beta1
kind: TaskRun
metadata:
  name: example-run
spec:
  taskRef:
    name: golang-build
  params:
  - name: package
    value: github.com/tektoncd/pipeline
  workspaces:
  - name: source
    persistentVolumeClaim:
      claimName: my-source

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/v1beta1
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.

See our project roadmap.