Overview

This document explains the Continuous Deployment (CD) process at DEVOPS. The CD pipeline is integrated with CI in the same Jenkinsfile but operates differently based on branch types. Pull request branches only run tests, while regular branches automatically deploy to Rancher environments after successful testing.

How the Pipeline Works

The Jenkins pipeline follows a simple rule to determine whether to deploy:

Regular Branches (feature_main, develop, main, etc.):

• Run all tests and quality checks
• Build and tag Docker image
• Push image to registry
• Deploy to appropriate Rancher environment
• Send notifications to Slack

Rancher Environments

We maintain two Rancher clusters with different namespaces for various stages of development:

Rancher v2 Dev Environment

URL: https://rancher-v2-dev.DEVOPS.tech/dashboard/home

Namespaces:

• **DEVOPS-dev**:
  • Development namespace for feature branches and active development. Developers can deploy and test their features here.
• **DEVOPS-test**:
  • QA namespace for testing release candidates. QA team validates features before production release.

Rancher ChatPB Environment

URL: https://rancher-chatpb-dev.DEVOPS.tech:4431/

Namespaces:

• **chatpb-deployment**:
  • Production namespace for stable releases. Only accessible by admin team with manual approval required.
• **chat-pb-feature-branch**:
  • Isolated environment for testing individual feature branches without affecting other developers.

Naming Conventions and Standards

Deployment Workload Naming

The system automatically generates workload names using this pattern: