Jenkins

Overview Jenkins users fall into two camps: one fills out forms on the web UI, clicks a few buttons, and gets things running — simple and direct. The other writes Jenkinsfiles in the code repository, turning build pipelines into code with version control, peer review, and rollback all built in. The first is called Freestyle Project. The second is called Pipeline Project. These two aren’t mutually exclusive. Many teams use both — simple script tasks with Freestyle, complex multi-stage releases with Pipeline....

Overview Pipeline as Code is the watershed moment when Jenkins evolved from “drag-and-drop configuration” to “code-driven.” Defining pipelines in a Jenkinsfile under Git version control means every pipeline change has a diff to review, a history to trace, and a branch to roll back. This article systematically covers Pipeline as Code practices, from Jenkinsfile syntax to production-grade pipeline design. Reference: Jenkins Pipeline Official Documentation I. Jenkinsfile Syntax 1.1 Declarative vs. Scripted Jenkins Pipeline has two syntax styles:...