gabrielr

Right. One of my favorite parts of Concourse is that all the config is declarative, in YAML that teams can (and do) check into a public Git repo (with the secrets kept elsewhere).

That lets teams share Concourse task and resource definitions. Many teams (including mine) publish our pipeline definitions too [0]. This enables "tooling" type teams build components that get a lot of re-use by other teams.

disclaimer: I work for Pivotal.

[0] e.g. code.cloudfoundry.org/cf-networking-ci

> Just trying to find logs is a pain, and getting the UI to show a full log output is basically impossible

Have you tried `fly watch`? It will stream logs from in-flight builds, or show the full output of completed ones.

Thanks everyone -- good things to think about.

This makes me wonder "What if two programs did this?" [1]

[1]: http://blogs.msdn.com/b/oldnewthing/archive/2005/06/07/42629...