84bb6d320a
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> |
||
---|---|---|
.github | ||
ansible-tower-cli | ||
argocd | ||
azure-cli | ||
buildah | ||
buildkit | ||
buildkit-daemonless | ||
buildpacks | ||
conftest | ||
gcloud | ||
git | ||
github | ||
gke-deploy | ||
golang | ||
jib-gradle | ||
jib-maven | ||
kaniko | ||
kn | ||
knctl | ||
kubeval | ||
makisu | ||
maven | ||
openshift-client | ||
openwhisk | ||
pullrequest | ||
s2i | ||
slackmessage | ||
terraform-cli | ||
test | ||
tkn | ||
vendor/github.com/tektoncd/plumbing | ||
.yamllint | ||
code-of-conduct.md | ||
CONTRIBUTING.md | ||
DEVELOPMENT.md | ||
Gopkg.lock | ||
Gopkg.toml | ||
LICENSE | ||
OWNERS | ||
README.md |
Tekton Catalog
This repository contains a catalog of Task
resources (and someday
Pipeline
s and Resource
s), 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 Task
s to install on your
cluster. A directory can hold more than one task (e.g. golang
).
Task
Kinds
There are two kinds of Task
s:
ClusterTask
with a Cluster scope, which can be installed by a cluster operator and made available to users in all namespacesTask
with a Namespace scope, which is designed to be installed and used only within that namespace.
Task
s in this repo are namespace-scoped Task
s, but can be installed as
ClusterTask
s by changing the kind
.
Using Task
s
First, install a Task
onto your cluster:
$ kubectl apply -f golang/build.yaml
task.tekton.dev/golang-build created
You can see which Task
s 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.