Seems somewhat similar to resources[0] in Concourse in that they use a container image that has a defined entry point. Concourse refers to this as a "get step"

Seems somewhat similar to resources[0] in Concourse in that they use a container image that has a defined entry point. Concourse refers to this as a "get step"[1] or a "put step", which calls a pre-defined script inside the container with a custom set of parameters. The "put step" is used when you expect side effects, while a "get step" is used to check status on some resource and trigger jobs. In general it makes the CI/CD system easily composable and clean. Concourse manages this very well and while I haven't used Bitbucket Pipes I suspect it to be a good experience as well. [0] https://concourse-ci.org/resources.html https://concourse-ci.org/resources.html [1] https://concourse-ci.org/implementing-resources.html https://concourse-ci.org/implementing-resources.html