This document discusses combining continuous integration (CI) with change management. It proposes using a change document to define the scope of a change and a transport request to deliver implementation artifacts. The change document would trigger CI to build and test code changes. The tested changes would then be deployed to development and imported to the transport request. This allows leveraging both CI for agile development and change management for governance.

1. EXTERNAL
CPL216 – Best of Two Worlds:
Continuous Integration and Change Management

2. 2EXTERNAL© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Speakers 2017
Las Vegas
September 25 - 29
Bangalore
October 25 - 27
Barcelona
November 14 - 16
Christoph Szymanski Sreedhara G S Wolfram Kramer

3. 3EXTERNAL© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission of SAP.
Except for your obligation to protect confidential information, this presentation is not subject to your license agreement or any other service
or subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or any related
document, or to develop or release any functionality mentioned therein.
This presentation, or any related document and SAP's strategy and possible future developments, products and or platforms directions and
functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information in this
presentation is not a commitment, promise or legal obligation to deliver any material, code or functionality. This presentation is provided
without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a
particular purpose, or non-infringement. This presentation is for informational purposes and may not be incorporated into a contract. SAP
assumes no responsibility for errors or omissions in this presentation, except if such damages were caused by SAP’s intentional or gross
negligence.
All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from
expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates,
and they should not be relied upon in making purchasing decisions.
Disclaimer

4. 4EXTERNAL© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Challenge
Idea
Process
Demo
Agenda

5. Challenge

6. 6EXTERNAL© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Continuous integration: basic flow
Write code
Push to central
source code
management
system
Automated build & tests
1 2
SCM triggers
CI server3
4
Provide feedback5
SCM
CI Server

7. 7EXTERNAL© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Change request management with SAP Solution Manager
Process layer: change & release management process
Technical layer: implementation/execution of changes
Create
request for
change
Process
request for
change
Handover to
execution
Manage
change
execution
Coordinate
release &
deployment
Close
change

8. 8EXTERNAL© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Change management and continuous integration: how to combine?
“We already use SAP Solution Manager and we do not want to lose it’s
established change management capabilities.
But we like CI and want to be agile.”

9. Idea

10. 10EXTERNAL© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Best of two worlds: continuous integration meets change management
Change Request Management
Quality Gate Management
Central Transport Management
Continuous
integration
Change
management
Integrate frequently
Automated verification
of each change

11. 11EXTERNAL© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Best of two worlds: continuous integration meets change management
Continuous
integration
Change
management
Change document
“What should be implemented by
the development team”
Transport request
“What has been implemented
by the development team”
createsdefines
scope
delivers
artifact
is
managed by

12. 12EXTERNAL© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Best of two worlds: continuous integration meets change management
The change document and the transport request are
the interface between continuous integration and change management.
Continuous
integration Change
management

13. 13EXTERNAL© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Best of two worlds: continuous integration meets change management
Leading process
Triggers development and defines the
implementation scope
Manages delivery to quality and
production system
Secondary process
Triggered by change document(s)
Delivers iteratively artifacts in high quality into open
transport request(s)
(development system)
Continuous
integration Change
management

14. 14EXTERNAL© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Best of two worlds: continuous integration meets change management
Continuous
integration Change
management
Development Test Production

15. 15EXTERNAL© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Best of two worlds: continuous integration meets change management
CPL126 S4H111
Continuous
integration Change
management

16. Process

17. 17EXTERNAL© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Change management: creation of change document
Business
key user
Business
requirement
Request for
change (RfC)
Change
manager
creates
creates
Change
document

18. 18EXTERNAL© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Continuous integration: code changes
Change
document
Development team
triggers
Code
change
creates
refers to

19. 19EXTERNAL© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Continuous integration: build
Development team
Code
change
creates
CI server
builds
Artifact
Build
Test
Code
check
Change
document

20. 20EXTERNAL© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Continuous integration: deployment
Development team
Code
change
creates
CI server
builds
Artifact
Build
Test
Code
check
uploads
Change
document
Transport
request
deploys
Development
account
Deployment
Iteration

21. 21EXTERNAL© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Change management: acceptance testing
Change
document
confirms successful test
Quality
account
automatic
import
Transport
request
Tester
tests
Development team
passes to test

22. 22EXTERNAL© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Change management: release
Change
document
Change
manager
closes
Production
account
approves import
Transport
request
Business
key user
Request for
change (RfC)
closes
IT operator
imports

23. 23EXTERNAL© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Demo

24. 24EXTERNAL© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Best of both worlds!
Enterprise requirements, SOX, ITIL etc. covered by Solution Manager.
Solution Manager controls the release process.
Continuous Integration is applied to deliver high quality changes into the
development system.
Developers can make usage agile practices to have fast quality feedback.
Change Document and Transport Request are the interfaces between the two
worlds.

25. 25EXTERNAL© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Access replays of
 Keynotes
 SAP TechEd live interviews
 Select lecture sessions
http://sapteched.com/online
Continue your SAP TechEd discussion after the
event within the SAP TechEd Community!
 Read and reply to blogposts
 Ask your questions
 Join conversations
sap.com/community
See all SAP TechEd Blogposts
SAP TechEd Online/Community

26. 26EXTERNAL© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Further information
Related SAP TechEd sessions
CPL126 – Continuous Delivery
S4H111 – Change Control Management-Continuous delivery in agile and hybrid solutions
CPL275 – Continuous Delivery for SAP Fiori Apps on SAP Cloud Platform
SAP Public Web
https://www.sap.com/developer/tutorials/ci-best-practices-intro.html
SAP Education and Certification Opportunities
Watch SAP TechEd Online
www.sapteched.com/online

27. 27EXTERNAL© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Thanks for attending this session.
Please complete your session
evaluation for CPL216.
Dirk Lüdtke
dirk.luedtke@sap.com
Wolfram Kramer
wolfram.kramer@sap.com
Feedback
Christoph Szymanski
christoph.szymanski@sap.com
Contact information: