Vespene is pretty new so a lot of things are up for grabs. Pipelines were implemented in about a day, so the potential to make rapid upgrades is pretty big.

That all being said, I think you have 95% of that right there today with http://docs.vespene.io/importing.html

This is a JSON file, and it can define what pipeline a project is part of, and what stage it is in that pipeline.

So it's like "this project is part of the analytics pipeline, and it is part of the deployment stage".

But you still have to make the analytics pipeline in the GUI right now. This means that you have to say (and this is all) the analytics pipeline has the following stages in order: A, B, C, and then D.

I think it's quite possible to have the definition OF the analytics pipeline in the vespene.json too, but it's a bit of a question of which one wins if there are conflicting definitions.

If you want to stop by talk.vespene.io this would be a great thing to bounce ideas around on!

I think https://concourse-ci.org/ is something you want to look at then.

Concourse has a really weird resources philosophy that makes it almost impossible to easily work with.

I'm a notorious Concourse fan, I'd be interested to understand why you think it's almost impossible to work with.

Weird in what way?

VSTS/Azure Devops is pretty good for this, as long as you host your own build servers. Their hosted solution is terrible.

All can be built through their UI, then exported to yml in your repos. Pretty good UI. Their service connections are good.