release

Bernie Zelitch writes that his company’s build system scales well because early on, they scrutinized their build naming convention, saw its implications to the build ecosystem, and made radical changes. Their new naming convention takes some getting used to, but once it was fully adopted, it improved economy, flexibility, and functionality.

When the number of employees, products, and releases you’re managing grows rapidly, that transformation introduces several challenges—and opportunities—in almost every aspect of configuration management. This article presents the major issues a company may face and the improvements you can make to processes and tools as a result.

Developers are distracted from coding by the need to interact with version control systems. Automation of branching, merging, and notifications allows developers to focus on coding. However, integration between the VCS and issue-tracking system, and preferably a continuous integration tool, is necessary to accomplish this goal.

In modern software development, changes to the code base of a project occur quickly as a result of high levels of end-user feedback and shifting needs. Agile has become an increasingly important software development lifecycle management methodology, and using automation to manage a code repository allows continuous integration to take center stage without imposing costs due to human error.