Hacker News new | past | comments | ask | show | jobs | submit login

We use https://gocd.io/ so I'll comment on this:

> - Truly a pipeline based stages. No messing around with git branches/tags for each environment release.

That's how we use it. We have two or more stages for each environment (repo upload + installation, often tests) that are simply chained.

> - Ability to combine multiple builds together.

You can do fan-in and fan-out between pipelines (you can combine multiple pipelines in a DAG).

> - Build dependencies. Ability to trigger project-B build when project-A build succeeds. (Docker Cloud Builds have something like this.)

As above, with a graph of pipelines. We use this to trigger rebuild of some projects when libraries change.

> - Use the same artifact across multiple build stages.

You can reference and retrieve artifacts from all previous stages, even stages from upstream pipelines. The syntax for referencing takes some time to get used to.

> - An option to promote a build to the next step either manually or automatically.

automatic is default, but you can have manual approval steps, optionally with permissions attached to them.

Plug: I wrote a book that uses GoCD for its examples: https://leanpub.com/deploy




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: