XebiaLabs DevOps Platform Version 6.2 Released with Automated Risk Scoring
March 28, 2017

XebiaLabs announced release risk assessment capabilities in its XebiaLabs DevOps Platform version 6.2, providing DevOps teams with an automated risk score that predicts which releases have a high chance of failure.

Armed with this risk intelligence, teams can s

The platform automatically assesses multiple risk factors to determine an overall release risk score. Armed with this intelligence, teams can predict which releases have a high risk of failure or delay. This insight allows them to solve issues and avoid setbacks before they become significant problems that impact the business.

The release risk assessment includes the following capabilities:

- Release Risk Score - The new Release Risk Score lets teams immediately see the risk associated with each release in the pipeline for in-progress releases. It correlates multiple indicators to assess risk for each release, then provides a risk score to alert teams that extra attention is needed.

- Risk-aware Overview across all Releases - A new risk-aware Release Overview provides detailed visibility across all releases. This view can be organized by risk and shows crucial details like due dates, release duration, phases completed, and more. Release managers and IT teams can now more easily view everything they need in one location, with the release risk score front and center for each release. Users can also sort and filter releases to create personalized views of their release landscape.

“For a busy release manager, knowing which releases are at risk is critical, and some of our customers have hundreds of releases running simultaneously. Getting alerted to which ones require attention – and addressing these risks early – can make the difference between success and failure,” said Tim Buntel, VP of Products for XebiaLabs. “Our new Risk Assessment feature evaluates all running releases to inform users about which releases are at risk and which are doing just fine, so their releases can succeed 100% of the time.”

In addition to building risk awareness into the DevOps pipeline, 6.2 introduces new Blackout Period functionality. This feature gives teams more control over the timing of their releases so they no longer need to make manual efforts to avoid inconvenient release times, such as holidays or end-of-quarter blackout windows. 6.2 also includes improvements for monitoring task progress and enhancements to plugins for Docker, Microsoft Team Foundation Server, and Amazon Web Services.

The XebiaLabs DevOps Platform version 6.2 is available now.

The Latest

April 27, 2017

In a movement that has gained momentum as quickly as DevOps has, it's always good to stop from time to time and evaluate where we are, where we have come from, and where we are going. We asked four industry experts some questions about the progress of ALM and DevOps ...

April 26, 2017

It's easy to ignore downtime. But ignoring downtime is a surefire way to upset your customers and your colleagues. More and more, teams need to think about shipping stellar experiences. Proper incident response is a great place to start ...

April 24, 2017

The expectation of regular software updates – it's what developers are tasked with, and what users expect and demand. Increased functionality, better performance, and fewer bugs – often in a week or less. Automation of critical processes such as QA can help meet the gargantuan task of constant updates, but it can also send your software into a death spiral of user abandonment unless deployed correctly ...

April 20, 2017

One could argue that testing is the most important phase of an IT project. It's also time-consuming and expensive. It's essential to strike a balance between an IT testing program that ensures a quality product and the cost-to-value ratio of your project. But when you're dealing with replatforming projects, how much testing is enough testing? ...

April 18, 2017

Whether through formal methods such as classroom or virtual training, job shadowing, and mentoring; or through informal methods such as team discussions or presentations, teaching needs to be a frequent element of team integration. It is a given that IT and business teams have difficulty understanding each other without a common taxonomy. Even teams within IT often fail to understand each other ...

April 17, 2017

Although DBAs fortunately have the rare ability to bridge the gap between development and operations, they have been detrimentally overlooked in many companies that deploy DevOps practices. A DBA's ability to interrogate code and construct a resilient, well–performing database environment uniquely defines the capabilities needed for DevOps – leaving me perplexed about why DBAs were not one of the first operations team members asked to join the DevOps movement ...

April 12, 2017

DEVOPSdigest asked experts across the industry — including analysts, consultants and vendors — for their opinions on the best way for a development or DevOps team to become more Agile. Part 5, the final installment in this series, provides tips on empowering people ...

April 10, 2017

DEVOPSdigest asked experts across the industry for their opinions on the best way for a development or DevOps team to become more Agile. Part 4 covers DevOps technologies ...

April 07, 2017

DEVOPSdigest asked experts across the industry for their opinions on the best way for a development or DevOps team to become more Agile. Part 3 provides some tips for getting started and gaining feedback ...

April 05, 2017

DEVOPSdigest asked experts across the industry for their opinions on the best way for a development or DevOps team to become more Agile. Part 2 covers processes including automation, continuous delivery and testing ..

Share this