https://www.rafaelvzago.com/en/tags/ci/cd/Recent content in Ci/Cd on Rafael ZagoHugoen-US© Rafael ZagoFri, 24 Jul 2026 16:16:10 -0300https://www.rafaelvzago.com/en/posts/dominando-pipelines-de-alta-performance/Fri, 13 Jun 2025 00:00:00 -0300https://www.rafaelvzago.com/en/posts/dominando-pipelines-de-alta-performance/<p><a href="https://www.rafaelvzago.com/assets/img/headers/dominando-pipelines-de-alta-performance.png" class="img-lightbox" data-lightbox> <img src="https://www.rafaelvzago.com/assets/img/headers/dominando-pipelines-de-alta-performance.png" alt="" loading="lazy" decoding="async"> </a></p> <h2 id="the-need-to-evolve-challenges-of-basic-jenkins">The Need to Evolve: Challenges of &ldquo;Basic&rdquo; Jenkins</h2> <p>Jenkins is one of the most powerful and popular automation servers in the world. It drives countless CI/CD pipelines that build, test, and deploy applications. Managed only through the web UI — what many call &ldquo;ClickOps&rdquo; — it shows its weak spots.</p> <p>ClickOps creates problems that hurt agility and reliability on any project, especially in complex MLOps environments:</p> <ul> <li><strong>No versioning or audit trail:</strong> Who changed a job config? Why? Without version control those questions are almost impossible to answer. Rolling back a bad change becomes a manual treasure hunt.</li> <li><strong>Inconsistency and hard reproducibility:</strong> Cloning a Jenkins environment for development, staging, or disaster recovery is painful and error-prone. Small config drifts between environments cause unexpected failures.</li> <li><strong>Painful scale and maintenance:</strong> Managing dozens or hundreds of jobs by hand does not scale. Maintenance becomes a bottleneck, and consistency across projects stays out of reach.</li> </ul> <p>To get the reliability, speed, scale, and security modern projects need, you have to go beyond the basics.</p>