Now It's Your Turn

I showed a very opinionated way to do continuous delivery and continuous deployment using Jenkins X in a Kubernetes cluster. Unlike The DevOps 2.4 Toolkit: Continuous Deployment To Kubernetes, the opinions didn’t come from me, but rather the platform itself. Unlike the traditional Jenkins, Jenkins X dictates how you should do continuous delivery or continuous deployment. It can be tweaked, but you do need to comply with some, if not all, of its processes. GitOps, for example, is a must. Without it, you’d lose too many of the great features it offers.

Staying up to date

At the time of this writing (October 2019), Jenkins X is still in its early phases, and we can expect that great new features are coming. I’ll do my best to keep this course up-to-date.

If you’re here, you now have an excellent foundation with Jenkins X. Now it’s up to you to implement it in your organization and put it to the only real test by running it in production. That is, if I managed to convince you that Jenkins X is the best way to implement continuous delivery inside your Kubernetes clusters.

Feedback

That being said, I’d love to hear about your experience.

• Are you using Jenkins X?
• Did you create a custom build pack?
• How did you onboard teams?

Any information about the way you use it and your experience with Jenkins X will help us improve the project. Please send me what you created. I want to see your processes and your pipelines. Even more, I’d love to work with you to publish them in a blog or as an appendix to this book. If you think you did something interesting, and I’m sure you did, please contact me on the DevOps20 Slack and show me what you created.

You learned from others, now it’s time for others to learn from you. I’m done explaining what I did, now it’s your turn to share what you made.

---

Please check out the next lesson to learn about the amazing people who made this course possible.