Jenkins X: Continuous Delivery for Kubernetes with James Strachan

The last 5 years has seen a huge change in how we build, package, run and manage software with the rise of Kubernetes, Cloud Native, Microservices and Continuous Delivery. As a result we all need to get better at delivering business value to our customers faster and continuously with a cloud native strategy - but how?
This talk will introduce you to a new open source project, Jenkins X which is an open source CI / CD platform for Kubernetes based on Jenkins.
After a couple of slides we'll spend most of talk demonstrating how to get stuff done with Jenkins X:
easily setup your own Jenkins based CI / CD system on your cloud of choice
quickly get started developing new microservices with automated CI / CD
import existing projects with automated CI / CD
use Pull Requests to trigger CI, Preview Environments, human approval then a full CD release
use automated provisioning to testing, staging, ephemeral and production environments via helm charts and GitOps
After this talk you should be able to develop at full speed with CI / CD in a cloud native way in any language on any cloud or kubernetes cluster! Lets all go faster!

[@spursn17uk]

Can Jenkins x be deployed using terraform for both cluster creation and the Jenkins x install?

[@JamesStrachan]

BTW here are my slides: docs.google.com/presentation/d/1hwt2lFh3cCeFdP4xoT_stMPs0nh2xVZUtze6o79WfXc/edit?usp=sharing and there's more docs & demos of Jenkins X at: jenkins-x.io/

[@piratevv]

excellent talk

[@ThePuTaMaDrE00]

This is all Greta and beautiful but there is no features for really test integration of microservices together. I still need to write a pipeline that does it serially on commute to master so we know that all microservices work together in their latest version all the time.

[@JamesStrachan]

We need to create a demo & blog post to show how to do that in more detail; but basically you can include whatever system/regression/acceptance tests inside your Preview helm chart so that they are all invoked in a separate namespace as part of the existing Preview pipeline: jenkins-x.io/about/features/#preview-environments You just need to edit the `charts/preview/requirements.yaml` file to add whatever charts are required to run your system/regression/acceptance tests with whatever other test frameworks or dependent microservices you wish to use. If you wanna know more pop into Slack or raise an issue and we can walk through how it all works: jenkins-x.io/community/

[@JamesStrachan]

you can use Previews or Environments for that. A Preview or Environment are just defined via helm charts; so you can add whatever dependencies you need to other microservices you wanna test (either by deploying separate copies of the microservices in the preview/environment - or by service linking to, say, the Staging/Production versions of the microservices)

[@ThePuTaMaDrE00]

James Strachan is there a full/partial sample of using Jenkins x and microservices with integration?

[@rarknoefi7545]

I'm also super interested in this, would be great if there's an up to date demo

[@JamesStrachan]

all the demos are here: jenkins-x.io/demos/ and articles: jenkins-x.io/articles/

[@ongeri]

I am a ninja operator developer :D

[@Goodwin454]

No idea what he was talking about