Balancing time-to-market pressures with regulatory needs and business continuity demands is a challenge for highly regulated large enterprises. Automating processes and mastering proven practices of release management makes developing and releasing software predictable, reliable, and repeatable.
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.
Amid all the excitement of DevOps, continuous delivery, and the magic of single-push-button deploys, some folks have forgotten the prerequisites. You cannot implement continuous anything without effective configuration management. This article will help you reassess where you are and ensure that you have the basic building blocks in place to ensure success.
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.
Deployment automation is becoming more of a requirement for software development teams that are looking to remain competitive. While there are many benefits, there are also a number of areas to consider before implementing a deployment automation solution as part of your software development and release process.
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.
Pushing frequent releases of high-quality software to customers is beneficial for everyone. But setting up a continuous delivery pipeline is about more than speed. How do you ensure that things don’t start breaking all over the place? Viktor Clerc shares some real-world methods of accurately measuring quality and building it into the pipeline.
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.
You might know the phenomenon of database drift as version creep—or simply that sinking feeling when the production system isn’t in the state you expect it to be. If you’re having drift problems, the odds are that there’s a technical, process, or change management issue somewhere farther up the chain.
Continuous testing provides a real-time, objective assessment of the business risks associated with an application under development. Ultimately, continuous testing can provide a quantitative assessment of risk and produce actionable tasks that will help mitigate these risks before progressing to the next stage of the software development lifecycle.