That is, you define the inputs and outputs of a job, then Concourse derives how to carry out your jobs in the correct order under the correct conditions.

A Concourse yaml file is pretty flat, as a consequence.

That's a great writeup. I think you'd find Concourse attractive.

I couldn't find any docs on intra pipeline dependency management though, any links?

Thanks!

As for my own project, we have an increasing group of downstream consumers of our API. There are a few ways I could signal upgrades. They could just watch my repo and narrow it to the directories they're interested in. I can also publish a file on S3 or push into a git repo that they watch.