Software Development: Difference between revisions
Jump to navigation
Jump to search
| Line 14: | Line 14: | ||
In the DevOps culture, CI is mandatory, and it performed automatically by a tool that runs automation scripts to eliminate all human intervention during the CI process. | In the DevOps culture, CI is mandatory, and it performed automatically by a tool that runs automation scripts to eliminate all human intervention during the CI process. | ||
The CI process requires a source code repository and a continuous integration server, that pulls code from the source repository and runs the build. | |||
==Continous Deployment (CD)== | ==Continous Deployment (CD)== | ||
Revision as of 19:06, 30 April 2017
DevOps
A collaborative process enabled by automation where application development, QA and Operations teams jointly accelerate delivery of new business application and services. DevOps emphasizes collaboration and cooperation.
CICD
Continous Integration (CI)
Continous Integration is a software development practice that involves the following:
- Verifies build integrity by checking if the source code can be pulled from repository and built for deployment. The build process may include compilation, packaging and configuration.
- Runs and validates the unit tests: executes all unit tests created by developers and validates the test results. This step insures that the source code was not broken as a side effect of the commit.
- Runs and validates the integration tests.
- Identifies problems and alerts the teams.
In the DevOps culture, CI is mandatory, and it performed automatically by a tool that runs automation scripts to eliminate all human intervention during the CI process.
The CI process requires a source code repository and a continuous integration server, that pulls code from the source repository and runs the build.