CI/CD & Deployment
Complete CI/CD ecosystem with GitHub Actions workflows and deployment automation
Our CI/CD infrastructure provides comprehensive automation for building, testing, and deploying applications across multiple technology stacks. We support two distinct workflow architectures and provide detailed deployment orchestration with environment-specific behaviors.
New to CI/CD?
CI/CD in 60 Seconds
CI/CD stands for Continuous Integration/Continuous Deployment. Think of it as an automated assembly line for your code:
1. You write code and push it to GitHub
2. CI (Continuous Integration) automatically builds and tests your code
3. CD (Continuous Deployment) automatically deploys working code to servers
4. Users get your features without manual intervention
Key Terms You'll See
Pipeline - The automated sequence of build → test → deploy
Workflow - A GitHub Actions file that defines your pipeline
Tag Cutting - Creating a release version (like v1.2.3) for deployment
GitOps - Using Git as the source of truth for deployments
ArgoCD - Tool that watches Git and deploys changes automatically
Environment - Where your code runs (Development, Staging, Production)
GitHub Actions Architecture Flows
Interactive comparison of our CI/CD pipeline architectures
NX-Based Monorepo CI/CD Flow
Archetype-based pipeline with multi-app support and dependency graph optimization
Code CommitMAIN
< 1sDeveloper pushes to main branch
Code PullMAIN
10-30sGitHub Actions pulls latest code
NX Build ProcessMAIN
2-5mArchetype-based build with dependency graph
Parallel TestingPARALLELMAIN
5-15mTests across libraries and apps simultaneously
Archive ResultsMAIN
30s-2mStore test results and artifacts in GitHub
Docker BuildMAIN
3-8mBuild container images (if tests pass)
Artifactory PushMAIN
1-3mTag and push images to registry with integrated versioning
Auto-Deploy to DevDEPLOY
30s-2mAutomatic deployment to development environment
Deploy to Staging/ProdDEPLOY
2-8mCoordinated deployment to higher environments
Interactive Guide
Click on any step in the flow diagrams to see detailed information about that stage of the pipeline. Orange steps highlight deployment operations, green steps indicate parallel execution, purple indicates feature branch operations, and blue indicates main branch operations.
Key Difference: Feature Branch CI
The new standalone architecture runs full CI/CD on feature branches for early validation, then follows a similar flow to the old process on main branch merge, but with tag cutting as a separate manual action for controlled releases.
DEPLOYMENT WORKFLOWS - The Critical Final Step
Your code is built and tested - now what?
Deployment workflows handle the critical transition from built artifacts to running applications. This is where your code becomes a live service that users can access.
Development
Automatic deployment on every commit
Staging
Manual tag cutting with team approval
Production
Controlled releases with full monitoring
Complete guide to tag cutting, environment promotion, and GitOps integration
Workflow Architecture
Recommended: Standalone Workflow (The Future)
All new projects should use the Standalone Workflow. It's simpler, more flexible, and designed for modern development practices.
| Standalone Benefits | Why It Matters |
|---|---|
| Individual repositories | Each service evolves independently |
| Feature branch CI/CD | Immediate feedback on every change |
| Simplified pipelines | Easier to understand and maintain |
| Faster builds | 2-8 minutes consistently |
| Easy onboarding | New developers can contribute quickly |
| Highly configurable | Adapt to your specific needs |
Legacy: NX-Based Workflow (Existing Projects Only)
The NX-based workflow is maintained for existing monorepo projects but is not recommended for new development. Consider migrating to Standalone when feasible.
| NX Characteristics | Current Reality |
|---|---|
| Monorepo structure | Complex dependency management |
| Limited feature branch CI | Slower feedback cycles |
| 5-20 minute builds | Variable performance |
| Steep learning curve | Harder for new team members |
| Archetype constraints | Less flexibility |
Documentation Sections
**ESSENTIAL GUIDE** - Environment-specific deployment processes, tag cutting, release management, and GitOps integration. Master the critical final step of your CI/CD pipeline.
Modern CI/CD with feature branch support, fast builds, and simplified pipelines. The recommended approach for all new projects.
Monorepo workflow for existing projects. Maintained for compatibility but not recommended for new development.
Browse our comprehensive library of 17+ reusable GitHub Actions organized by technology stack.
Complete workflow templates and real-world examples for common development scenarios.
Resolve common issues, optimize performance, and follow CI/CD best practices.
Quick Start
Choose your path based on your project type:
For New Projects (Recommended)
- Start with Standalone Workflow - Modern, flexible CI/CD
- Browse Actions Library - Ready-to-use automation components
- Copy Workflow Examples - Templates for your technology stack
- Master Deployment Workflows - The critical final step
For Existing NX Projects (Legacy)
- Continue with NX-Based Workflow - Maintain existing monorepos
- Plan migration strategy to Standalone when feasible
Related Resources
- Platform Infrastructure - ArgoCD, Kubernetes, and infrastructure management
- Security Guidelines - Secure CI/CD practices and compliance
- Monitoring & Observability - Pipeline monitoring and alerting