-
# Expected Behavior
Specify a serviceaccount from an other namespace must be allowed in trigger object
# Actual Behavior
If the serviceaccount used in the EventListener has not the right to i…
-
# Log
```shell
1.683615978721644e+09 INFO controller.run-filter Inspecting BuildRun instance for Tekton's CustomRun ownership {"generation": 1, "namespace": "default", "name": "trigger-bhfw…
-
{
"hub-mirror": [
"gcr.io/tekton-releases/github.com/tektoncd/pipeline/cmd/entrypoint:v0.44.4",
"gcr.io/tekton-releases/github.com/tektoncd/pipeline/cmd/nop:v0.44.4",
"…
-
# Expected Behavior
Triggers are an excellent way to provide a partially configured set of runtime resources, and isolated a limited number of parameters that are relevant for specific use cases.
…
-
I tried the current 4.6 lab with the amended pipeline and trigger yamls for 4.7 on a 4.8 install and everything worked except the trigger step.
I used this GIST to accelerate through
[https://gis…
-
### Feature request
Currently by default the dashboard install using the operator is setting the default namespace for tekton pipelines and tekton triggers to 'tekton-pipelines' . In certain use ca…
-
# Expected Behavior
I can `kubectl diff` tekton triggers resources
# Actual Behavior
On the plumbing repo:
```
$ kubectl diff -k tekton/resources
Error from server (InternalError): Internal …
-
{
"hub-mirror": [
"gcr.io/tekton-releases/github.com/tektoncd/triggers/cmd/eventlistenersink:v0.18.1$triggers-cmd-eventlistenersink"
]
}
-
{
"hub-mirror": [
"gcr.io/tekton-releases/github.com/tektoncd/triggers/cmd/controller:v0.18.1$triggers-cmd-controller"
]
}
-
{
"hub-mirror": [
"gcr.io/tekton-releases/github.com/tektoncd/triggers/cmd/interceptors:v0.18.1$triggers-cmd-interceptors"
]
}