Tools & Practices to disrupt the status quo
Reshape the way you build software on an ABAP stack
About me
- Technical Guidance Unit @ msg systems
- Interests & Background:
- #CloudNative, #CloudFoundry, #SAPCP ( ~2 yrs)
- #ABAP, #BOPF, #S4HANA ( ~8 yrs)
https://people.sap.com/victor.ionescu
@ivictor88 ( <-- look here for slides )
ionescuv.github.io
Some History && Motivation
DevOps Principles
[ ... high performing organizations deliver software faster AND WITH BETTER QUALITY ... ]
Change might be closer than we think
But first, where's the problem?
-
Quick iterations
-
Fast delivery
-
Automation
Expectation
Reality
- Slow, manual transport processes
- Conflicting changes
- Unstable environments
vs.
-
Responsible teams
-
Reliable delivery
- Silo thinking
- Documentation
- Fingerpointing
Expectation
Reality
vs.
-
High Quality
-
Fast customer feedback
- Long-lasting manual test phases
- Quality not PART of development phase
Expectation
Reality
vs.
Root Cause Analysis
Culture
Infrastructure
Culture
Infrastructure
All-in-one:
- IDE
- SCM
- compiler
- build server
- runtime
NW ABAP
?
Reshape Culture
using the right Tools
Let's try it out!
*not (yet) for productive use
local dev
push
dev
test
prod
CTS
pull
ABAP
UI5
Demo
[1] Application Overview
[2] Use abapGit
[3] Use Unit Tests
[4] Use end-to-end tests
[5] Use pipelines
[6] Pipelines in action
Conclusion
- Internalize & apply the Principles
2. Find the right tools to enable you
3. Stay tuned for updates!
How do you like #itconsapcj?
Thank you for your attention!
