1.
ca DevCenter
Case Study: How CA’s IT Automated Salesforce
Deployments with CA Release Automation
Sathish Chandrasekaran
CA Technologies
Sr. Director, Information Technology
DCT07S #CAWorld

2.
Abstract
SaaS-based applications like Salesforce.com are increasingly relevant to
companies to compete and grow their business. However, the
opportunity of faster time to value and availability offered by Cloud and
SaaS comes with an urgent need to automate the application
development and release processes. Learn how CA’s internal IT team
used CA Release automation to reduce software release times by
simplifying and standardizing the release process and minimizing errors.
 An 80% reduction in release errors during deployment
 Software release times reduced by 4-5x times
Sathish
Chandrasekaran
Sr. Director, IT
CA Technologies
2 © 2014 CA. ALL RIGHTS RESERVED.

3.
Agenda
SALESFORCE LANDSCAPE & CHALLENGES @ CA
TOOLS FOR SALESFORCE RELEASE AUTOMATION
SOLUTION OVERVIEW
SFDC ACTIONS OVERVIEW
RELEASE MODELS FOR SALESFORCE DEPLOYMENT
LESSONS LEARNED AND OBSERVATIONS
1
2
3
4
5
6
3 © 2014 CA. ALL RIGHTS RESERVED.

4.
CA’s IT – Salesforce Footprint
CA Salesforce
 75 Development
 5 Configuration
 5 Full Sandboxes
 1 Production
Nimsoft Salesforce
 15 Sandboxes
 5 Configuration
 1 Production
Nolio Salesforce
 15 Sandboxes
 5 Configuration
 1 Production
4 © 2014 CA. ALL RIGHTS RESERVED.
Layer 7 Salesforce
 15 Sandboxes
 5 Configuration
 1 Production

5.
The Challenge of Salesforce Application Deployments
Production
Deploy
Change Set
5 © 2014 CA. ALL RIGHTS RESERVED.
 Lack of standardized release process
 Manual tracking of changes
 Manual execution of deployment steps
 Lack of automated tests and validation
 Frequent Release errors
 Manual environments sync up and
management
20% of development time spent on deployment activities
Developer 1
Developer 2
Developer 3
Code/Configu
ration
Code/Configu
ration
Code/Configu
ration
Development
Sandbox
Development
Sandbox
Deploy
Change Set
Deploy
Change Set
QA
Deploy
Change Set
Other Inflight
Projects
Deploy
Change Set
Production
Support

6.
Release Automation Tool chain
CONTINUOUS APPLICATION DELIVERY
Configuration Management
(Developer’s workspace including
Code/Configuration Repository)
Agile Testing
(Test Automation Tools)
Eclipse API
6 © 2014 CA. ALL RIGHTS RESERVED.
Deployment Pipeline
(Tools used for Automation of pipeline)
CA Release
Automation
ANT Migration
Metadata
Toolkit CLI Tools
Force.com IDE
CA Release
Automation
SFDC Actions
Code and
Configurations
CA Application Test
Metadata API

7.
Solution overview with Subversion ( v1 )
Developer 1
Code
Commit
Developer
Branch SCM
Code
Commit
Developer
Branch SCM
Code
Commit
Developer
Branch SCM
CI Server
CI Server
Integration Lab
Run SFDC Unit Test scripts
7 © 2014 CA. ALL RIGHTS RESERVED.
QA
Environment
UAT/Staging
Production
TRUE AGILE
DEVELOPMENT
CA Release Automation
Auto Self-Service/
Approval
CO/
Approval
Production
Support
Other Inflight QA
Environment(s)
Developer 1
Developer 1
CONTINUOUS
DELIVERY
CA Release Automation
CONTINUOUS
VALIDATION

8.
Lessons Learned and Observations
CHANGE SET ( SFDC ) CA RELEASE AUTOMATION
WITH SUBVERSION
8 © 2014 CA. ALL RIGHTS RESERVED.
CA RELEASE AUTOMATION
WITH SFDC ACTIONS
 Developers and Business
analysts required additional
build time
 Business Analysts required
training and did not welcome
 Early conflict resolution
 Reduction in release errors
 Reduction in time to deploy
 Manual tracking of changes
and preparation of
documentation
 Manual coordination and
creation of change set
 Manual execution of
deployment steps
 Frequent release errors

9.
How are the newly released SFDC actions used?
Developer(s)/ BSA
work on making
the Build changes
CA RELEASE AUTOMATION
DISCOVER
CHANGES
RETRIEVE,
DEPLOY,
VALIDATE
RETRIEVE,
DEPLOY,
VALIDATE
Development
Integration
QA
Production
TEMPLATES
PROCESSES
Developer(s)/
BSA
Actions Description
Discover metadata Discovers the changes the developers and BSAs have done
Retrieve metadata Retrieves the metadata components from the designated Salesforce organization
Deploy metadata Deploys the metadata components to the designated Salesforce organization
Validate metadata Validate Metadata components and run test classes
9 © 2014 CA. ALL RIGHTS RESERVED.
RETRIEVE,
DEPLOY,
VALIDATE
FLOWS
ACTIONS

10.
Solution Overview with RA / SFDC Actions ( v2 )
Developer 1 Commit
Changes
Code
Commit
Development
Sandbox
Auto
Discover
Development
Sandbox
CA Release Automation
CI Server
CI Server
Run Tests in CA Application Test | Run SFDC Unit Test scripts
Integration Lab
(n)
10 © 2014 CA. ALL RIGHTS RESERVED.
QA
Environment
UAT/Staging
Production
TRUE AGILE
DEVELOPMENT
Auto Self-Service/
Approval
CO/
Approval
Production
Support
Other Inflight QA
Environment(s)
Developer 1
Developer 1
CONTINUOUS
DELIVERY
CA Release Automation
CONTINUOUS
VALIDATION
Auto
Discover

11.
Lessons Learned and Observations
 Developers and Business
analysts required additional
build time
 Business Analysts required
training and did not welcome
 Early conflict resolution
 Reduction in release errors
 Reduction in time to deploy
 Manual tracking of changes
and preparation of
documentation
 Manual coordination and
creation of change set
 Manual execution of
deployment steps
 Frequent release errors
11 © 2014 CA. ALL RIGHTS RESERVED.
 Reduction in build time to
keep track of changes
 Easier adoption by the
Business analysts and
Developers
 Early conflict resolution
 Reduction in release errors
 Reduction in time to deploy
CHANGE SET ( SFDC ) CA RELEASE AUTOMATION
WITH SUBVERSION
CA RELEASE AUTOMATION
WITH SFDC ACTIONS

12.
Release models for Salesforce Deployments
Salesforce
Administrator
Select 1 of 3 templates to create a release and execute
Developer
START
Configuration Only
Template Description
Code and
Configuration
Wait for
Configuration only A template that is selected for a release that has only configuration changes.
Code and Configuration
A template that is selected for a release that has both Code and Configuration
changes.
Release with user Lock out(s)
A big release that releases code and configuration and locks out user(s) before
deployments
12 © 2014 CA. ALL RIGHTS RESERVED.
Release with User
Lockout
Input release number
Choose the environment
to Deploy END
release process
to complete

13.
Before…After Comparative Analysis
Automatic tracking and conflicts resolution:
Zero hours required for tracking
Manual tracking of changes:
up to 16 hours per resource
Creation of a build request:
2 minutes per build
Change sets and documentation of steps:
up to 24 hours per build
Deployment of changes:
1-2 hours per deployment
Deployment of change set
up to 10 hours per deployment
13 © 2014 CA. ALL RIGHTS RESERVED.

14.
For More Information
Insert appropriate screenshot and text overlay
from following “More Info Graphics” slide here;
ensure it links to correct page ca Devcenter
To learn more about Devcenter, please visit:
http://bit.ly/1wbjjqX
14 © 2014 CA. ALL RIGHTS RESERVED.

15.
For Informational Purposes Only
Terms of this Presentation
This presentation provided at CA World 2014 is intended for information purposes only and does not form any type of warranty.
Content provided in this presentation has not been reviewed for accuracy and is based on information provided by CA Partners
and Customers.
15