BookNest is a public repository whose tests finish in seconds, so its pull-request checks stay in Actions, where GitHub put them. Jenkins 8,793 takes the half of the pipeline that must run near BookNest's infrastructure:
| Need | Better fit | Why |
|---|---|---|
| Test every pull request | GitHub Actions 29 | Free for public repositories, shown on the PR |
| Push the image to a local registry | Jenkins | GitHub 29 cannot reach the registry |
| Deploy to Kubernetes's cluster | Jenkins | Runs inside the network that can reach it |
The Jenkins pipeline built in this chapter runs the same npm 2,036 test and reports to GitHub as a commit status (Commit Status Checks), so both systems' results appear on each commit. The question worth asking is not "Jenkins or Actions" but "which steps must run where."