Techniques for Jenkinss
Jenkins pipeline techniques are the features beyond a simple linear build: parallel stages, when conditions, matrix builds, parameters, post actions, input approvals and artifact archiving. This unit sits in the Pipelines in Practice stage and shows how to model realistic workflows with branches, environments and failures.
Stage: Pipelines in Practice · Part of the Jenkins roadmap · Last reviewed 19 November 2026
What to learn in Techniques
- Run test suites in parallel stages to shorten pipeline time
- Use when conditions to deploy only from the main branch
- Define build parameters and read them in the pipeline
- Add post blocks that always archive reports and notify on failure
- Pause for manual approval before a production deployment
Techniques interview questions
What is the difference between declarative and scripted pipelines?
Declarative pipelines use a structured pipeline block with fixed sections such as stages and post, which is easier to read and validate. Scripted pipelines are free-form Groovy inside a node block, which is more flexible but harder to maintain.
How do you make a pipeline stage run only on a specific branch?
Add a when directive to the stage, for example when { branch 'main' }. In multibranch pipelines Jenkins creates a job per branch, and the condition skips the stage elsewhere. You can combine conditions with allOf, anyOf and not.
Where Techniques fits in the Jenkins roadmap
Techniques belongs to the Pipelines in Practice stage (intermediate level). Real workflows.
Other units in this stage
Back to the full Jenkins roadmap