Full Disclosure: I also work at Pivotal on a team that has done a large amount of automation using Concourse (check out our pipelines [1]) Things that we've do

Full Disclosure: I also work at Pivotal on a team that has done a large amount of automation using Concourse (check out our pipelines [1]) Things that we've done so far with Concourse: * A dependency check notifier that based on an RSS feed from various language maintainers: Sends an email, updates our pivotal tracker account, sends a message to our slack channel * A job, that based on the completion of a build will upload the resulting artifact to Github and tag the release with a new version, auto generated release notes and checksums * Travis.ci style github pull request analysis * A security feed monitor that notifies us when a part of our application is vulnerable and when it is, kicks off a build and sends an email notification * Automatically updates submodules and gems for git repos and runs specs and tests against the updated artifact. These tasks were not difficult to implement. Every pipeline for Concourse is explicitly defined in its configuration file [2], which we version control. There is never any reconfiguring or rebuilding "snowflake" servers when we re-deploy our Concourse VMs. They rebuild identically based on the config files. [1] - http://buildpacks-ci.cfapps.io http://buildpacks-ci.cfapps.io (Chrome friendly, Firefox not) [2] - https://github.com/cloudfoundry/buildpacks-ci https://github.com/cloudfoundry/buildpacks-ci