|
Continuous Integration: new source code is added submitted to development tier codebase. Once new source code is submitted, it only makes it onto the development tier after several different types of automated testing are passed. These test types include, but are not limited to: unit, functional, acceptance, and data integrity.
|
|
###### [Home](home) / [Digitec Coding Practices](coding-practices) / Code Delivery Processes
|
|
|
|
|
|
Continuous Delivery: Once new source code passed the automated tests it is sent to a staging environment for manual testing and QA review.
|
|
---
|
|
|
|
|
|
Continuous Deployment: after manual testing and QA reviews have been completed, new code arrives at the production servers daily for small changes.
|
|
|
|
|
|
# Code Delivery Processes
|
|
|
|
|
|
|
|
###### Overview
|
|
|
|
---
|
|
|
|
|
|
|
|
__Continuous Integration__
|
|
|
|
|
|
|
|
New source code is added submitted to development tier codebase. Once new source code is submitted, it only makes it onto the development tier after several different types of automated testing are passed. These test types include, but are not limited to: unit, functional, acceptance, and data integrity.
|
|
|
|
|
|
|
|
__Continuous Delivery__
|
|
|
|
|
|
|
|
Once new source code passed the automated tests it is sent to a staging environment for manual testing and QA review.
|
|
|
|
|
|
|
|
__Continuous Deployment__
|
|
|
|
|
|
|
|
After manual testing and QA reviews have been completed, new code arrives at the production servers daily for small changes.
|
|
|
|
|
|
Any security patches and bug fixes are rolled out immediately and clients notified as soon as they are rolled out.
|
|
Any security patches and bug fixes are rolled out immediately and clients notified as soon as they are rolled out.
|
|
|
|
|
... | | ... | |