Continuous Integration (CI) in software development
As part of Continuous Integration in software development, components are being assembled during continuously executed build processes. Usually a build is started after each push to the central version control server.
The aim of Continuous Integration is to increase the quality in software development through fast and early detection of potential errors.
In addition to the build of the software, automated tests and quality analyses can be executed as part of a CI-pipeline.
Differentiation between Continuous Deployment and Continuous Delivery
Continuous Integration with the Cloudogu EcoSystem (CES)
The Cloudogu EcoSystem has everything you need to set up a Continuous Integration pipeline:
- Version control server (SCM-Manager)
- Build server (Jenkins)
- Code analysis tool (SonarQube)
- Artefact repository server (Nexus Repository)
An example of a CI-pipeline is described in this blog post: Example setup of continuous integration platform.