Jenkins as code for multiple teams (on-site)
Details
Dear DevOps Community
I’m thrilled to invite you to an ON-SITE Meetup at Vontobel (Bleicherweg 21, 8002 Zurich, Switzerland).
I am very happy that Vontobel shows us how to setup a distributed Jenkins as infrastructure as code.
Abstract:
One-click installations may get you started faster, but they will hurt you in the long run if you are not able to reliably reproduce your deployed instance.
During this talk we will discuss why we ran into this issue and how we solved it. More specifically, we will go into design and implementation details of how we created an open-source Jenkins for multiple teams across Vontobel, while sticking to the following concepts:
- Disaster recovery being at the forefront of our design
- Every Jenkins build and deployment can be reproduced
- Read-only Jenkins in production
- Jenkins itself based on GitOps: Jenkins in production always reflects what is in GIT
We will walk you through our entire setup, from building Jenkins docker images to deploying Jenkins on OpenShift. How to install, upgrade and uninstall Jenkins plugins, how to keep Jenkins as CasC (Configuration as Code), authentication, and Jenkins jobs as code.
Improving CI/CD is a never ending journey, and therefore we will end this session by also mentioning a few things that we still need to refine.
Bio:
Olga Diaz, Full-Stack Engineer @ Vontobel
I am a software engineer currently working towards continuous deployment, in the meantime I am a button-clicking expert.
My world is encompassed by Spring Boot, Angular, Ionic and the never ending framework saga.
I program in many languages (except German) by day, and forget it all at night with beer.
Patrizio Simona, Software Engineer and Techie at Heart at Oepfelbaum
Studied Robotics at ETH Zurich
Built drones for the entrainment industry
Brought live 2 E-Banking Projects for Swiss Banks
One constant DevOps
Don Kodiyan, Software Engineer at dsi engineering ag.
I’m currently working @ Vontobel on the advisory platform for our client advisors.
When I’m not writing code, I like to play basketball or drink beer to forget our flaky Jenkins builds.
After the talk there will be enough time for questions and discussions.
Agenda:
17:00- 17:15: Organizer's welcome messages
17:15 - 18:15: Talk
18:15 - 18:45: Q&A, Discussion
18:45 - 22:00: Apero
Looking forward seeing you :)
