5
Why Continuous Delivery Platform ?
● tight integration into Zalando infrastructure e.g.
○ Docker registry
○ IAM
○ Zalando cluster setup
● one file to configure tasks
○ no extra configuration via UI, plugins, configurations etc.
● managing 100+ Jenkins masters plus more agents is quite some effort
● unique build environment
● quick worker feedback
● worker easy scaling up and down
● transparent credential
8
Main Concepts
● proxy with user transparent credentials
○ untrusted build workers without secrets
○ transparent credential injection for artifact upload and source access in build workers
● deep integration
○ GHE, Zalando Sonarqube, Zalenium, Zalando Kubernetes
● “The Second Best Interface is The One You Already Use”
- Joao Santos
● scm-source.json generation out of the box
● all configuration in delivery.yaml file
Slide 9
Slide 9 text
9
Way of Working
● team does informed decisions
○ programming language
○ proxy technology
● weekly presentations (recorded for the whole company)
● weekly stakeholder alignment
● monitoring from the very beginning
Slide 10
Slide 10 text
10
https://www.flickr.com/photos/eyecatcherfotosde/25418973420/
Demo
- build https://github.com/zalando/ghe-backup
- delivery.yaml
- deploy to k8s with Github Enterprise feedback
- delivery.yaml
https://www.flickr.com/photos/eyecatcherfotosde/25102321260
Slide 11
Slide 11 text
11
https://www.flickr.com/photos/eyecatcherfotosde/25418973420/
- build https://github.com/zalando/ghe-backup
- delivery.yaml
- deploy to k8s with Github Enterprise feedback
- delivery.yaml
- (init Container)
I’m sure you have questions
https://www.flickr.com/photos/eyecatcherfotosde/25397937985