Guides

Jenkins Pipeline for Beginners

By Ravindra Bagale, DevOps trainer · LinkedIn · Published: 30 September 2026 · Last updated: 30 September 2026

Read this guide in: English · मराठी · हिंदी

Why do we need a Jenkins Pipeline? Because there is a real problem between developers and operations when the company runs CI on its own server. Developers want automatic checks. Operations — the employee on the server side — often owns the Jenkins controller. A Jenkinsfile describes the same stages as code: checkout, run steps, fail early — then Build Now and read Console Output.

Friends, Jenkins is still common at Infosys-style clients. First see who owns the controller. Then the Declarative skeleton sticks.

Language: English · मराठी · हिंदी

Why do we need Jenkins Pipeline?

1. Many companies already have Jenkins for CI/CD.
2. Operations on the server side needs one place to see build history.
3. Pipeline-as-code stops “click the UI differently every Friday.”

Need a Jenkins you are allowed to use (lab VM/container). Do not scan servers you do not own. Basic Git. Compare: GitHub Actions.

What does operations have to do with Jenkins?

1. Operations often installs plugins, agents, and credentials on the controller.
2. Developers write the Jenkinsfile; both read Console Output when red.
3. Prefer Jenkinsfile in Git so reviews travel with the app.

What is the problem? Suppose we are…

Suppose we are building Instagram (like updates)

Suppose every profile change is “built” by whoever remembers the local script. Operations has no Jenkins history when production breaks.

Suppose we are working at Netflix and we are giving updates

Suppose high-frequency updates need the same stages every time. A Declarative pipeline is that checklist as code.

Suppose you are working in Infosys on a client project

Suppose the client’s operations team already runs Jenkins. Your job is a Pipeline job + Jenkinsfile they can audit — not a private laptop ritual.

How Jenkins answers that same fight

Declarative skeleton:

pipeline {
  agent any
  stages {
    stage('Checkout') {
      steps { checkout scm }
    }
    stage('Check') {
      steps { sh 'ls -la' }
    }
  }
}

Steps in Jenkins UI:

1. Open Jenkins and sign in (lab URL you administer).
2. New Item → name like client-ci → Pipeline → OK.
3. Definition: Pipeline script (paste skeleton) or Pipeline script from SCM (real projects).
4. Build Now → open build → Console Output.
5. Add a failing check once (sh 'test -f README.md') and learn to read the red log.
6. Store the Jenkinsfile next to application code for review history.

What you should see

1. Build history blue/green (success) or red (failure).
2. Console Output prints each sh command and exit code.
3. Stage view lists Checkout → Check in order.

Common errors — story pain then fix

Samajla ka? Why Jenkins = company-owned CI where operations and developers share Console Output; Instagram / Netflix / Infosys “suppose”; Jenkinsfile = pipeline as code. Build Now, read the console.