Menu

TechValidate Research on CA Release Automation

14 Case Studies


CA Technologies Release Automation Case Study

Case Study for CA Release Automation: Global 500 Banking Company

Introduction

This case study of a Global 500 banking company is based on a June 2016 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.

“With CA Release Automation, it’s easy to do releases. Also, it is a quickly understandable tool and user friendly.”

Challenges

  • Reasons for automating application releases:
    • Increase the volume of release deployments
    • Reduce release failures and improve deployment quality
    • Manage the complexity of applications, tools and environments
    • Get better control over the release process and pipeline
    • Track releases for compliance and audit purposes
  • Chose CA Release Automation over:
    • VMware

Use Case

  • Using CA Release Automation version 5.5
  • 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 deploy in a compliance-driven environment
    • To improve team collaboration and accountability for application deployments
    • To provide Continuous Delivery as an IT service

Results

  • Most valuable features of CA Release Automation:
    • Release execution flexibility to pause, restart, or roll back a deployment
    • Visual UI for building workflows
    • A consolidated reporting dashboard
    • Artifact management, modeling, and tracking
    • 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
  • Rating of CA Release Automation’s features when compared to the competition:
    • Depth/breadth of integrations: Highly superior
    • Deployment workflow design: Significantly superior
    • Release execution/reliability: Significantly superior
    • Visibility to release activity: Significantly superior
    • Scalability: Significantly superior
  • Value achieved by implementing CA Release Automation:
    • The ability to reliably release applications on demand
    • Getting customer feedback faster
    • Increased volume of releases
    • Improved visibility, consistency, and reliability of release processes across the pipeline
    • The ability to easily integrate with existing environment and tools
    • Reduced or eliminated downtime
  • Improved with CA Release Automation:
    • Time to market: By more than 50-75%
    • Ability to handle more releases: By more than 75%
    • Speed of release cycles: By more than 75%
    • Release quality: By 50-75%
    • Tracking for compliance and audit: 50-75%

CA Technologies Release Automation Case Study

Case Study for CA Release Automation: HMS (Health Management Systems)

Introduction

This case study of HMS (Health Management Systems) is based on a July 2016 survey of CA Technologies Release Automation customers by TechValidate, a 3rd-party research service.

“We adopted CA Release Automation over other solutions because it was able to deploy Informatica code. This deployment cut the deployment time from hours to minutes. "

Challenges

  • Reasons for automating application releases:
    • Increase the volume of release deployments
    • Reduce release failures and improve deployment quality
  • Chose CA Release Automation over:
    • Microsoft Release Management

Use Case

  • Using CA Release Automation version 5.5
  • 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 provide Continuous Delivery as an IT service

Results

  • Most valuable features of CA Release Automation:
    • Visual UI for building workflows
    • Artifact management, modeling, and tracking
    • Re-usability of workflows and components
  • Rating of CA Release Automation’s features when compared to the competition:
    • Depth/breadth of integrations: Highly superior
    • Deployment workflow design: Highly superior
    • Release execution/reliability: Significantly superior
    • Visibility to release activity: Highly superior
    • Scalability: Highly superior
  • Value achieved by implementing CA Release Automation:
    • Getting customer feedback faster
    • Significantly sped up release cycles
    • Reduced or eliminated downtime
  • Improvements to Application Delivery with CA Release Automation:
    • Time to market: More than 75%
    • Ability to handle more releases: More than 75%
    • Speed of release cycles: More than 75%
    • Release quality: More than 75%
    • Tracking for compliance and audit: More than 75%

CA Technologies Release Automation Case Study

Global 500 Bank Significantly Improves Its App Delivery With CA Release Automation

Introduction

This case study of a Global 500 Banking Company is based on a June 2016 survey of CA Technologies Release Automation customers by TechValidate, a 3rd-party research service.

“Yes, I would recommend CA Release Automation. It is more robust and user-friendly than IBM UrbanCode.”

Challenges

  • Reasons for automating application releases:
    • Increase the volume of release deployments
    • Manage the complexity of applications, tools, and environments
    • Get better control over the release process and pipeline
  • Chose CA Release Automation over:
    • IBM UrbanCode

Use Case

  • Using CA Release Automation version 6.0
  • Currently using CA Release Automation to:
    • Orchestrate the release pipeline – deploying an application from stage to stage
    • Accurately deploy service updates across multiple applications and environments
    • Improve team collaboration and accountability for application deployments
    • Provide Continuous Delivery as an IT service

Results

  • Most valuable features of CA Release Automation:
    • Depth and breadth of integrations with 3rd party and in-house technologies
    • Visual UI for building workflows
    • Artifact management, modeling, and tracking
    • 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
  • Rating of CA Release Automation’s features when compared to the competition:
    • Depth/breadth of integrations: Highly superior
    • Deployment workflow design: Highly superior
    • Release execution/reliability: Highly superior
    • Visibility to release activity: Highly superior
    • Scalability: Highly superior
  • Value achieved by implementing CA Release Automation:
    • 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
    • Reduced or eliminated downtime
  • Improvement to Application Delivery with CA Release Automation:
    • Time to market: By 50-75%
    • Ability to handle more releases: By 50-75%
    • Speed of release cycles: By 50-75%
    • Release quality: By 50-75%
    • Tracking for compliance and audit: By 50-75%

CA Technologies Release Automation Case Study

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

Introduction

This case study of a medium enterprise financial services company is based on a June 2016 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.

Challenges

  • Reasons for automating application releases:
    • Get to market quicker
    • Increase the volume of release deployments
    • Reduce release failures and improve deployment quality
    • Manage the complexity of applications, tools and environments
    • Get better control over the release process and pipeline
    • Capture and re-use deployment best practices
    • Track releases for compliance and audit purposes
  • Chose CA Release Automation over:
    • Serena
    • Xebialabs

Use Case

  • Usung CA Release Automation version 6.1.
  • 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 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

Results

  • Most valuable features of CA Release Automation:
    • Release execution flexibility to pause, restart, or roll back a deployment
    • A consolidated reporting dashboard
    • Re-usability of workflows and components
    • Ability to deploy a large number of applications across multiple environments
  • Rating of CA Release Automation’s features when compared to the competition:
    • Depth/breadth of integrations: Highly superior
    • Deployment workflow design: Superior
    • Release execution/reliability: Superior
    • Visibility to release activity: Highly superior
    • Scalability: Highly superior
  • 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
  • Improvements to company’s capabilities with CA Release Automation:
    • Time to market: By 50-75%
    • Ability to handle more releases: By 50-75%
    • Speed of release cycles: By 50-75%
    • Release quality: By 50-75%
    • Tracking for compliance and audit: By 50-75%

CA Technologies Release Automation Case Study

Case Study for CA Release Automation: S&P 500 Financial Services Company

Introduction

This case study of a S&P 500 financial services company is based on a June 2016 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.

Challenges

  • Reasons for automating application releases:
    • Get to market quicker
    • Increase the volume of release deployments
    • Reduce release failures and improve deployment quality
    • Manage the complexity of applications, tools and environments
    • Get better control over the release process and pipeline
    • Capture and re-use deployment best practices
      *Chose CA Release Automation over:
    • Automic
    • Electric Cloud
    • Hewlett Packard Enterprise (HPE)
    • IBM UrbanCode
    • Xebialabs

Use Case

  • Using CA Release Automation version 5.5.
  • 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 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

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
    • Artifact management, modeling, and tracking
    • Re-usability of workflows and components
    • Ability to deploy a large number of applications across multiple environments
  • Rating of CA Release Automation’s features when compared to the competition:
    • Depth/breadth of integrations: Superior
    • Deployment workflow design: Highly superior
    • Release execution/reliability: Highly superior
    • Visibility to release activity: Superior
    • Scalability: Superior
  • Value achieved by implementing CA Release Automation:
    • The ability to reliably release applications on demand
    • Getting customer feedback faster
    • 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
  • Improvements to Application Delivery with CA Release Automation:
    • Time to market: By 35-50%
    • Ability to handle more releases: By 50-75%
    • Speed of release cycles: By 35-50%
    • Release quality: By 35-50%
    • Tracking for compliance and audit: By 15-35%

CA Technologies Release Automation Case Study

Case Study for CA Release Automation: Medium Enterprise Insurance Company

Introduction

This case study of a medium 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 to deploy all applications with release automation.”

Challenges

  • Reasons for automating application releases:
    • Getting to market quicker
    • Increasing the volume of release deployments
    • Reducing release failures and improving deployment quality

Use Case

  • Using version 5.5 of CA Release Automation.
  • Cites that CA Release Automation has been implemented for 0 – 12 months.
  • Currently using CA Release Automation to:
    • To extend Agile development methodologies into the release pipeline
    • To accurately deploy service updates across multiple applications and environments
    • To deploy in a compliance-driven environment
  • Tools and platforms integrated with CA Release Automation:
    • Jenkins
    • IBM Rational ClearCase
    • Nexus

Results

  • Most valuable features of CA Release Automation:
    • Visual UI for building workflows
    • Re-usability of workflows and components
  • Value achieved by implementing CA Release Automation:
    • The ability to reliably release applications on demand
    • Improved collaboration and accountability between the Development and Operations teams
  • Company’s progress on journey to Continuous Delivery:
    • BEFORE using CA Release Automation: Scripting
    • AFTER using CA Release Automation: Tool Automation

CA Technologies Release Automation Case Study

Case Study for CA Release Automation: Fortune 500 Financial Services Company

Introduction

This case study of a Fortune 500 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.

“We have been getting very positive feedback for CA Release Automation from our Development and Release Management teams. CA Release Automation changed the way in which the builds are getting deployed to production. I would recommend CA Release Automation. It is consistent, repeatable, scalable and predictable, and it supports our Continuous Integration framework.”

Challenges

  • Reasons for automating application releases:
    • Getting to market quicker
    • Increasing the volume of release deployments
    • Reducing release failures and improving deployment quality
    • 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 extend Agile development methodologies into the release pipeline
    • To accurately deploy service updates across multiple applications and environments
    • To deploy in a compliance-driven environment
    • To provide Continuous Delivery as an IT service
  • Tools and platforms integrated with CA Release Automation:
    • Jenkins
    • SERENA Release Control
    • IBM Rational Build Forge
    • Home-grown deployment orchestrator

Results

  • Most valuable features of CA Release Automation:
    • Depth and breadth of integrations with 3rd party and in-house technologies
    • Visual UI for building workflows
    • 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
    • Getting customer feedback faster
    • Significantly sped up release cycles
    • Increased volume of releases
    • Improved visibility, consistency, and reliability of release processes across the pipeline
    • 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: Scripting
    • AFTER using CA Release Automation: Continuous Delivery

CA Technologies Release Automation Case Study

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

Introduction

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.

Challenges

  • Reasons for automating application releases:
    • Increasing the volume of release deployments
    • Reducing release failures and improving deployment quality
    • Getting better control over the release process and pipeline
    • 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 provide Continuous Delivery as an IT service
  • Tools and platforms integrated with CA Release Automation:
    • Jenkins
    • JFrog Artifactory

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
    • A consolidated reporting dashboard
    • Artifact management, modeling, and tracking
  • Value achieved by implementing CA Release Automation:
    • The ability to reliably release applications on demand
    • Significantly sped up release cycles
    • Increased volume of releases
    • Reduced or eliminated downtime
  • Company’s progress on journey to Continuous Delivery stage:
    • BEFORE using CA Release Automation: Scripting
    • AFTER using CA Release Automation: Continuous Delivery

CA Technologies Release Automation Case Study

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

Introduction

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.

Challenges

  • 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

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
    • 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

CA Technologies Release Automation Case Study

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

Introduction

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.

“Our experience with CA Release Automation has been great. We are able to deploy several hundred deployments with almost zero downtime. Also, we are able to provision applications within no time, at any time. This is awesome and our developers were able to focus on quality deliverables rather than spending time on deployment bridges. I would absolutely recommend CA Release Automation, as it has robust integrations to various development tools and provides great value in Continuous Delivery.”

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
    • Tracking releases for compliance and audit purposes
    • Ability to deploy applications with zero downtime in QA and Prod

Use Case

  • Using version 5.5 of CA Release Automation.
  • Has been implemented for 1 – 2 years.
  • Currently using CA Release Automation to:
    • To extend Agile development methodologies into the release pipeline
    • 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 achieve advanced deployments like Canary, Dark, and Blue-Green
    • To provide Continuous Delivery as an IT service
  • Tools and platforms integrated with CA Release Automation:
    • JFrog Artifactory
    • ServiceNow
    • CA Service Virtualization
    • Bamboo, HP Quality Center

Results

  • Most valuable features of CA Release Automation:
    • Depth and breadth of integrations with 3rd party and in-house technologies
    • A consolidated reporting dashboard
    • Artifact management, modeling, and tracking
    • 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
    • Getting customer feedback faster
    • 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: Manual
    • AFTER using CA Release Automation: Continuous Delivery

CA Technologies Release Automation Case Study

Case Study for CA Release Automation: Medium Enterprise Banking Company

Introduction

This case study of a medium enterprise banking 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.

Challenges

  • Reason for automating application releases:
    • Reducing release failures and improving deployment quality

Use Case

  • Using version 5.5 of CA Release Automation.
  • Has been implemented for 0 – 12 months.
  • Currently using CA Release Automation to:
    • To accurately deploy service updates across multiple applications and environments
  • Tool and platform integrated with CA Release Automation:
    • Jenkins

Results

  • Most valuable features of CA Release Automation:
    • Artifact management, modeling, and tracking
    • Re-usability of workflows and components
    • Ability to deploy a large number of applications across multiple environments
  • Value achieved by implementing CA Release Automation:
    • Significantly sped up release cycles
    • The ability to efficiently manage deployment environments and dependencies
    • Improved collaboration and accountability between the Development and Operations teams
  • Company’s progress on journey to Continuous Delivery:
    • BEFORE using CA Release Automation: Manual
    • AFTER using CA Release Automation: Tool Automation

CA Technologies Release Automation Case Study

Case Study of CA Release Automation: Large Enterprise Banking Company

Introduction

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

Challenges

  • Reasons for automating application releases:
    • Getting to market quicker
    • Increasing the volume of release deployments
    • Reducing release failures and improving deployment quality
    • 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 1 – 2 years
  • Currently using CA Release Automation to:
    • To accurately deploy service updates across multiple applications and environments
    • To deploy in a compliance-driven environment
    • To provide Continuous Delivery as an IT service
  • Tools and platforms integrated with CA Release Automation:
    • Jenkins
    • SharePoint

Results

  • Most valuable features of CA Release Automation:
    • Release execution flexibility to pause, restart, or roll back a deployment
    • Re-usability of workflows and components
  • Value achieved by implementing CA Release Automation:
    • The ability to reliably release applications on demand
    • Getting customer feedback faster
    • Improved visibility, consistency, and reliability of release processes across the pipeline
  • Company’s progress on journey to Continuous Delivery:
    • BEFORE using CA Release Automation: Scripting
    • AFTER using CA Release Automation: Tool Automation

CA Technologies Release Automation Case Study

Case Study for CA Release Automation: S&P 500 Banking Company

Introduction

This case study of a S&P 500 banking 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.

Challenges

Reasons for automating application releases:

  • Reasons for automating application releases:
    • Reducing release failures and improving deployment quality
    • Getting better control over the release process and pipeline
    • Tracking releases for compliance and audit purposes

Use Case

  • Using version 5.5 of CA Release Automation.
  • Has been implemented for 1 – 2 years.
  • Currently using CA Release Automation to:
    • To orchestrate the release pipeline – deploying an application from stage to stage
  • Tools and platforms integrated with CA Release Automation:
    • Jenkins

Results

  • Most valuable features of CA Release Automation:
    • Depth and breadth of integrations with 3rd party and in-house technologies
    • 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
    • Improved visibility, consistency, and reliability of release processes across the pipeline
    • Reduced or eliminated downtime
  • Company’s progress on journey to Continuous Delivery:
    • BEFORE implementation: Manual
    • AFTER implementation: Tool 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