Commit 90e7f313 authored by David Diederich's avatar David Diederich
Browse files

Minor editorial updates

parent 93c72238
......@@ -5,7 +5,7 @@ Find the most recent documentation build [here](http://osdu.pages.community.open
A common place for shared CI/CD Pipeline files, for use will all OSDU projects.
[The OSDU Platform System project](https://community.opengroup.org/osdu/platform/system) (including sub-projects) makes use of [GitLab's built-in CI/CD capabilities](https://docs.gitlab.com/ee/ci/introduction/) to provide a CI/CD pipeline that runs automatically on commits to the project. The stages in the pipeline include:
[The OSDU Platform project](https://community.opengroup.org/osdu/platform) (including sub-projects) makes use of [GitLab's built-in CI/CD capabilities](https://docs.gitlab.com/ee/ci/introduction/) to provide a CI/CD pipeline that runs automatically on commits to the project. The stages in the pipeline include:
- Security scanning for known vulnerabilities (CVEs)
- Scanning for use of approved Licenses in submitted code and dependencies
......@@ -17,22 +17,21 @@ A common place for shared CI/CD Pipeline files, for use will all OSDU projects.
**Continuous Integration**
* Developers merge/integrate the code to Master as soon as developer made a progress on the feature. Usually everyone commits to the Master every day.
* Continuous Integration assumes a high degree of tests which are automated into the software. we have good automated testing coverage as we progress we need to add more test cases.
* Continuous Integration refers to Integrating code, building and testing code(Unit and Integration tests) within the development environment.
* Continuous Integration refers to Integrating code, building and testing code (Unit and Integration tests) within the development environment.
**Continuous Delivery**
* Continuous Delivery means that you are able to do frequent deployments to a testing enviornment and/or production environment but may choose not to do it, due to various reasons(Ex: businesses not ready or OSDU applicatiions note ready )
* Continuous Delivery means that you are able to do frequent deployments to a testing environment and/or production environment but may choose not to do it, due to various reasons (Ex: businesses not ready or OSDU applicatiions not ready)
**Continuous Deployment**
* Continuous Deployment means that every change goes through the pipeline and automatically(No manual approval) gets put into production, resulting in many production deployments every day.
* Continuous Deployment means that every change goes through the pipeline and automatically (No manual approval) gets put into production, resulting in many production deployments every day.
# A graphical overview of the CI/CD Pipeline:
**Cotinues Delivery is not ready and its just an idea for now but we will have to figure out how & where to run UAT and Performance tests.**
**Continuous Delivery is not ready and its just an idea for now but we will have to figure out how & where to run UAT and Performance tests.**
**Cotinues Deployment might not be applicable for OSDU.**
**Continuous Deployment might not be applicable for OSDU.**
![alt text](CD1.jpg "CI/CD Pipeline")
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment