Jenkins Dashboard explanation
Haan. CI/CD ka almost saara practical kaam isi Jenkins dashboard se hota hai.
Jo screen tum dikha rahe ho, ye job ka Configure page hai. Ab isko calmly, section by section samjhte hain.
Big picture pehle samjho
Jenkins ka main dashboard hota hai jahan saare jobs dikhte hain
Har job ke andar:
Configure
Build Now
Console Output
Workspace
CI/CD ka logic job ke Configure page me hi define hota hai.
Ab tumhare screen ke sections
1. General
Ye job ki basic identity aur behaviour define karta hai.
Description
Sirf human-readable note.
Example:
This job builds and tests my application
Discard old builds
Old build history automatically delete
Disk space bachane ke liye important
Real life me always use hota hai.
GitHub project
GitHub repo ka URL
Sirf linking ke liye (logic yahan nahi hota)
This project is parameterized
Build time pe input dena
Example: branch name, environment (dev/prod)
Ye thoda advanced but very useful feature hai.
2. Source Code Management (SCM)
Yahin se CI start hota hai.
Yahan tum batate ho:
Code kahan se aayega
Git
GitHub
GitLab
Repo URL
Branch (main, dev, etc.)
Credentials
Simple flow:
Jenkins → Git repo → code pull
Agar yahan kuch nahi hai, to Jenkins ke paas build karne ko code nahi hota.
3. Triggers
Ye section batata hai build kab start ho.
Common options:
Manually: Build Now
Poll SCM: har X minute me check
GitHub webhook: code push hote hi build
CI ka heart yahi hai.
Example:
Developer ne code push kiya → Jenkins auto build start
4. Environment
Yahan tum environment variables set karte ho.
Example:
JAVA_HOME=/usr/lib/jvm/java-17APP_ENV=dev
Ye variables:
Build steps
Shell scripts
me use hote hain.
5. Build Steps (MOST IMPORTANT)
Yahin actual kaam hota hai.
Example:
Execute shell
Maven build
Gradle
npm install
Docker build
Tum jo pehle whoami run kar rahe the, wo yahin tha.
CI ka matlab:
Code aaya → build → test
Sab yahin hota hai.
6. Post-build Actions
Build ke baad kya ho?
Examples:
Email bhejna
Artifact archive
Deploy to server
Trigger next job
CD ka major part yahan aata hai.
Simple CI/CD flow using this page
Source Code Management -> Code pullTriggers -> Kab build hoBuild Steps -> Build + TestPost-build Actions -> Deploy / Notify
Important clarity
Ye job-level dashboard hai
Jenkins ka global dashboard alag hota hai
CI/CD logic job ke Configure page me define hota hai
Interview-ready line
“In Jenkins, CI/CD pipelines are configured at the job level using SCM, triggers, build steps, and post-build actions.”
One-line summary
Haan, CI/CD ka practical kaam isi dashboard se hota hai.
Bas har section ka role samajhna zaroori hai.
Agar chaho next:
1. Source Code Management (SCM)
None
Jenkins ke paas koi code repo nahi
Tum jo bhi command likhoge, wahi run hogi
Practice / basic testing ke liye use hota hai
Git
Jenkins GitHub/GitLab se code pull karega
Real CI yahin se start hota hai
👉 CI/CD seekh rahe ho to Git use karna hi padega
2. Triggers (Build kab start ho)
Trigger builds remotely
API ya script se build start
Advanced use case
Build after other projects
Ek job ke baad dusri job auto run
Pipeline type flow
Build periodically
Time ke hisaab se run
Cron job jaisa
GitHub hook trigger
GitHub pe code push hua
Jenkins turant build kare
Best & fastest CI
Poll SCM
Jenkins baar-baar repo check kare
Push hua ya nahi
Webhook na ho to use karte hain
Tumhare liye best combo (abhi)
SCM → Git
Trigger → GitHub hook trigger
Isse flow banega:
Code push → Jenkins build auto
One-line summary
SCM = code kahan se aayega
Triggers = build kab chalega
Environment section ka matlab
Build kis condition aur kis setup me chalegi
Har option ka simple meaning
Delete workspace before build starts
Purana code delete
Fresh build start
Bugs avoid karne ke liye useful
Use secret text(s) or file(s)
Password, token, SSH key
Secure way me use karne ke liye
Example: GitHub token
Provide Configuration files
Config files inject karni ho
Example:
settings.xml,.env
Add timestamps to the Console Output
Logs ke saath time show
Debugging easy ho jati hai
Provide Node & npm bin/folder to PATH
NodeJS project ke liye
Jenkins ko
nodeaurnpmmil jata hai
Terminate a build if it’s stuck
Build hang ho jaye to auto stop
Server resources save hote hain
With Ant
Java + Ant build ke liye
Agar Ant use nahi kar rahe, ignore
Tumhe abhi kya use karna chahiye
Beginner ke liye:
❌ Sab chhod sakte ho
✅ Optional: Add timestamps
Jab project real hoga tab:
Secrets
Config files
Workspace cleanup
One-line summary
Environment section = build ka setup box.
Abhi zaroori nahi, but real projects me kaafi useful.
Post-build Actions ka matlab
Build complete hone ke baad kya karna hai
Build success ho ya fail, uske baad jo kaam hoga wo yahan set hota hai.
Common post-build actions (simple)
Archive the artifacts
Build ke output ko save karta hai
Example:
.jar,.war,.zipDownload ke liye future me kaam aata hai
Send notification
Email / Slack alert
Build success ya fail ka message
Trigger another job
Ek job complete → doosri job start
CI → CD flow yahin se banta hai
Deploy
Build ke baad app server pe deploy
Example: copy files, restart service
Tum abhi kya use karo
Beginner stage me:
❌ Kuch add karna zaroori nahi
Build Steps sahi chal rahe hain, wahi kaafi hai
Real project me:
Artifact archive
Deployment
Notifications
One-line summary
Post-build Actions = build ke baad ka kaam.
CI yahin khatam hota hai, CD yahin se start hota hai.