-
I found some old Copland install stuff. Included was a font suitcase called Tekton Plus. Tekton Plus would have been used to show off the QuickDraw GX font stuff, including glyphs for small caps, supe…
-
**Actual behavior**
With the latest release (last night), some of our e2e tests fail with:
```
INFO[0000] CMD ["echo Hello World"]
INFO[0001] Skipping push to container re…
-
We need to provide the ability to set a failure criteria in the container vulnerability scanning task which would result in the termination of the build. The build results, along with the scan output…
-
# Expected Behavior
When running a nested pipeline configuration, the node selector value is not passed to child pipelines. This results in nodeSelector being None.
# Actual Behavior
Node select…
-
I have a setup where we have `Pipeline`, some `Task`s and a `TriggerTemplate`. Pipelines are triggered by a Github webhook, so we are not manually creating `PipelineRuns` or `TaskRuns`.
Now, I woul…
-
When trying to install the tekton operator on okd using the operatorhub.io it installs version 0.61
there are 2 yaml files below
edit: no more error, this was due to the use of the wrong image …
-
# Expected Behavior
Not sure if this is the expected behavior, I just thought that this was pretty confusing for my scenario, let me know what you think.
I have PipelineRun that runs something like …
-
# Expected Behavior
task generating array:
```yaml
apiVersion: tekton.dev/v1
kind: Task
metadata:
name: build-kaniko-env-vars
spec:
workspaces:
- name: source
description: …
-
Tracking issue for integration with [Tekton Triggers](https://github.com/tektoncd/triggers).
Our goal here is to start recording input events (e.g. Push/Pull Request payload) as part of results, an…
-
# Expected Behavior
Taskrun describe/get should show any information about the workspaces which use default workspace binding
# Actual Behavior
Taskrun describe/get does not show any information …