-
{
"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"
]
}
-
### Feature request
This issue tracks the requirements for the cloudevents controller to be in a position to be integrated with Tekton Pipeline as a standalone controller.
- [x] #835
- [ ] Sen…
-
TriggerTemplates are very generic and can (theoretically) be used to create anything. We initially made them very generic on purpose b/c this felt like a better design: less coupling = better!
Howe…
-
# Expected Behavior
The Tekton Chains controller should only create TaskRun attestations if the TaskRun succeeds.
# Actual Behavior
The controller creates TaskRun attestations regardless of the f…
-
# Expected Behavior
When there are resources for build pods required the pods will be left to the Kubernetes scheduler to find resources for the pods.
This is a requirement of Karpenter to find ca…
-
### Feature request
* We aim to add annotations to Pipelineruns created by Triggers.
* These annotations will be utilized in results to capture data for both summary and record.
We sugg…
-
# Expected Behavior
Have Openshift Pipelines operator installed succesfully
# Actual Behavior
Openshif Pipelines operator never gets a succesfull state
# Steps to Reproduce the Problem
…
-
This is kind of an Epic issue for moving towards having Tekton building Tekton.
The ultimate goal is to have all CI/CD (aka PR builds, periodics builds, release builds, commands handling, …) of the `…
-
Create a [tekton](https://tekton.dev/) basic tutorial
* understanding triggers
* understanding templates
* understanding tasks
* understanding pipeline