DevOps / Gitlab Interview questions
What is the difference between GitLab CI/CD and Jenkins?
GitLab CI/CD is a native part of the GitLab platform, configured with a single .gitlab-ci.yml file per repository and tightly integrated with merge requests, environments, and the container registry. Jenkins is a standalone, general-purpose automation server that can integrate with any Git host, but requires separate setup and plugins to get equivalent functionality.
| GitLab CI/CD | Jenkins |
Configuration lives in code (.gitlab-ci.yml) per repo. | Configuration often lives in the Jenkins UI or a Jenkinsfile plus plugin config. |
| Native integration with MRs, registry, environments. | Integration with Git hosts happens through plugins. |
| Runners are GitLab's own agent software. | Uses "agents"/"nodes," a separate concept with its own setup. |
| Minimal plugin ecosystem needed for core features. | Heavily plugin-dependent; thousands of community plugins. |
Jenkins' strength is its long history and enormous plugin ecosystem, which lets it fit into almost any toolchain. GitLab's strength is that CI/CD, review, and deployment tracking are already wired together, so there's less integration work and fewer moving parts to maintain and secure.
GitLab CI/CD configuration is primarily defined:
A key strength commonly attributed to Jenkins is:
More Related questions...
