Thanks for the post! This helped me more carefully examine Concourse while I’ve been evaluating it as a CI solution.

However, my experience has been different, maybe you were working with an older version?

There’s no way to edit tasks in the UI on purpose, because if you change a task definition in the UI, your pipeline will no longer be fully declared from your version controlled YAML files, — this is a feature of Concourse, not a bug. No snowflake build servers! You can execute builds from the UI.

The fly binary can be downloaded from the Concourse UI, and it provides a mechanism to replace itself with an updated version from whatever concourse instance you point it to. (`fly sync`)

There is now a secrets mechanism in Concourse.

You can and I have run a pipeline with multiple Docker images from multiple sources in series or in parallel, just specify a different image in the task and/or a different docker-image resource.

RE: Uber Docker image with database and dependancies built in, — you can build this artifact with steps in your pipeline. E.G. a step that gets an image and adds your code, which outputs to a step that fetches a DB, which outputs those both to a step that runs the app/tests. You could then even selectively choose from all those inputs and create a final Docker artifact at the end.