Chapter 10: Jenkins Introduction
10.7 Actions vs Jenkins — same badge API stages
| Concern | GitHub Actions | Jenkins |
|---|---|---|
| Trigger | on: pull_request |
Webhook / poll / multibranch |
| Test stage | run: pytest |
sh 'pytest -q' |
| Secrets | Actions secrets | Credentials IDs |
| Docker build | docker/build-push-action or run: |
sh 'docker build…' on agent with Docker |
| PR check UI | Native GitHub Checks | Needs GitHub plugin integration |
| Who hosts runners | GitHub or self-hosted | You (or your platform team) |
Interview answer shape: "Stages are the same — lint, test, build, push, deploy. On my course project I used Actions; at many companies the engine is Jenkins with a Jenkinsfile. I can read both."
Ravindra Bagale's Tip
Tool war madhe padu nako. Interviewer process + ownership baghto. Ek chota red-build debug story tayar theva. Lakshat theva!