@@ -18,10 +18,14 @@ The life cycle of this app is handled through many tools and methods that we dev
...
@@ -18,10 +18,14 @@ The life cycle of this app is handled through many tools and methods that we dev
Obviously the developers needs to respect the Contributing guidelines provided by the original authors to make the automation possible and smooth. For example, frequent and light commits are needed in order to make debugging easier and, in turn, also make patching easier.
Obviously the developers needs to respect the Contributing guidelines provided by the original authors to make the automation possible and smooth. For example, frequent and light commits are needed in order to make debugging easier and, in turn, also make patching easier.
The project remote repository is hosted on GitLab.com as a public project.
2.**CI/CD : Continuous Integration**
2.**CI/CD : Continuous Integration**
The Continuous Integration part is handled with our GitLab.com. The CI pipeline defined by the .gitlab-ci.yml file is triggered automatically through local commit. It means that every time you commit as a developer to your local working tree, the GitLab CI pipeline runs every stages and all the jobs they contain in a pre-defined order to build, test (at different granularity) and deploy your commit.
The Continuous Integration part is handled with our GitLab.com. The CI pipeline defined by the .gitlab-ci.yml file is triggered automatically through local commit. It means that every time you commit as a developer to your local working tree, the GitLab CI pipeline runs every stages and all the jobs they contain in a pre-defined order to build, test (at different granularity) and deploy your commit.
I chose GitLab.com as the automation platform to be able to respect the configuration-as-code easily. This way the pipeline definition is right next to the source code of the application it is maintaining.
3.**CI/CD : Continuous Delivery**
3.**CI/CD : Continuous Delivery**
If all CI jobs pass it's time for the CD pipeline to run. This Continous Delivery pipeline is meant to check for the deployability of the uploaded new code on a frequent basis. It ensures that we can safely deploy the application integrating this code while keeping stability.
If all CI jobs pass it's time for the CD pipeline to run. This Continous Delivery pipeline is meant to check for the deployability of the uploaded new code on a frequent basis. It ensures that we can safely deploy the application integrating this code while keeping stability.
