There is a point to this story, but it has temporarily escaped my mind...
Contact Me MyFaceBook MyLinkedIn MyGitHub MyTwitter

Why should I use a Continuous Deployment Server?

You most likely already have an automated build/continuous integration server. It will compile your code. It will run your tests: unit, integration, and acceptance. At this point, you might be inclined to think that it can also deploy directly to your various environments as well. However, most build servers only offer you the ability to run a script independent of whether that script is a script to compile the code or some other arbitrary set of commands… This is where a Continuous Deployment/Delivery Server becomes the right tool…

Manual Deployments

  • Time consuming
  • Repetitive
  • Boring
  • Error-prone

A common solution is to create deployment manuals but these can quickly become obsolete and out-of-sync…

Automated Deployments

  • Speed
  • Repeatable
  • Reliable

Treating the deployment as code allows the same deployment process to be executed regardless of the environment or role. It also allows the deployment process to be version controlled in a source control management system.

Copyright © 2022 by Julian Easterling. SOME RIGHTS RESERVED.
Privacy Policy              Terms of Use             

Creative Commons License
Except where otherwise noted, content on this site is
licensed under a Creative Common Attribution-Share Alike 4.0 International License.

All of the opinions expressed on this website are those of Julian Easterling and
do not represent the views of any of my current and previous clients or employers in any way.

If you notice an error on the site or content that has not been properly attributed, bring
it to my attention using the contact page and I will endeavor to fix it as soon as I can.

I accept no responsibility or liability for any damages incurred by following any of
my advice or by using any of the information on my site or of those sites that I link to.