CICDkäytännöt

CICDkäytännöt refers to the set of practices and principles that enable continuous integration and continuous delivery or deployment within software development. These practices aim to automate and streamline the software delivery pipeline, from code commit to production release.

Continuous Integration (CI) involves developers frequently merging their code changes into a central repository, after which automated builds and tests are run. This helps to detect and address integration issues early in the development cycle. The goal is to prevent the "integration hell" that can occur when large code changes are merged infrequently.

Continuous Delivery (CD) extends CI by automatically preparing code changes for release to production. This means that after the CI stage, the code is automatically deployed to a staging environment where further testing, such as user acceptance testing, can be performed. The decision to deploy to production is often manual, allowing for a final check.

Continuous Deployment (also CD) takes this a step further by automatically deploying every change that passes all stages of the pipeline directly to production. This requires a high level of confidence in the automated testing and a robust rollback strategy.

Key elements of CICDkäytännöt include version control systems (like Git), automated build tools (like Maven or Gradle), automated testing frameworks (like JUnit or Selenium), and deployment automation tools (like Jenkins, GitLab CI, or CircleCI). The underlying philosophy is to foster collaboration, reduce manual errors, and deliver value to users more frequently and reliably. Implementing these practices requires a cultural shift towards automation and a commitment to quality throughout the development lifecycle.