Case Study: GM Financial Transforms App Deployments With CA Release Automation and Gold Deployment Standards
3 likes573 views
GM Financial has transitioned to release automation to address issues stemming from their rapid operational expansion, including knowledge gaps and deployment inconsistencies. The implementation of shared components has facilitated repeatable deployment processes, enhancing software stability and visibility in development cycles. The automation effort has improved team efficiency and resource allocation towards optimizing deployment practices.
Case Study: GM Financial Transforms App Deployments With CA Release Automation and Gold Deployment Standards
- 5. 5 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD GM Financial’s Need for Infrastructure Change Rapid expansion in national and IO operations led to noticeable issues in the environment § Knowledge gaps § Inconsistencies in application environments § Miscommunication between teams in the organization More comprehensive audit and compliance requirements Lengthy project timelines and missing deployment dates
- 9. 9 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Deployments by Month—Dramatic Increase from January 0 500 1000 1500 2000 2500 January February March April May June July August September DEPLOYMENTS BY MONTH
- 10. 10 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD GM Financial’s Automated SDLC Design Dev designs Business code request Build/Scan Test CA Service Virtualization Perfecto Deploy CA Release Automation Busines s Reques t Application Servers Developer submits request for code package to move to QA Customer gets Product Project is complete d Deploying DEV/QA/TRN/PR D Testing QA Ticket s send to QA Moving to release automatio n Code Checked into TFS
- 14. 14 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Shared Component Identify § Determine similar and repeatable actions in deployment § Fit actions into specific categories – Artifact type deployments: IIS, .NET, Tibco BusinessWorks (java application) – Release Integration tasks: DEVTest, ServiceNow, F5 § Outline basic functions required § Identify best actions for deployment § Identify the necessary variables for each deployment § Communicate deployment steps between teams that are part of the release process to get feedback
- 15. 15 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Shared Component Standardize § Setup artifact build integration to have a standard package before it is pushed into CA Release Automation with applications like Jenkins § Work with other teams to set best practices for deployments § Limit shared component versions between CA Release Automation applications to maintain consistency in releases § Use common names across shared components in CA Release Automation to easily identify action and flow sections – Folder names like ‘Logging’ include logging configurations – Parameter values like environment using similar names like ‘service_account’ for applications
- 16. 16 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Shared Component Integrate § Setup flows that will become processes for easy on boarding of applications § Test in a low impact environment when making changes and then expand to a trial group before pushing changes to all applications § Discuss shared parameter values between shared components that can be leveraged in applications § Use shared components to integrate deployment calls outside of code releases – Automated Test: DEVTest and Perfecto – Deployment Approvals: ServiceNow
- 17. 17 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Shared Component Update § Rotate team members updating shared components to get a fresh perspective § Tag processes before updating for easy rollback § Communicate challenges with shared component layout for brainstorming between team members § Request feedback from users to add new deployment functions and features § Work as a team to constantly improve deployment processes – Can we set a flow to perform error handling if a deployment action fails? – Can where can we get the best logs for a deployment having issues? – Can we go off key words in logs to automatically fix deployment issues?
- 18. 18 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Deployment Times by Environment 00:00.0 01:26.4 02:52.8 04:19.2 05:45.6 07:12.0 08:38.4 10:04.8 11:31.2 DEV QA PRD Deployment … AVERAGE TIMES FOR DEPLOYMENTS SUCCEEDED
- 20. 20 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Tips for a CA Release Automation User What NOT to do § Overuse looping in deployments with artifacts § Set environment and attribute parameters in deployments that are not necessary § Set up non-repeatable processes inside individual application design § Set up an enterprise instance without an enterprise database What to do § Set a central server to collect logs and send notification emails § Set browser to 90% zoom § Leverage token values for action values in flows § Use community site to ask questions and look for patch updates § Use CI applications for intended purpose
- 23. 23 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Recommended Sessions SESSION # TITLE DATE/TIME DO5T03P Leadership Panel: Continuous Delivery in the Financial Services Industry 11/16/2016 at 04:30 pm DO5T14S Analyst Keynote: Continuous Delivery: Making DevOps Awesome 11/17/2016 at 10:30 am DO5T19S GM Financial Builds a Sustainable, Holistic, Continuous Delivery Practice 11/17/2016 at 04:30 pm
- 24. 24 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Must See Demos Modernize App Delivery Integrated CD Theater 5 - DOV501P Deliver Test Data Faster Test Data Manager Theater 5 - DOV511P Deliver Better Apps Service Virtualization Theater 5 - DOV507P Orchestrate Your Release Release Automation Theater 5 - DOV513P
- 25. 25 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD DevOps – Continuous Delivery For more information on DevOps – Continuous Delivery, please visit: http://cainc.to/PiTFpu