The author reflects on their experiences with Jenkins, a continuous integration/continuous deployment (CI/CD) platform, highlighting its evolution from a plugin-heavy tool to a more mature system with the introduction of Jenkins 2.0, which emphasized "Pipeline as Code" and containerization using Docker. The narrative jumps to 2025, where Jenkins is deployed on Kubernetes using Pulumi for infrastructure as code, showcasing a modern, scalable, and efficient CI/CD setup. This approach leverages Kubernetes' orchestration capabilities and Pulumi's programming flexibility, offering benefits like ephemeral build agents, seamless environment isolation, and reproducible infrastructure configurations. The author acknowledges the advancements Jenkins has made but also considers newer CI/CD platforms like GitHub Actions, GitLab CI/CD, Tekton, and Argo Workflows, which offer cloud-native features and reduced infrastructure complexity, suggesting that while Jenkins retains its utility, especially in legacy systems, the modern landscape provides more streamlined alternatives for cloud-native environments.