[margor]

I don't have a website yet, but I recently hooked myself up to work on yet another CI/CD solution. Hear me out before you say "booring!".

What if you could migrate to a CI/CD that is better to fit your organization _without_ changing any existing definitions?

What if your new fancy CI/CD could support your existing github-actions/bitbucket pipelines/circleci.yml definitions right out of the box?

And what if you could progressively migrate to some new/other format that fits your needs better without having to create multi-year organization wide migration to the "new and better CI"™, only to do it _yet again_ once vendor goes out of business?

So that's my idea. I admit, the endeavor is really big, since supporting multiple formats which often don't have direct equivalents between each other seems like a really hard thing to do. But I strongly believe this is real problem, because according to my n=1 experience, every organization sooner or later faces this challenge, and the fact that all vendors force you to migrate to their custom format for defining, what is essentially a DAG of tasks is outrageous to me.