End to end Continuous Delivery tools

From CitconWiki
Revision as of 07:41, 24 August 2013 by Citconjoe (talk | contribs) (Created page with "Idea: A tool to open up, input the CD workflow and it's done. Does this exist? Does it need to exist? '''General workflow''' -Someone checks code in to version control -Chec...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

Idea: A tool to open up, input the CD workflow and it's done. Does this exist? Does it need to exist?


General workflow -Someone checks code in to version control -Checkin gets picked up by build server -artifact repository or source control or build tool -Script infrastructure: chef/puppet/custom scripts (should be version controlled) -Deploy (chef, Capistrano, shell scripts, manually -Testing -UAT /(business sign off) -Roll to Production


Thoughts Teams use their own build tools and they come together in an artifact repo. For example, 1000 people working on the app(s). Do we want everything to go to a centralized CI server, or do we want devs to be more involved? Teams can have a local CI server, but it would be nice to still have a CD workflow on the ops level.

What are people doing today?

Retrieved from "http://citconf.com/wiki/index.php?title=End_to_end_Continuous_Delivery_tools&oldid=15298"