-
# Expected Behavior
A single 'dev.tekton.event.pipelinerun.successful.v1' event after a successfull pipelinerun.
# Actual Behavior
Sometimes, duplicate events are being sent out:
```
Cont…
ghost updated
3 years ago
-
### Feature request
When a component removes a resource from their release build it would be great to have that resource removed during operator's upgrade cycle.
### Use case
In Tekton Pipeli…
ghost updated
3 years ago
-
Tekton is the component that allows us to define and create CI/CD pipelines. It is a cloud-native CI/CD tool.
Tekton defines Pipelines, which consist of Tasks, which in turn consist of Steps. Step…
-
# Versions and Operating System
- Kubernetes version:
**Output of `kubectl version`:**
```
Client Version: version.Info{Major:"1", Minor:"10+", GitVersion:"v1.10.0+b3b92b2", GitCommit:…
-
# Expected Behavior
# Actual Behavior
# Steps to Reproduce the Problem
```
apiVersion: triggers.tekton.dev/v1alpha1
kind: EventListener
metadata:
name: listener
spec:
serviceAccount…
-
### Which section(s) is the issue in?
I dont know where the Tekton docs live within the OpenShift docs but @Preeticp recomended I open this here.
https://tekton.dev/docs/triggers/eventlistener…
itewk updated
3 years ago
-
Add an action to be able to install Tekton on a cluster which doesn't have Tekton installed.
**Kubernetes:**
https://github.com/tektoncd/pipeline/blob/master/docs/install.md
https://github.com/t…
-
# Expected Behavior
EventListnere respond to github webhook reequest
# Actual Behavior
Unable to register github webhook, getting the following inside the `EventListener` logs
```
{"level…
-
I'm running the MLFlow sklearn e2e workflow example, as documented, and the first workflow run always gets stuck in the build step and remains in a pending state for several minutes.
Here's some re…
-
As currently worded, SLSA 1 unintentionally requires that the build steps were defined in some source material, i.e. "config as code". This is a problem because it excludes many build systems where su…