Any opinion on pipelinesascode? about tekline

[joyrex2001]

Tekline was initiated when pipelines-as-code was still in a proof of concept phase, and therefor not useable for our setup. Beside this, the pipeline system we were building was bare kubernetes based, not OpenSHift.

The main requirements we had when starting this were:

• be able to share versioned standard pipelines
• be able to share versioned standard tasks
• be able to update tasks and pipelines without breaking current usage of these
• keep the pipeline configuration close to the soure repository that uses it
• allow bring-your-own-pipeline if there is no standard pipeline available

These requirements are all met with tekline, and I would not change the setup where this project originated from. After a couple of years, this has proven to be a good setup which allows both sharing of tasks, pipelines and also provide the ability to create custom pipelines if the teams desire to. Using git tags for versioning helps keeping builds stable during development of the shared standard pipelines and tasks (I am not a fan of ClusterTasks).

In projects where OpenShift is used, I show this tekline implementation, but suggest them to use pipelines-as-code as this is the opinionated approach for OpenShift. I don't know in detail if pac supports the requirments I mentioned earlier though.

[uqix]

Thanks for sharing, we have quite the same requirements