Release Management
Articles
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. |
||
A Gateway to Quality Builds and Keeping the Release Branch Green Eitan Schichmanter’s team evolved its development process from a focus on build management to a more robust DevOps transformation, and they designed a custom gated check-in system to help. He shares how they tackled challenges and created an internal solution to address an important technical requirement. |
||
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. |
||
Defining What’s Really Important in a DevOps Maturity Model There is a lot more to DevOps than just single push-button deploys. While a DevOps maturity model can help measure where you are now and indicate where you need to get to as part of the DevOps transformation, it can be more useful to focus on the capabilities you need to measure: timely deployment and secure, reliable systems. |
||
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. |
||
Create Your Own Assembly Line-Style Migrations for Database Changes In an increasingly data-driven world with ever-changing systems, having an automated process for database migrations is a valuable practice. Instead of people having to keep track of each file, table, procedure, or object being modified, a tool can make database deployments more automatic and less excruciating, saving time and reducing errors. |
||
Pushing Back against Database Drift 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. |
||
Manage the Business Risks of Application Development with Continuous Testing 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. |
||
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. |