Difference between revisions of "IT-SDK-CICD"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| + | =Ref= | ||
| + | * https://www.redhat.com/en/topics/devops/what-is-ci-cd | ||
| + | * https://www.softwarecollections.org/en/ | ||
| + | * src: https://paulhammant.com/2013/04/05/what-is-trunk-based-development/ | ||
| + | * src: https://trunkbaseddevelopment.com/ | ||
| + | * src: https://continuousdelivery.com/ | ||
| + | * src: https://8thlight.com/blog/doug-bradbury/2013/10/08/stuck-in-the-muck.html | ||
=CI-CD-CD= | =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 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. | ||
| − | |||
=Continuous Delivery vs Continuous Deployment= | =Continuous Delivery vs Continuous Deployment= | ||
| + | [[File:ci-cd-cd.png]] | ||
[[File:cd-vs-cd.jpg]] | [[File:cd-vs-cd.jpg]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
=Jenkins= | =Jenkins= | ||
* Creating artifact for the build. | * Creating artifact for the build. | ||
* Artifact was added to the build. | * Artifact was added to the build. | ||
* In Jenkins-GUI: $WORKSPACE; in Jenkinsfile: ${WORKSPACE} | * In Jenkins-GUI: $WORKSPACE; in Jenkinsfile: ${WORKSPACE} | ||
Revision as of 13:12, 2 June 2021
Ref
- https://www.redhat.com/en/topics/devops/what-is-ci-cd
- https://www.softwarecollections.org/en/
- src: https://paulhammant.com/2013/04/05/what-is-trunk-based-development/
- src: https://trunkbaseddevelopment.com/
- src: https://continuousdelivery.com/
- src: https://8thlight.com/blog/doug-bradbury/2013/10/08/stuck-in-the-muck.html
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
Jenkins
- Creating artifact for the build.
- Artifact was added to the build.
- In Jenkins-GUI: $WORKSPACE; in Jenkinsfile: ${WORKSPACE}
