4. About XebiaLabs
Success stories
o
o
Headquartered in Boston, Massachusetts
Global development and support offices in
US, NL, UK, France and India
Automate & Accelerate Application Delivery
The XL platform combines Build, Deployment,
Provisioning and Delivery Automation to help
enterprises deliver higher quality software faster.
o
o
o
Reduce development applications costs
Accelerate application time to market
Bridge the gap between Development and
Operations
And more…
5. Release Coordination Challenges
o
Many disparate information sources: Wikis, emails, Excel sheets, CI
tools, Change Management tools etc. + mix of manual & automated
steps
o
Results in lots of unpleasant surprises, stressful problem fixing, reactive
management, no shared insight
o
No audit trail when the release deviates from the plan
Releases are:
o
Unpredictable and inefficient
o
Prone to “unpleasant surprises”
o
Nobody knows what’s going on
6. Application Release Documentation
To ensure that everyone follows the same release procedures,
companies create long, complex documentation to describe the
application release process.
Software release
1.
o Difficult to maintain
For the software releases, Developers should make a request via e-mail to the Release Manager and
assign the task to himher regarding the confirmation of compatibility and readiness of the web
components.
Notification Thread
To: Release Management
Subject: release of <software> <version>
Content:
A Software release is planned
date
realm
Software release
o Typically, not applicable for all
software releases
2.
3.
1. For the software releases, Developers should make a request via e-mail to the Release Manager and
Release Manager has the right to decline the release by indicating the reason in the e-mail
assign the task to himher regarding the confirmation of compatibility and readiness of
response to the initial request. Further activities are organized according to the point "Software release. the web
components.
Release Manager makes a configuration e-mail request to the PMs, mentioning the web components
Notification Thread
and their versions, basing on the versions of the released components in the release calendar and
To: Release Management
version matrix, adds a calendar item and assigns the task regarding the compatibility and readiness of
Subject: release of <software> <version>
web components to the Lead QA person.
Content:
Planning Thread
To: <planning>*
A Software release is planned
Subject: Release. release of <software> <version>: Update web
date
realm
Update of following web-components is planned for the date software releases, Developers should make a request via e-mail to the Release Manager and
1. For the for the realm-s realmrealm-s:
2.
decline the release by indicating the reason in the e-mail
Web components Release Manager has the right to assign the task to himher regarding the confirmation of compatibility and readiness of the web
response to the initial request. Further activities are organized according to the point "Software release.
components.
Kindly ask you to confirm if the versionmakes a configuration e-mail ready (notto the PMs, mentioning the web components
3. Release Manager is right and the component is request later than date )and to
Notification Thread
appoint QA and Dev in charge.
and their versions, basing on the versions of the released components in the release calendar and
To: Release Management
version matrix, adds a calendar item and assigns the task regarding the compatibility and readiness of
Subject: release of <software> <version>
person.
*for more detailsweb components to the Lead QA Content:
about mailing groups please see notification matrix
Planning Thread
Not later than two working days before the release Project Managers are to confirm the
To: <planning>* readiness for the release on the indicated date. The regulations are
A Software release is planned
correctness of the versions and their
Subject: into account the technical details of the upcoming release.
Release. release of <software> <version>: Update web
date
actualized if possible taking
realm
Lead QA person appoints RQA-а and assigns the task to him/her to receive the confirmation of
Update of web components. RQA analyzes status the date for the realm-s realmrealm-s:
compatibility and readinessof following web-components is planned forof web components of the versions
2. Release Manager has the right to decline the release by indicating the reason in the e-mail
Web components
that are indicated in the task, assigns the task to Release Manager with the status changed to Resolved.
response to the initial request. Further activities are organized according to the point "Software release.
Software release
o Directs users to various systems of
knowledge for complying with
process
o Inflexibility when releasing to nonPROD environments
o Rules not enforced
4.
5.
Release Manager has the ask you decline the if the version is right and the component is ready (not later than date )and to
basing on the information provided by Project
Kindly right to to confirm releaseRelease Manager makes a configuration e-mail request to the PMs, mentioning the web components
3.
appoint QA and further activities and organized according to the point «Software released components in the release calendar and
Managers и RQA-s. In this case theDev in charge.
are their versions, basing on the versions of the
release. Decline of the release».
version matrix, adds a calendar item and assigns the task regarding the compatibility and readiness of
Release Manager by responding to the initial requestweb componentsManagernotification matrix
from GRelease to the Lead QA person.
*for more details about mailing groups please see confirms that the web
component is ready for the release and closes the task to receive confirmation of compatibility and
Planning Thread
4. Not later than
readiness of the web components. two working days before the release Project Managers are to confirm the
To: <planning>*
correctness of the versions and their readiness for the release on the indicated date. The regulations are
Notification Thread actualized if possible taking into account the technical details of the upcoming release.
Subject: Release. release of <software> <version>: Update web
To: reply all
Lead QA person appoints RQA-а and assigns the task to him/her to receive the confirmation of
Subject: RE: release of <software> <version> of web components. RQAweb-componentsof web components of the versions
Update of following analyzes status is planned for the date for the realm-s realmrealm-s:
compatibility and readiness
Content:
Web components
that are indicated in the task, assigns the task to Release Manager with the status changed to Resolved.
5.
Release Manager has the right to Kindly ask you to confirm if on the information providedcomponent is ready (not later than date )and to
decline the release basing the version is right and the by Project
appoint QA and Dev in charge.
Managers и RQA-s. In this case the further activities are organized according to the point «Software
release. Decline of the release».
Release Manager by responding to the initial details from GRelease Manager confirms see notification matrix
*for more request about mailing groups please that the web
component is ready for the release and closes the task to receive confirmation of compatibility and
4. Not later than two working days before the release Project Managers are to confirm the
readiness of the web components.
correctness of the versions and their readiness for the release on the indicated date. The regulations are
Notification Thread
actualized if possible taking into account the technical details of the upcoming release.
To: reply all
Lead QA person appoints RQA-а and assigns the task to him/her to receive the confirmation of
Subject: RE: release of <software> <version> and readiness of web components. RQA analyzes status of web components of the versions
compatibility
Content:
that are indicated in the task, assigns the task to Release Manager with the status changed to Resolved.
5.
Release Manager has the right to decline the release basing on the information provided by Project
Managers и RQA-s. In this case the further activities are organized according to the point «Software
release. Decline of the release».
Release Manager by responding to the initial request from GRelease Manager confirms that the web
component is ready for the release and closes the task to receive confirmation of compatibility and
readiness of the web components.
Notification Thread
To: reply all
Subject: RE: release of <software> <version>
Content:
7. What is Application Deployment Really?
Well, yes, there is all the work to deploy the app
o
o
o
o
o
o
Installing applications
Updated applications
Configuring resources
Configuring middleware components
Starting/stopping components
Configuring the installed application
..and there’s all the other
work that has to be done…
o
o
o
o
o
E-mail notifications
Authorizations
Validation gates
Notifications
Tasks to complete
o Updates to systems
Prod
1,2&3
My app
v 1.x
v 2.x
v 3.x
QA
1&2
Dev 1
8. XL Release – Advanced Enterprise Coordination
XL Release is an advanced enterprise release coordination
software solution that allows you to:
o
Plan, track and execute release plans from code
drop to end user
o
Pro-actively avoid delays and release failures by
tracking resource conflicts, dependencies and
pending tasks
o
Accelerate your delivery process by replacing
manual with automated tasks and standardizing
release plans
By providing a single source of truth and increasing the level of automation and
standardizing the release process, XL Release helps customer deliver higher quality
software faster.
9. XL Release – Key Features
Collaborate
Accelerate
Reduce
Collaborate:
o Easy modeling of your release plan
o Support for gates, conditions, dependencies
o Calendar overview of planned and ongoing releases
10. XL Release – Key Features
Collaborate
Accelerate
Reduce
Accelerate:
o Combine manual and automated tasks
o Grow automation progressively
o Adapt plans during a release with full audit trail
11. XL Release – Key Features
Collaborate
Accelerate
Reduce
Reduce:
o Full audit trail - what happened where, when, why & by whom
o
o
Delivery pipelines giving a high-level overview of on-going
releases
Drive automation based on metrics vs. “feel”
12. XL Release – Key Benefits
Plan
Execute
Automate
Plan:
o
Making releases more predictable, more efficient, less manual
and less error-prone
o
Results in less downtime and more higher quality delivery
achieved faster
o
One place to document and track what needs to happen for
an entire application/platform release across multiple teams
13. XL Release – Key Benefits
Plan
Execute
Automate
Execute:
o
Manage Dependencies and Conflicts
o
Insight into overlapping and conflicting release activities and
overloaded resources across projects
o
Gain oversight and effect change proactively where needed
14. XL Release – Key Benefits
Plan
Execute
Automate
Automate:
o
One place to document and track what needs to happen for
an entire application/platform release across multiple teams
o
Single source of truth for all team members to see the state of
the release process
o
Measurable path towards more automated, standardized
releases
16. More Info
o Whitepaper: Next Steps in Advanced Enterprise
Release Coordination:
o http://go.xebialabs.com/
ASLPNextStepsinReleaseCoordination_1Register.html
o XL Release Demo Video
o http://youtu.be/rXH-qPtOSXY
o XL Release Product Fact Sheet:
o http://go.xebialabs.com/rs/xebialabs/images/XL-releaseFactSheet.pdf
o XL Release web content:
o www.xebialabs.com/xl-release-overview
18. Thank You!
CONTACT DETAILS
o TJ Randalll: trandall at xebialabs dot com
NEXT STEPS
o More information: www.xebialabs.com
GET STARTED
o Trial: http://go.xebialabs.com/TrialXL.html
STAY INFORMED
XebiaLabs Products: www.xebialabs.com/products
Blog: blog.xebialabs.com
Twitter: @xebialabs
YouTube: youtube.com/xebialabs
