Skip to content
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

[FEATURE]: Merge all of the pipelines into one #146

Open
piotrpdev opened this issue Oct 13, 2023 · 0 comments
Open

[FEATURE]: Merge all of the pipelines into one #146

piotrpdev opened this issue Oct 13, 2023 · 0 comments
Labels
kind/documentation Improvements or additions to documentation kind/enhancement New feature or request priority/high Important issue that needs to be resolved asap. Releases should not have too many o

Comments

@piotrpdev
Copy link
Member

Details

Is your feature request related to a problem? Please describe.

  • Having to trigger several different pipelines is annoying for the end user.
  • It is difficult to transfer information between pipelines in Tekton.
  • It is difficult to trigger pipelines from other pipelines in Tekton.

Fixes #68

Describe the use-case or expected workflow

The user doesn't have to trigger several separate pipelines, instead they only trigger one. All of the pipeline-related work is done in one pipeline.

Describe alternatives you've considered

After looking into it, it seems the experimental Pipelines in Pipelines Tekton feature is much more underdeveloped than I thought. This is the approach I suggested in #68 (comment), however it seems like it won't be feasible any time soon.

Additional context

I still hold my concerns from #68 (comment), but I think this is a necessary choice to progress the PoC.

Considering that "Tekton indeed doesn't really offer any easy way to trigger one pipeline from another" and the issues we've been having keeping the pipelines separate (e.g. #137 (comment)) I now agree with @adelton's suggestion to merge the pipelines into one.

@piotrpdev piotrpdev added kind/documentation Improvements or additions to documentation kind/enhancement New feature or request priority/high Important issue that needs to be resolved asap. Releases should not have too many o labels Oct 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Improvements or additions to documentation kind/enhancement New feature or request priority/high Important issue that needs to be resolved asap. Releases should not have too many o
Projects
None yet
Development

No branches or pull requests

1 participant