Setup for Jenkinss
Jenkins setup covers installing the controller, completing the first-run wizard with the initial admin password, installing plugins, and creating a first pipeline job from a Jenkinsfile. It is the only unit in the Getting Started stage, and it gets a working server and a simple build-and-test pipeline running before more advanced topics.
Stage: Getting Started · Part of the Jenkins roadmap · Last reviewed 19 November 2026
What to learn in Setup
- Install Jenkins on Linux or run it from the official Docker image
- Complete the setup wizard using the initial admin password
- Install and update plugins from the Manage Jenkins screen
- Create a pipeline job that checks out code from a Git repository
- Write a basic declarative Jenkinsfile with build and test stages
Setup interview questions
What is the difference between a Freestyle job and a Pipeline in Jenkins?
A Freestyle job is configured through the web form and is hard to version or review. A Pipeline is defined as code in a Jenkinsfile stored with the project, so it can be reviewed, versioned and reused, and it supports multiple stages and conditions.
What is a Jenkinsfile?
A Jenkinsfile is a text file, usually kept in the repository root, that defines a pipeline using declarative or scripted Groovy syntax. Jenkins reads it on each run, so pipeline changes go through the same version control and review as application code.
Where Setup fits in the Jenkins roadmap
Setup belongs to the Getting Started stage (beginner level). Install and first pipeline.
Back to the full Jenkins roadmap