04_CI-CD-CD-Infrastructure.md

Continuous Integration, Continuous Delivery and Continuous Deployment Infrastructure

Table of Contents

• About
• The Tools
• Gitlab and Jenkins
  • GitLab
  • Jenkins

About

The following articles should explain what are all these processes:

• http://blog.crisp.se/2013/02/05/yassalsundman/continuous-delivery-vs-continuous-deployment
• https://www.atlassian.com/continuous-delivery/ci-vs-ci-vs-cd
• https://puppet.com/blog/continuous-delivery-vs-continuous-deployment-what-s-diff
• https://stackoverflow.com/questions/28608015/continuous-integration-vs-continuous-delivery-vs-continuous-deployment

The Tools

There are specialized tools that can be used to achieve Continuous Integration, Delivery and even Deployment. But that's not the whole story. Many source control, build, orchestration, provisioning and even testing tools are used to achieve Continuous Integration, Delivery and Deployment. There are also services that offer specialized features to achieve the same objectives.

Probably the most known specialized CI/CD systems are Jenkins, Travis (used a lot in GitHub stored projects), GitLab CI (now fully integrated part of GitLab).

Gitlab and Jenkins

For experiencing the CI/CD/CD processes, we'll be working with GitLab and Jenkins.

GitLab

Check the second assignment - part 1.

Jenkins

Check the second assignment - part 2.