James,

Thanks for the detailed answer. We started treating Jenkins views as the
representation of a particular space and each view contains many of jobs
for that push one app to that space.

autopilot plugin is definitely a move in the right direction, but we have a
richer deployment story --- we run smoke tests before we switch the routes.
We are implementing lower-level primitives that support this level of
granularity.

We are currently using Java, but will probably switch to Go if our approach
works (and we find time to learn Go)

Thanks,
David

--
http://www.linkedin.com/in/dvydra
http://www.testdriven.com
http://twitter.com/vydra