TechValidate Research on CA Release Automation


Case Study for CA Release Automation: Large Enterprise Insurance Company

Introduction

This case study of a large enterprise insurance company is based on a September 2015 survey of CA Technologies Release Automation customers by TechValidate, a 3rd-party research service. The profiled company asked to have their name blinded to protect their confidentiality.

“The next challenge we plan to address with CA Release Automation is new generation platforms, mainly cloud and SaaS based deployments.”

Challenges

  • Reasons for automating application releases:
    • Getting to market quicker
    • Increasing the volume of release deployments
    • Reducing release failures and improving deployment quality
    • Managing the complexity of applications, tools, and environments
    • Getting better control over the release process and pipeline
    • Capturing and re-using deployment best practices

Use Case

  • Using version 4.7 of CA Release Automation.
  • Has been implemented for 2 – 4 years.
  • Currently using CA Release Automation to:
    • To orchestrate the release pipeline – deploying an application from stage to stage
    • To extend Agile development methodologies into the release pipeline
    • To improve team collaboration and accountability for application deployments
  • Tools and platforms integrated with CA Release Automation:
    • Microsoft Azure
    • TFS, BizTalk

Results

  • Most valuable features of CA Release Automation:
    • Depth and breadth of integrations with 3rd party and in-house technologies
    • Release execution flexibility to pause, restart, or roll back a deployment
    • Visual UI for building workflows
    • Support for complex processes, looping, and cross-server processing
    • Ability to deploy a large number of applications across multiple environments
  • Value achieved by implementing CA Release Automation:
    • The ability to reliably release applications on demand
    • Significantly sped up release cycles
    • Increased volume of releases
    • Improved visibility, consistency, and reliability of release processes across the pipeline
    • The ability to efficiently manage deployment environments and dependencies
    • The ability to easily integrate with existing environment and tools
    • Reduced or eliminated downtime
    • Improved collaboration and accountability between the Development and Operations teams
  • Company’s progress on journey to Continuous Delivery:
    • BEFORE using CA Release Automation: Tool Automation
    • AFTER using CA Release Automation: Continuous Delivery




About This Data

This data was sourced directly from verified users of CA Release Automation by TechValidate.

TechValidate verifies the identity and organizational affiliation of all participants that contribute to published research data. When research participants so desire, we also guarantee their anonymity so that they may share information honestly and freely.


More Research on CA Release Automation