The latest News and Information on Continuous Integration and Development, and related technologies.
Configuring applications, services, and environments by modifying plain text files is a standard part of modern software development. Configuration as Code (CaC) takes this one step further by systematically generating, storing, and managing configuration files. CaC allows development teams to automate config management for their applications and environments while ensuring consistency and traceability throughout the development life cycle.
Ciara details how and when to generate an SBoM with the help of open-source tooling. Learn how to host SBoMs, as well as other SBoM considerations.
The first continuous integration (CI) tools were all self-hosted, meaning they ran on a developer’s local computer or server. Although this setup was viewed favorably by dev teams at the time, it has limited flexibility, and developers had to spend time maintaining the infrastructure.
This post is the third in a series of deeper dive articles discussing DORA metrics. In previous articles, we looked at: The third metric we’ll examine, Change Failure Rate, is a lagging indicator that helps teams and organizations understand the quality of software that has been shipped, providing guidance on what the team can do to improve in the future.
For more information, read this tutorial: https://circleci.com/blog/intro-to-software-testing-life-cycle/
