DevOps CI/CD Pipelines Course in Mohali: Tools & Technologies Covered

This page sets out the tools and technologies covered in the DevOps CI/CD Pipelines course in Mohali at techcadd. A CI/CD pipeline automates how code moves from a commit to a running application, and the course teaches you how each tool in that chain fits together through practical labs.

How a CI/CD Pipeline Fits Together

Continuous integration (CI) means every change is built and tested automatically. Continuous delivery and deployment (CD) means tested changes can be released to environments in a repeatable way. A typical pipeline moves through source control, build, test, code quality and security checks, packaging into an artefact or container image, and deployment, with monitoring afterwards. Each stage uses specific tools, listed below.

Source Control Tools

Git

Branching, merging, tags and commit history that trigger pipeline runs.

GitHub and GitLab

Pull or merge requests, branch protection, required status checks and webhooks that start pipelines.

CI/CD Servers and Platforms

Jenkins

Declarative Jenkinsfiles, agents, multibranch pipelines, shared libraries and plugins.

GitHub Actions

Workflow YAML, runners, matrix builds, secrets and reusable workflows.

GitLab CI

The .gitlab-ci.yml structure, stages, jobs, runners and artefacts, introduced for comparison.

Build, Test and Quality Tools

• Maven and Gradle: building and testing Java applications.

• npm: installing dependencies, building and testing Node.js projects.

• JUnit and pytest: unit test frameworks whose reports are published in pipelines.

• SonarQube: code quality and static analysis with quality gates.

• Trivy: scanning container images for known vulnerabilities.

Packaging and Artefact Tools

• Docker: writing Dockerfiles, multi-stage builds and tagging images.

• Container registries: Docker Hub, Amazon ECR or similar registries for storing images.

• Nexus or JFrog Artifactory: storing versioned build artefacts such as JAR files.

Deployment and Infrastructure Tools

• Kubernetes and kubectl: deployments, services, rolling updates and rollbacks.

• Helm: packaging and versioning Kubernetes releases.

• Argo CD: an introduction to GitOps-style continuous delivery.

• Terraform: provisioning infrastructure from pipelines.

• Ansible: configuring servers during deployment.

• AWS: EC2, EKS and related services as deployment targets.

Monitoring After Deployment

Pipelines do not end at deployment. The course introduces Prometheus and Grafana to watch application health after a release, and explains how monitoring results can inform rollbacks.

Projects That Use These Tools Together

• A Jenkins pipeline that builds a Java app with Maven, runs tests, checks quality with SonarQube and archives the artefact

• A GitHub Actions workflow that builds a Docker image, scans it with Trivy and pushes it to a registry

• A deployment to Kubernetes using Helm with a rolling update and rollback

• An infrastructure pipeline that runs Terraform plan on pull requests

Course Overview, Eligibility and Batches

The course suits developers, system administrators, QA engineers and graduates with basic Linux and Git knowledge. Duration and fees vary by batch format; contact the techcadd Mohali team for the current fee structure and batch timings. Career outcomes in DevOps and release engineering roles depend on effort, skills and market conditions.

Frequently Asked Questions

Which CI/CD tool is the main focus?

Jenkins and GitHub Actions are the main tools, with GitLab CI introduced for comparison.

Is Docker covered in the CI/CD course?

Yes, building, scanning and pushing Docker images is a core part of the pipeline labs.

Will I deploy to Kubernetes?

Yes, deployments to Kubernetes with kubectl and Helm are included, with an introduction to Argo CD.

Do I need to know all these tools before joining?

No. Basic Linux and Git knowledge is enough; the tools are taught during the course.

Are security tools part of the pipeline?

Yes, SonarQube and Trivy are used for quality and vulnerability checks.

Can the tool list change?

The core tools stay the same, but versions and some supporting tools may be updated. Confirm the current list with the team.

Enquire About the CI/CD Pipelines Course at techcadd

Want to see the full tool list for the next batch? Contact techcadd Mohali to ask about the CI/CD course.