Here is a quote from the current content of continuous-integration:
... process of merging developer's working code copies to a shared codebase frequently to prevent or minimize integration problems.
OK, I get that. But then there is also continuous-delivery and continuous-deployment, and that's where I continuously get a bit lost:
- How does continuous integration relate to continuous delivery and/or continuous deployment, assuming that somewhere along the line(s) via
integration you end up
delivering in a target environment where everything will be
- What's the difference between continuous delivery and continuous deployment?
Back in the days, before DevOps was called DevOps, we used terminology which might possibly help to understand these new DevOps terms, such as:
- promote to (or demote from) some pre-prod target, optionally combined with some type of regeneration process (compiles, binds, etc) to package all related components together in executable-like things. That's what should be similar/close to continuous integration, or not?
- distribute to some target environment, using something like FTP (if standard copies cannot bridge the gap), but do not yet activate it in the target. That's what should be similar/close to continuous delivery, or not?
- install (or activate) in some target environment, combined with things like binds, stop/start operations, etc. That's what should be similar/close to continuous deployment, or not?
Too much tag markdown makes it hard to read. That doesn't bring more context to the question so I think the Ords can be stressed by an _underline_
\_markdown\_ to ease the reading
I mean editing is a pain :) hint for answer http://blog.crisp.se/wp-content/uploads/2013/02/continuous-delivery-deployment-sm.jpg
Related StackOverflow post
My related answer: https://softwareengineering.stackexchange.com/a/358551/3385