Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Deployment and continuous delivery without Jenk...

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.

Nico Rehwaldt

April 28, 2020
Tweet

More Decks by Nico Rehwaldt

Other Decks in Programming

Transcript

  1. Context: Continuous Integration A practice. As part of your DEV

    flow, automatically do anything — action or time triggered. 1
  2. Context: Continuous Delivery A practice. Build your software so it

    is always deployable throughout its lifecycle. See Martin Fowler - Continuous Delivery 2
  3. 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
  4. CI Systems - Capabilities Describe your job / pipeline Multi-platform

    builds Complex environment setup Secret management Upload to anywhere aka deploy DEV flow integration 4
  5. 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
  6. Show Case: Travis CI .travis.yml in a project defines the

    projects build pipeline Infrastructure as code 6
  7. 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