Difference between revisions of "IT-SDK-CICD"

From wiki.samerhijazi.net
Jump to navigation Jump to search
(CI-CD-CD)
Line 1: Line 1:
 
=CI-CD-CD=
 
=CI-CD-CD=
* Continuous Integration (CI): Is an automation process. In which code changes from multiple contributors (built, tested, and merged) to a shared repository.
+
* Continuous Integration (CI): Is an automation process. In which code changes from multiple contributors are built, tested, and merged to a shared repository.
 
* Continuous Delivery (CD): Released to Repository. Where software (developer’s changes) manually deployed from the repository to a live production environment by the operations team.
 
* Continuous Delivery (CD): Released to Repository. Where software (developer’s changes) manually deployed from the repository to a live production environment by the operations team.
 
* Continuous Deployment (CD): Released to production. Where software (developer’s changes) automatically deployed from the repository to live production environment.
 
* Continuous Deployment (CD): Released to production. Where software (developer’s changes) automatically deployed from the repository to live production environment.

Revision as of 13:05, 2 June 2021

CI-CD-CD

  • Continuous Integration (CI): Is an automation process. In which code changes from multiple contributors are built, tested, and merged to a shared repository.
  • Continuous Delivery (CD): Released to Repository. Where software (developer’s changes) manually deployed from the repository to a live production environment by the operations team.
  • Continuous Deployment (CD): Released to production. Where software (developer’s changes) automatically deployed from the repository to live production environment.

Continuous Delivery vs Continuous Deployment

Cd-vs-cd.jpg

Ref

Jenkins

  • Creating artifact for the build.
  • Artifact was added to the build.
  • In Jenkins-GUI: $WORKSPACE; in Jenkinsfile: ${WORKSPACE}