|
Convention over Configuration: Replace Scripting with New Build Names 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.
|
|
|
Where Did Configuration Management Go? 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.
|
|
|
What You Need to Know to Make Deployment Automation Work for Your Business 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.
|
|
|
Automation of Branching, Merging, and Notifications in Parallel Development 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.
|
|
|
Why Continuous Delivery Is Nothing without Real-Time Test Analysis 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.
|
|
|
Automation Opportunities in Agile Release Management 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.
|
|
|
When Should You Automate Your Testing? Although it sounds counterintuitive, manual testing still plays a large role in automation. In truth, manual testing will never go away. While automation is all the rage, there are instances when manual testing is preferable over automation. Knowing when to employ one tactic over the other can be helpful in reaching your goals.
|
|
|
What Is Release Management, and Why Is It Needed? This article talks about what release management is, then tells you how to implement the concepts in an organization by explaining what skills are needed, how release managers work within a team, and how the process is related to continuous integration.
|
|
|
Achieving Enterprise Release Harmony An enterprise release consists of individual releases, some independent and some dependent. If we think of an enterprise release as a song, then the individual releases can be thought of as the musical notes that make up the song. This article discusses problems associated with an enterprise release and ways in which these problems can be overcome, resulting in release harmony.
|
|
|
Blending Test Automation Approaches One hundred percent test automation and 100 percent exploratory testing are absolutes. They make for great arguments, but, for those of us stuck in the great middle ground, those positions aren't very helpful. Matthew Heusser describes a blended approach to software testing, explains how some of his clients have used it over the long term, and provides tips for evaluating and adapting your approach.
|
|