#1 India's Top IT Training Institute
×

About Uncodemy

Know more about who we are and what we stand for.

About Us

About Us

Discover our mission to equip individuals with essential IT skills and industry expertise.

Read More →
UnCodeMy Gallery

UnCodeMy Gallery

Explore highlights from our IT training sessions and success stories.

Read More →
Mentors

Mentors

Meet the industry experts who train and guide you through your course.

Read More →
Free Resources

Free Resources

Free tutorials, interview questions, tools and calculators to help you learn.

Explore →
×

Free Resources

Learn, practice and plan your career — bilkul free.

Tutorials

Tutorials

Step-by-step written tutorials to learn any technology at your own pace.

Read More →
Free Counselling

Free Counselling

Book a free video counselling session and pick the right course for you.

Read More →
Online Compiler

Online Compiler

Write, run and test your code online — no setup required.

Read More →
Jenkins · Topic 2 of 15

What is Jenkins?

By Uncodemy Editorial Team · Updated 16 Nov 2026

Jenkins in one paragraph

Jenkins is a free, open-source automation server. You tell it what to do when something happens, for example "when someone pushes to the main branch, pull the code, run the tests, build the package and deploy it to the test server", and Jenkins does that every time, on its own, and shows you the result. That automated flow is CI/CD (continuous integration and continuous delivery/deployment); the idea itself is explained in Introduction to CI/CD. Jenkins is written in Java, runs on Linux, Windows and macOS, and serves its web interface on port 8080 by default.

Where it came from

Jenkins began as Hudson, a project started by Kohsuke Kawaguchi at Sun Microsystems in the mid-2000s. After Oracle bought Sun, a dispute over the Hudson name led the community to rename the project Jenkins in 2011. It has been community-run and open source throughout; it was never a paid product.

The parts you will meet

PartWhat it is
ControllerThe main Jenkins server: web UI, configuration, scheduling. Older guides call it "master".
AgentA machine or container that actually runs builds. Older guides call it "slave". See Jenkins controller and agent architecture.
ExecutorOne build slot on a node. A node with two executors can run two builds at once.
Job / itemA configured task: Freestyle project, Pipeline, or Multibranch Pipeline.
BuildOne run of a job, numbered #1, #2, ... with its own console log.
PluginAn add-on. Git, Pipeline, credentials, email and most other features come from plugins.
JenkinsfileA text file in your repository that describes the pipeline as code.

What a Jenkins job looks like today

Modern teams keep the pipeline in a Jenkinsfile next to the code, so changes to the build are reviewed like any other change. A small Java project might use:

pipeline {
    agent any
    stages {
        stage('Checkout') {
            steps { checkout scm }
        }
        stage('Test') {
            steps { sh 'mvn -B test' }
        }
        stage('Package') {
            steps { sh 'mvn -B -DskipTests package' }
        }
    }
    post {
        always { junit 'target/surefire-reports/*.xml' }
    }
}

In the UI you would create it like this (described as screens):

  1. Dashboard → New Item: type a name, pick Pipeline, click OK.
  2. Pipeline section → Definition: choose "Pipeline script from SCM", select Git, paste the repository URL and pick credentials.
  3. Script Path: leave Jenkinsfile. Save.
  4. Build Now: the build appears under Build History. Open it and click Console Output to see each command and its result.

The syntax is covered step by step in Jenkins Pipeline: concepts and types, and connecting a repository in creating a Jenkins job with Git.

What Jenkins is good at, and what it costs you

Errors beginners hit first

Next topic: installing Jenkins.

Master Jenkins & DevOps with Uncodemy

Hands-on live training, real projects and Dedicated Placement Support — become job-ready in DevOps.

Enroll in DevOps Training →