Chapter 10: Jenkins Introduction
10.1 Why Jenkins still appears in interviews
GitHub Actions is convenient when GitHub is the centre of gravity. Many enterprises still run Jenkins: long history, huge plugin ecosystem, and pipelines that must reach servers deep inside private networks.
Why it matters for an Instagram-style badge API : if you join a team that already has Jenkins shared libraries and agents next to on-prem servers (servers), you should read a Jenkinsfile without panic — even if your personal projects use Actions.
| GitHub Actions | Jenkins |
|---|---|
YAML in .github/workflows |
Often Jenkinsfile in repo (Pipeline-as-code) |
| GitHub-hosted runners common | You often run controller + agents yourself |
| Tight GitHub PR UI | Classic UI + Blue Ocean / others |
| Secrets in GitHub | Credentials plugin / external vaults |
Neither tool "wins" forever. Interviews reward: same CI stages, different engines.
Ravindra Bagale's Tip
"Jenkins outdated" mhanun skip karu nako. Job description madhe Jenkins + Docker ajun common aahe. Concepts overlap — syntax vegla. Lakshat theva!