TechValidate Research on CA Release Automation

CA Technologies Release Automation Case Study

Case Study for CA Release Automation: Large Enterprise Financial Services Company


This case study of a large enterprise financial services 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.


  • Reasons for automating application releases:
    • 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
    • Tracking releases for compliance and audit purposes

Use Case

  • Using version 5.0 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 accurately deploy service updates across multiple applications and environments
    • To deploy in a compliance-driven environment
    • To improve team collaboration and accountability for application deployments
    • To provide Continuous Delivery as an IT service
  • Tools and platforms integrated with CA Release Automation:
    • Jenkins
    • Salesforce
    • ServiceNow
    • Datical


  • 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
    • A consolidated reporting dashboard
    • Re-usability of workflows and components
    • 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 stage:
    • BEFORE using CA Release Automation: Manual
    • 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