Portable Pipelines

Thu, 21 Mar 2019 00:00:00 +0000

Every microservices team eventually reinvents the same pipeline. They copy and paste the YAML from the last service they built, change the image name, and call it done. For a while, it works fine.

Then a security vulnerability surfaces and you need to add a container scan step to every pipeline. Or you want to enforce a consistent artifact naming scheme. Or someone needs to change how environment variables are injected. Suddenly you’re touching 30 pipelines individually, hoping you get them all — and hoping they’re consistent enough to actually find.

Blog on CoreX

Portable Pipelines