Way to the cloud - How We Moved Jenkins to GCP at Swisscom
Details
We are back! Get inspired in the middle of the week and get your head in the clouds.
Join this talk from Mattia Bordoni and Daniel Lorch, Senior DevOps Engineers at Swisscom, to learn about the engineering challenges they had to overcome in their journey to the cloud.
Today, internal Swisscom developers are building their software transparently on the Google Cloud Platform (GCP) infrastructure. As part of a pilot, our team enabled GCP to run our internal build tools. For the first time, we are able to share our learnings from our experiments with the public cloud.
What are the steps necessary to migrate internal developer tools to a public cloud environment? For more than three years already, our team is offering build tools like Jenkins as a Service to a growing internal user base. Until recently, these tools were running on an internal VMWare-based stack. This platform was going to be decommissioned. This summer, after nine months of effort, we successfully and securely re-platformed our stack to the public cloud with almost no user impact. Jenkins alone accounted for 1'500 containers that were migrated in the process. As a next step, we refactored the service to cloud-native architecture and enabled the users to benefit from the elasticity of the cloud, as well as saving costs.
