Deployment and continuous delivery without Jenkins (TM)

This Camunda Tech Talk introduces CI/CD as a practice and summarizes the basic capabilities offered by state of the art CI/CD tools.

It goes on show casing TravisCI as an alternative to Jenkins for small/medium sized OSS projects where focus lies on developer productivity, feedback and out-of-the box superb DEV flow integration.

Transcript

1. Deployment and continuous delivery without Jenkins (TM) Nico Rehwaldt @nikku
2. Context: Continuous Integration A practice. As part of your DEV flow, automatically do anything — action or time triggered. 1
3. Context: Continuous Delivery A practice. Build your software so it is always deployable throughout its lifecycle. See Martin Fowler - Continuous Delivery 2
4. 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
5. CI Systems - Capabilities Describe your job / pipeline Multi-platform builds Complex environment setup Secret management Upload to anywhere aka deploy DEV flow integration 4
6. 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
7. Show Case: Travis CI .travis.yml in a project defines the projects build pipeline Infrastructure as code 6
8. Simple jobs... language: node_js node_js: 'node' script: - npm run all 7
9. More complex jobs... bpmn-js Camunda Modeler 8
10. Demo 9
11. 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
12. Thanks 11