We want to have a closer look at various aspects and see how to make them fit into our highly modular Sling-based technology stack. This session should provide an introduction to fundamental concepts as well as best practices, approaches and ideas how to set up your own delivery pipeline.

1. APACHE SLING&FRIENDSTECHMEETUP
BERLIN,26-28SEPTEMBER 2016
Get theFlow!
DominikSüß, Adobe,Conrad Wöltge,Netcentric

2. Agenda
adaptTo()2016 2
▪ DevOps & Co.
▪ The Flow
▪ Demo
▪ Challenges

3. DevOps
adaptTo()2016 3
DevOps is a […] practice that emphasizes the
collaboration and communication of both software
developers and […](IT) professionals while automating
the processof software delivery and infrastructure
change.(https://en.wikipedia.org/wiki/DevOps)
Operations
DevOps

4. Continuous Integration
adaptTo()2016 4
Continuous Integration(CI) is a practice to
continuouslymerge the working stateof all
developers togetherandtest the sanity of the
integrated system.

5. Continuous Integration
adaptTo()2016 5
ReleasesareexpensiveReleasesareexpensive
Releasemoreoften!

6. Continuous Delivery
6
Continuous Delivery(CD) isthe practice
to continuouslyand automatically
validateeach integrated state for all
functionaland non-functionalaspects

7. Continuous Deployment
7
Continuous Deployment defines the practice
to automatethe flow of software from
development to production througha
continuouspipeline.

8. The Flow
adaptTo()2016 8
git Flow
(Pull-Requestbased)
Jenkins Pipeline

9. Demotime
9
Ingredients
- Slingshot application to build
- Jenkins 2.0 with Pipeline Plugin
- Docker Slingshot and Maven
- Github
Szenario
- Pull request: test and deploy to PROD 

10. 10
DEMO

11. Challenges:TestingContent
adaptTo()2016 11
▪ Whento to update slave statefor various stages?
Installationstateofproductionmight change
afterhitting earlypipeline stages

12. Challenges:Goals
adaptTo()2016 12
Tests to be automated ina pipeline:
▪ Test coverage (Unit tests, integration tests,...)
▪ Code analysistests (style, security, … )
▪ Non-functional tests (endurance, load, stress, security,
…

13. Challenges:ConfigurationManagement
13
▪ Split Configuration from Code
▪ Configuration needs to be versioned
▪ Keep configuration and infrastructure in synch
▪ Plan access control across stages for
Continuous Deployment pipelines.

14. Challenges:Sling Specifics
adaptTo()2016 14
▪ Continuous Delivery
Coming from file based technologies
on monolith repositories
▪ Challenges for Sling based Projects
▪ Maven and Java versioning
▪ OSGi load specifics
▪ Everything is content, data is key
▪ Content and configuration states
▪ Modularity of application

15. adaptTo()2016 15
Continueon UnattendedInstallations