CI/CD Pipelines

The CI/CD Pipeline tab within a deployment stage of a product feature gives you a real-time and historical view of how every technology in the stage is built and deployed. You can track progress step-by-step, open the underlying CI/CD job (Jenkins or GitHub Actions), and also monitor pipeline health analytics.

Working with the CI/CD Pipeline View

The CI/CD Pipeline view provides a visual and interactive way to track your build and deployment progress in real time. Each technology is represented as a horizontal sequence of predefined stages.

As soon as a CI pipeline starts, its live progress becomes visible on the CI/CD Pipeline tab. The continuous integration and deployment for each technology is represented as a virtual pipeline composed of multiple predefined stages (for example, Initialization, Build, Unit Tests, SonarQube Scan, and Deploy, among others).

On this screen, you can do the following:

Hover over a stage to see:

  • Stage name

  • Status (In Progress, Success, or Failed)

  • Run duration

For SonarQube Scan:

  • Hover over the stage to see a quick scan summary.

  • Click the scan link to open the detailed report in SonarQube.

  • Status pill (upper right of each pipeline): Instantly shows whether the pipeline succeeded, failed, or is still running.

  • Timestamps: View the exact last run date and time to confirm build recency.

  • Build Number & Commit ID: Helps you correlate the deployment with a specific code change.

View Job: Opens the pipeline run directly in your configured CI/CD tool (Jenkins or GitHub Actions) for full logs, environment variables, and execution details. This is useful for:

  • Debugging failed stages

  • Reviewing deployment logs

  • Validating test output

Graph icon: Opens the Monitoring section for CI/CD pipeline analytics. From there, you can:

  • Identify recurring failure points

  • Track average build durations

  • Measure success rates over time

  • Spot performance regressions

CI/CD Pipeline Stages

The continuous integration and deployment for each technology is represented as a virtual pipeline composed of multiple predefined stages. These stages differ slightly depending on whether Jenkins or GitHub Actions is configured as the CI/CD tool.

Jenkins: Continuous Integration (CI) Stages

  1. Checkout SCM – Pulls the source code from the configured Git repository, checking out the appropriate branch or commit.

  2. Initialization – Prepares the build environment, loads configuration, and sets up required dependencies and environment variables.

  3. Build – Compiles and packages the application (for example, Maven, Gradle, npm).

  4. Unit Tests – Executes automated test cases to validate core functionality and prevent regressions.

  5. SonarQube Scan – Performs static code analysis for quality, coverage, and security vulnerabilities; enforces quality gates.

  6. Build Container Image – Creates a Docker/OCI image from the packaged application using the project’s Dockerfile.

  7. Publish Container Image – Pushes the image to the configured container registry (e.g., JFrog Artifactory, Docker Hub, Amazon ECR).

Jenkins: Continuous Deployment (CD) Stages

  1. Declarative: Checkout SCM – Retrieves the latest source code from the repository, including deployment descriptors (Helm charts, YAML).

  2. Initialization – Prepares the deployment environment with necessary configuration and cluster credentials.

  3. Deploy – Deploys the containerized application to the target Kubernetes or OpenShift cluster.

GitHub Actions: Continuous Integration (CI) Stages

  1. Set Up Job – Initializes the GitHub Actions runner and configures the environment.

  2. Checkout Code – Pulls the repository source code using the actions/checkout action.

  3. Initialization – Sets environment variables, loads secrets, and installs required tools and dependencies.

  4. Build – Compiles and prepares the application using the appropriate build system (Maven, Gradle, npm, etc.).

  5. Unit Test – Runs automated unit tests and generates reports.

  6. SonarQube Scan – Executes static analysis to check code quality and security issues, enforcing defined quality gates.

  7. Build Container Image – Builds a Docker/OCI image for deployment.

  8. Publish Container Image – Pushes the image to the configured container registry (JFrog, ECR, ACR, etc.).

  9. Push to Collector – Sends build metadata and results to Calibo Accelerate for pipeline monitoring.

  10. Post Checkout Code & Complete Job – Performs final cleanup and marks the CI job as complete.

GitHub Actions: Continuous Deployment (CD) Stages

  1. Set Up Job – Initializes the runner for deployment tasks.

  2. Checkout Code – Pulls repository code needed for deployment (e.g., manifests, Helm charts).

  3. Initialization – Installs dependencies, configures credentials, and prepares the deployment context.

  4. Configure Kubeconfig File – Sets up Kubernetes access to the target cluster.

  5. Deploy to Kubernetes – Applies manifests or Helm charts to deploy the workload to the cluster.

  6. Push to Collector – Sends deployment metrics and logs to Calibo Accelerate.

  7. Post Checkout Code – Cleans up the repository workspace after deployment.

  8. Complete Job – Finalizes the job and marks the deployment workflow as finished.

Related Topics Link IconRecommended Topics

What's next? Managing Source Code