Currently, our build pipelines are separated, with one file per repository [1]. In total, we have 11 repositories, 2 of which are related to operators. This means that in cases of maintenance or changes to these pipelines, the workload would likely be multiplied by the number of repositories involved.

The goal of this task is to analyze whether it would be viable and recommended to unify the build pipeline files into a single shared pipeline, at least for the repositories that have several steps and tasks in common, such as koku, koku-daily, and nise-populator.

Key points to consider:
a) Is it feasible to move the build pipeline file out of its respective repository?
b) If customization is required for specific repositories, how would we handle it? (We know this is unlikely to happen often, but it’s worth to think about it).

For more context, you can check the related Slack threads:

1. https://redhat-internal.slack.com/archives/C04476G1F7H/p1734011993461459
2. https://redhat-internal.slack.com/archives/C06M5T9SSKW/p1734099168543669?thread_ts=1734081644.506009&cid=C06M5T9SSKW

[1] We have .tekton directories with pipelines files, such as: https://github.com/project-koku/koku/tree/main/.tekton and https://github.com/project-koku/koku-daily/tree/main/.tekton