Deployment and continuous
delivery without Jenkins (TM)
Nico Rehwaldt @nikku
Slide 2
Slide 2 text
Context: Continuous Integration
A practice.
As part of your DEV flow, automatically do anything — action
or time triggered.
1
Slide 3
Slide 3 text
Context: Continuous Delivery
A practice.
Build your software so it is always deployable throughout its
lifecycle.
See Martin Fowler - Continuous Delivery
2
Slide 4
Slide 4 text
Context: Technical support - CI Systems
Jenkins, Circle CI, Gitlab CI, GitHub Actions
Roll your own cron job or connect your bash script to a web
hook
SaaS or self hosted
3
Slide 5
Slide 5 text
CI Systems - Capabilities
Describe your job / pipeline
Multi-platform builds
Complex environment setup
Secret management
Upload to anywhere aka deploy
DEV flow integration
4
Slide 6
Slide 6 text
Show Case: Travis CI
Describe your job / pipeline
Multi-platform builds
Complex environment setup
Secret management
Upload to anywhere aka deploy
DEV flow integration
5
Slide 7
Slide 7 text
Show Case: Travis CI
.travis.yml in a project defines the projects build
pipeline
Infrastructure as code
6
Slide 8
Slide 8 text
Simple jobs...
language: node_js
node_js: 'node'
script:
- npm run all
7
Slide 9
Slide 9 text
More complex jobs...
bpmn-js
Camunda Modeler
8
Slide 10
Slide 10 text
Demo
9
Slide 11
Slide 11 text
Wrap up
No self-hosted Jenkins is needed in many cases
Infrastructure as code is
Visibility and feedback is
Proper integration into DEV flow is a must
10