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
Vincent Demeester 84bb6d320a jib-gradle: use workspace instead of GitResource 🐐
This migrate jib-gradle to use `workspace` instead of an input
`GitResource`.

This also updates e2e tests to use a `Pipeline` in order to clone the
repository in the workspace.

Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
2020-03-11 07:43:48 -05:00
.github Add info about yaml validation in github/pull_req_template 2019-11-18 11:49:32 -06:00
ansible-tower-cli Update README to change inputs/params levels 2020-03-06 09:01:47 -06:00
argocd Update README to change inputs/params levels 2020-03-06 09:01:47 -06:00
azure-cli Update README to change inputs/params levels 2020-03-06 09:01:47 -06:00
buildah buildah: use workspace instead of GitResource 🐐 2020-03-11 07:43:48 -05:00
buildkit Update README to change inputs/params levels 2020-03-06 09:01:47 -06:00
buildkit-daemonless Update README to change inputs/params levels 2020-03-06 09:01:47 -06:00
buildpacks buildpacks: use workspace instead of GitResource 🐐 2020-03-11 07:43:48 -05:00
conftest Update README to change inputs/params levels 2020-03-06 09:01:47 -06:00
gcloud Port gcloud to v1beta1 🐩 2020-03-06 09:01:47 -06:00
git Update README to change inputs/params levels 2020-03-06 09:01:47 -06:00
github Update README to change inputs/params levels 2020-03-06 09:01:47 -06:00
gke-deploy gke-deploy: use workspace instead of GitResource 🐐 2020-03-11 07:43:48 -05:00
golang Update README to change inputs/params levels 2020-03-06 09:01:47 -06:00
jib-gradle jib-gradle: use workspace instead of GitResource 🐐 2020-03-11 07:43:48 -05:00
jib-maven Update README to change inputs/params levels 2020-03-06 09:01:47 -06:00
kaniko Update README to change inputs/params levels 2020-03-06 09:01:47 -06:00
kn Update README to change inputs/params levels 2020-03-06 09:01:47 -06:00
knctl Update README to change inputs/params levels 2020-03-06 09:01:47 -06:00
kubeval kubeval: use workspace instead of GitResource 🐐 2020-03-11 07:43:48 -05:00
mail Update README to change inputs/params levels 2020-03-06 09:01:47 -06:00
makisu Update README to change inputs/params levels 2020-03-06 09:01:47 -06:00
maven Update README to change inputs/params levels 2020-03-06 09:01:47 -06:00
openshift-client Update README to change inputs/params levels 2020-03-06 09:01:47 -06:00
openwhisk Port openwhisk to v1beta1 🦇 2020-03-06 07:49:46 -06:00
pullrequest Add Task equivlalent of PullRequest PipelineResource ⚗️ 2020-03-06 09:37:47 -06:00
s2i s2i: use workspace instead of GitResource 🐐 2020-03-11 07:43:48 -05:00
slackmessage Update README to change inputs/params levels 2020-03-06 09:01:47 -06:00
terraform-cli Update README to change inputs/params levels 2020-03-06 09:01:47 -06:00
test Use PipelineRun instead of TaskRun in e2e 📎 2020-03-11 07:43:48 -05:00
tkn Update README to change inputs/params levels 2020-03-06 09:01:47 -06:00
vendor/github.com/tektoncd/plumbing Bump plumbing to latest changes 🔗 2019-11-15 09:52:31 -06: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 Combine DEVELOPMENT.md and CONTRIBUTING.md 2020-03-03 10:51:45 -06: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 Update README.md to use v1beta1 😌 2020-03-11 07:43:48 -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 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.