<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pipeline on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/tags/pipeline/</link><description>Recent content in Pipeline on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 08 Oct 2026 07:00:02 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/tags/pipeline/index.xml" rel="self" type="application/rss+xml"/><item><title>Bye-bye Jenkins: why we migrated our pipelines to GitLab CI</title><link>https://javapro-en.svenruppert.com/bye-bye-jenkins-why-we-migrated-our-pipelines-to-gitlab-ci/</link><pubDate>Thu, 08 Oct 2026 07:00:02 +0000</pubDate><guid>https://javapro-en.svenruppert.com/bye-bye-jenkins-why-we-migrated-our-pipelines-to-gitlab-ci/</guid><description>&lt;p&gt;In the project environment of bahn.de and DB Navigator, we have migrated our pipeline engine from (several) Jenkins instances and hundreds of pipeline jobs to GitLab CI over the past few months. Due to the large number of instances, pipeline variants, and special features, this was a mammoth task that took us a lot of time and effort. Nevertheless, the migration was naturally associated with high expectations: standardization and unification of the development infrastructure, reduction of build infrastructure costs, reduction of cognitive load in the teams, and less exposure to security vulnerabilities.&lt;/p&gt;</description></item></channel></rss>