---
title: "Continuous Integration erklärt - dev.house GmbH"
description: "Continuous Integration (CI) ist der Prozess der kontinuierlichen Integration des Codes eines Teams in den Hauptzweig Ihres Code-Repositorys. Der Schwerpunkt liegt darauf, dies in kleinen Schritten (sogenannten Inkrementen), aber kontinuierlich zu tun. Ein wesentlicher Bestandteil dieses Ansatzes ist die Überprüfung dieser Inkremente auf ihre Qualität. Dabei spielen automatisierte Builds und Tests, die Testabdeckung und das"
author: "Maximilian Hammerschmidt"
date: "2022-09-16T10:11:12+00:00"
language: "en-GB"
canonical_url: "https://zhxupqvgy2u2emm.onstatic.studio/en/2022/09/16/continuous-integration/"
source_url: "https://zhxupqvgy2u2emm.onstatic.studio/en/2022/09/16/continuous-integration/"
content_type: "text/markdown"
---

# Continuous Integration explained







								-
						[





										September 16, 2022
									](https://zhxupqvgy2u2emm.onstatic.studio/en/2022/09/16/)








															![dev.house GmbH Continuous Integration](https://zhxupqvgy2u2emm.onstatic.studio/wp-content/uploads/2022/09/continuous-integration-dev.house-process-how-does-it-work-software-development-team-steps-new-1024x1024.png)



									Continuous Integration (CI) is the process of continuously integrating the team's code into the main branch of your code repository. The focus is on doing this in small increments, but continuously. An integral part of this approach is to check these increments for quality. In doing so, automated builds and tests, test coverage and scanning the code for security vulnerabilities play a major role. The development process becomes more transparent and helps to avoid errors in the future deployment.

Why is it important for you?

- detect problems in development earlier

- find and remove bugs earlier

- save the developers time during tests and quality gates

- deliver new features and get user feedback more rapidly

How does it work?

- automate your builds

- make your builds self-testing

- create quality gates for the code

- test on an isolated copy of production environment

- make the build process transparent for everyone in the team
– Durch Automatisierung Ihrer Builds
– Machen Sie Ihre Builds selbsttestend
– Erstellen von Quality Gates für den Code
– Testen auf einer isolierten Kopie der Produktivumgebung
– Transparenz des Build-Prozesses für alle Teammitglieder

Which tools do we use?
– Azure DevOps (Azure Pipelines)
– Gitlab CI
– Github Actions
– Jenkins