How do you integrate Git with Jenkins, GitLab CI, or GitHub Actions?

Short answer: Integration means connecting your Git repository to your CI/CD system so every push, pull request, or tag triggers an automated build, test, and deploy pipeline.

Explain a bit more

✅ Jenkins Integration Install the Git plugin in Jenkins. Create a new pipeline job and link it to your Git repository: pipeline { agent any stages { stage('Checkout') { steps { git branch: 'main', url: } } stage('Build') { steps { sh 'npm install' sh 'npm test' }

Example code

}
}
} ● Jenkins polls Git or listens for webhooks to trigger builds automatically. ✅ GitLab CI/CD GitLab CI is built-in — simply create .gitlab-ci.yml: stages: test deploy test: script: npm install npm test deploy: script: ./deploy.sh only: main Every push triggers this pipeline automatically. ✅ GitHub Actions GitHub has its own YAML-based workflows: name: Node CI on: [push, pull_request] jobs: build: runs-on: ubuntu-latest steps: uses: actions/checkout@v4 run: npm ci run: npm test It runs directly in GitHub without needing extra setup. Real-world example: Your team pushes code to GitHub → GitHub Actions automatically runs tests → Jenkins (or GitLab CI) deploys to a staging environment → Approval required for production deploy.

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.