Pre-Con Lab: Getting Started (and Hands-on) with CA Release Automation Continuous Delivery Edition

World®
’16
Getting Started with CA Release
Automation Continuous Delivery Edition
Andrew Cluttey - Principal Consultant, PreSales – CA Technologies
D05X25L
DEVOPS

2 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
© 2016 CA. All rights reserved. All trademarks referenced herein belong to their respective companies.
The content provided in this CA World 2016 presentation is intended for informational purposes only and does not form any type of
warranty. The information provided by a CA partner and/or CA customer has not been reviewed for accuracy by CA.
For Informational Purposes Only
Terms of this Presentation

Abstract
Is the volume, quantity and complexity of releases from multiple
organizations creating new bottlenecks in your rapid delivery of apps?
CA Release Automation Continuous Delivery Edition can help your
organization pull together all aspects of an extensive, heterogeneous
release pipeline. It provides a single control point to manage, release
and track content for multiple applications across any number of
organizations and deployments. In this getting started session, you will
learn how to plan multiple, concurrent releases, link user stories and
defects, resolve dependencies, manage conflicts and promote cross-
team collaboration.
Andrew
Cluttey
CA Technologies
Principal Consultant
PreSales

Agenda
CHALLENGES FOR CONTINUOUS DELIVERY PIPELINES
CREATE A BASIC RELEASE
QUESTIONS AND ANSWERS
HANDS ON LAB
MANAGING MULTIPLE RELEASES
HANDS ON LAB
1
2
3
4
5
6

Challenges for Continuous Delivery
Pipelines

Continuous Delivery Ecosystem & Workflow
Write user stories
(requirements)
Right data for the
right test environment
Dev Test QA Prod
Continuous
integration
(Build-Deploy-
Test)
Continuous Delivery Workflow
Build / deployment / promotion dashboard and reports
Adaptive, dynamic releases Automated & manual testing/test data Deployment workflow, rollback, pre/post tasks
Automated test
kick-off, tracking
Testing coverage &
progress reporting
Trigger build &
deploy in Dev
Runboo
k
Deployment
automation
Release & artifact tracking,
environment mgmt, baselining
Application
knowledge
Link application to user stories
To Do Doing Done
ManageAuthorize
Trigger
release
deployment
Plan
Releases
Plan Release
Trains
Promote
Define release
workflow, gates
& environments
Watch progress
(tracing, auditing, reporting)
Create release
package with
build /deploy
status
Get app
definition
Release Manager
Product Owner
Business User
Scrum Master
Enterprise
Architect
Dev
Developers
QA
Test/QA
Deployment
Manager
Customer
Implement
components
Define app:
Component
s
& versions
Infra provisioning / environment mgmt / PaaS / containerization / configuration mgmt
Agile
Central
Use
app

New Pressure Points in the Continuous Delivery Pipeline
Forward-looking companies have been designing, developing and delivering apps
more effectively to dramatically improve the customer experience……and uncovering
new pressure points in the Continuous Delivery pipeline.
Complex
multi-level
applications
Having to balance
velocity and
quantity
Multiple teams on
multiple projects
Prioritizing the
deployment of the
right content

QA/TEST PRE-PROD PRODUCTIONDEV
ZERO-TOUCH
DEPLOYMENT
Continuous Delivery Dynamic Duo
Zero-touch Deployment + Advanced Release Management
Continuous Delivery DashboardOPTIMIZE
PIPELINE
CA Release
Automation
CA Release
Automation
CD Edition
PLAN & MANAGE
RELEASES

Managing
complex multi-
application
releases
CA Release Automation Continuous Delivery Edition
Providing key
performance
metrics
allowing
customers to
continually
improve their
release pipeline
Answering the
question, what
content is in
what release
and where is it
in the Release
Pipeline
Open
integration, and
a focused set of
integration
points with CA
tools delivering
a CA continuous
delivery
ecosystem

Building Blocks of a Release
APPLICATIONSWhich applications are going to be handled?
WORK PLANWhat is the workflow to be done in each phase?
TIMELINEWhen should each phase run? Do they conflict?
STAKEHOLDERSWho are the people participating in the release?
CONTENTWhich stories & bugs are going to be delivered?

Creating a Basic Release

CA Release Automation Continuous Delivery Edition Objects
Application Content Integration
Internal or External Content
Agile Central / Jira
User Stories, Tasks, Defects/Bugs
Stakeholders
Owners, Members
Tokens
User Defined last_successful_build
Release
Release Name, Version Application,
Owners, Members
Phase/s
Phase name, owners manual, auto,
Sched environments
Task/s
Task name, description, owners task
type
User Management
Groups, Users LDAP, AD, Internal
Tracks
Track name, owners production time
frame
Milestones
Applications
Plug-ins
Release automation
Jira
Agile Central (Rally Platform)
Rest 1.0
Jenkins
ServiceNow
Contains
Contains

High Level Workflow
Run Release
Define users/groups
Configure endpoints
Agile Central, Jira,
RA, Jenkins, Rest
ServiceNow
Import RA applications
Manage/view
output
Create Release/s
Add Application/s
link content for App
Create Phase/s
Manual, scheduled, automatic
Start/end times, environment/s
Add tasks/type
Manual, run deployment, rest,
Jira, Agile Central

Creating a Basic Release Lab

Lab Steps: Releases > New Release
Enter data as shown in
graphic:
Applications exist in CA
Release Automation
Click Create

Lab Steps: GC Coffee Applications
Set each Applications version.
Content, (Jira, Agile Central,
Internal), can now be
associated with the
application.
Click Check mark to save

Lab Steps: Releases > GC Coffee > Phases
Create Phase Name: Stage
Choose ‘Stage’ from
environment dropdown.
Set from/to – Today/Tomorrow
Conflict generated : planned
date is outside defined
maintenance windows for the
Stage environment
Click Create

Lab Steps: Phase > Stage > Create tasks
Create tasks based on data in
table. All tasks run in numbered
sequence
Tip: Duplicate 4th and 5th tasks
from 3rd task by highlighting task.
Change task specific data
and clicking
1st Task: 2nd Task: 3rd Task:
4th Task: 5th Task:

Lab Steps: Check Your Defined Tasks
Check that your stage is identical to the sequence
in the graphic.
Note: Sequence is implied, as shown by the gap
between tasks. If tasks needed to run in parallel,
you would drag the task towards the task which
needed to run in parallel

Lab Steps: Create Production Phase
Highlight ‘stage’ phase to
duplicate
Duplicate Phase: Stage to create
Production phase
Change all ‘stage’ environment
references to be ‘production’
Change Phase to Automatic
Delete task: Readiness

Lab Steps: Update Production tasks
Edit all tasks in production phase
and make sure their
environment is pointing to the
‘production’ environment

Lab Steps: Run Release
Click the to run the Stage
phase
The readiness task is just an
example of using a manual
runbook task, in this case to
confirm all readiness for the
release.
Mark the Manual task as ‘Done’

Lab Steps: Confirm Your Release Was Successful
Check that all the tasks run
successfully.
The Release can be marked as
done, when it has been decided
that it is complete.
Check the activity window for
activities performed during the
release
“Congrats”

Managing a CA Release Automation
Continuous Delivery Edition Release

Offers Important Continuous Delivery Integration Points
CA Release Automation
Continuous Delivery Edition
ALM
Continuous
Integration
Testing
Provisioning
Deployment
Change
Management
Application
Tracking
Release
Execution
Productivity
Metrics
Process
Improvement
Conflict
Avoidance
Business
Value
§ CA Release Automation
§ CA Agile
Central/Atlassian Jira
§ Jenkins
§ Rest
§ ServiceNow
§ Custom Plug-in
DATA &
OPERATIONS

What Makes Up The Contents Of A Release
§ Installer checks for JDK and prompts for Tomcat installation folder
§ Download from CA support siteConfigure Endpoints
Define internal Apps and import RA
Apps from defined endpoint/s
Define Release, Phase, Task and link
associated user stories, issues etc to
individual apps within each release
Agile Central
UserStories Task
Defects
Jira
Issues
Plugins
Run Deployment
Run Process
Jira
Agile Central
ServiceNow
Rest
Manual
Phase: Stage estimated start/end dates
Select App Environment
Task 1
Run Deployment: App 1
Link content
Task 2
Link content
Task 3
Link content
Task 4
Jira Add/Update/Create Issues
Task 5
Agile Central Task/Defect Update Check test
case results
Task 6
Rest – Get. Post. Put
Delete, patch, head
Task 7
Manual
Task 8
ServiceNow – create/update task
Create/update Chg Req
Wait for approval
Phase: Production estimated start/end dates
Select App Environment
Task 1
Link content
Task 2
Link content
Task 3
Link content
Task 4
Jira Add/Update/Create Issues
Task 5
Agile Central Task/Defect Update Check test
case results
Task 6
Rest – Get. Post. Put
Delete, patch, head
Task 7
Manual
Task 8
Run Process
Release A
App1, App2, App3
OwnersLink Content to
Application
contains

Plugin Capabilities in CA Release Automation
Continuous Delivery Edition
Run Deployment Run Process Manual Rest
Run RA deployments
utilizing all RA
integrations.
Used to run individual RA
processes without tying to
a deployment plan
Add any manual runbook
tasks and/or any manual
decision needed for the
phase
Used to automate any
tasks not covered by a
standard plugin and
supports Rest
Agile Central
Link Agile Central content, as well
as updating task/defect status
and/or checking test case results
ServiceNow
Create/update ServiceNow task or
Change Request.
Wait for SNOW approval
Jira
Link Jira content, as well as run
tasks to add/update or create
issues

CA Release Automation CD Edition – Continuous Delivery Metrics

Agilely Manage Complexity of Cross-Application Releases
Release A
Release B
Release C
Continuous Delivery
Story 1
Story 2
Story 3
Story 4
Story n
§ Release and track stories
independently or grouped
based on business
requirements
§ Map customer feedback to
user stories, features and
bug fixes moving through
the release pipeline
§ Gain visibility of and
reconcile dependencies
Manage and monitor multi-application content through the release cycle

Release Tracks Enable Visibility and Governance
of Key Releases within Large Enterprise Releases
Release A
Release B
Release C
Story 1
Story 2
Story 3
Story 4
Story n
Manage and monitor multi-application content through the release cycle
Release Track 1
Group and manage
releases to a common
release cycle & schedule
or to fulfill dependencies
Use Release Tracks to drive
cadence of releases
delivered to production
Continuous Delivery

Dynamic Release Pipeline Tasks
§ Download from CA support site
Pipelines have to be dynamic !!!
For example in a multi app release, one
app deployment fails, you need to be able
to :
Rerun just that deployment task, skip that
task, run the whole phase again, skip the
rest of the phase etc. etc.

Understanding Your Release Dates

End to End Traceability Across the Release Pipeline
§ Download from CA support site Associate CDE
Application task
To Content
Define CA Release
Automation CD Edition
(CDE) Release
Link Jira/Agile Central
Content to CA Release
Automation (RA)
Application in CDE
Jenkins build triggers
CDE Release for named
App
CDE Content Report shows what content
delivered in release
CDE Application Report
shows deploy status
RA deploys build. Artifact
Management in RA has build number
1 2 3
4 5 6

2 31

4
5
6

Managing CA Release Automation
Continuous Delivery Releases - Lab

Lab steps: Manage a CA Release Automation
Continuous Delivery Release
Placeholder
Run Release
Configure
Application Content
Check
last_successful_build
Create ServiceNow
ticket
Manage/view
output
Inspect Calendar and
conflicts
Add Release to
Track
Configure Release tasks

Lab steps: Configure Application Content
Step1, Step2, Step3 etc

Lab steps: Check Jenkins integration

Lab steps: ServiceNow ticket

Lab steps: Manage Calendar

Lab steps: Configure Release Tasks

Lab steps: Run release

Lab steps: Manage Output

Questions?

Recommended Sessions
SESSION # TITLE DATE/TIME
DO5T21P
Keynote: End-to-End Integrated Continuous Delivery
Ecosystem: How to Drive Innovation and Differentiation
11/16/2016 at 10:30 am
DO5T02P
Leadership Panel: DevOps Leaders Discuss the Journey to
Continuous Delivery
11/16/2016 at 01:45 pm
DO5T14S
Analyst Keynote:
Continuous Delivery: Making DevOps Awesome
11/17/2016 at 10:30 am

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

Pre-Con Lab: Getting Started (and Hands-on) with CA Release Automation Continuous Delivery Edition

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (6)

Similar to Pre-Con Lab: Getting Started (and Hands-on) with CA Release Automation Continuous Delivery Edition

Similar to Pre-Con Lab: Getting Started (and Hands-on) with CA Release Automation Continuous Delivery Edition (20)

More from CA Technologies

More from CA Technologies (20)

Recently uploaded

Recently uploaded (20)

Pre-Con Lab: Getting Started (and Hands-on) with CA Release Automation Continuous Delivery Edition