-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove Tekton Triggers #438
Milestone
Comments
michaelsauter
added a commit
that referenced
this issue
Feb 9, 2022
Closes #438. All required functionality is now part of the ODS pipeline manager. Required for pipeline queueing, which is required to avoid pipeline run race conditions.
michaelsauter
added a commit
that referenced
this issue
Feb 9, 2022
Closes #438. All required functionality is now part of the ODS pipeline manager. Required for pipeline queueing, which is required to avoid pipeline run race conditions.
michaelsauter
added a commit
that referenced
this issue
Feb 9, 2022
Closes #438. All required functionality is now part of the ODS pipeline manager. Required for pipeline queueing, which is required to avoid pipeline run race conditions.
michaelsauter
added a commit
that referenced
this issue
Feb 9, 2022
Closes #438. All required functionality is now part of the ODS pipeline manager. Required for pipeline queueing, which is required to avoid pipeline run race conditions.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At the moment we add an interceptor in the Tekton Triggers chain to pull off "CI as code". This was done in an attempt to stay close to "official" usage of Tekton.
It turns out we gain very little from this and needlessly complicate the architecture. Further, design proposal #407 (which aims to fix #394) requires that we control the creation of
PipelineRun
resources, which prevents us from using Tekton Triggers.Note that other projects (e.g. https://github.com/openshift-pipelines/pipelines-as-code) also do not use Tekton Triggers.
Therefore we are going to remove it. We only need to replicate two things in our own code:
The text was updated successfully, but these errors were encountered: