Description

A lean, battle-tested CI/CD foundation that runs your existing tests on every pull request, builds artifacts or images, optionally deploys to staging previews, and safely deploys to production when merged to main with approvals.

Overview

Automated CI/CD pipelines with GitHub Actions
Test automation for Node.js and Python projects
Optional preview deploys for pull requests
Production deploys gated by environment approval
Light script review and setup
DevOps assessment and future roadmap

Included Deliverables

1) CI/CD Workflows (GitHub Actions)

CI Workflow (ci.yml): Runs on pull requests, installs dependencies, executes tests, and builds Docker images if a Dockerfile exists. Supports optional staging preview on labeled pull requests.
Deploy Workflow (deploy.yml): Runs on merge to main or manual trigger, builds and pushes images, and deploys to production using GitHub environments with approval.

2) Scripts and Glue

scripts/deploy.sh: Cloud-agnostic deployment entry point for staging and production.
scripts/healthcheck.sh: Simple HTTP 200 probe used after deployment.
Includes a short script review to align with your environment.

3) Assessments

Includes a CI/CD and DevOps assessment checklist that evaluates your current branching, testing, release, and security posture.

4) Future DevOps Roadmap

Includes a 30/60/90+ day roadmap to guide you toward Infrastructure as Code, observability, blue/green deploys, scanning, and rollback strategies.

5) GitHub Integration

All actions are committed directly to your repository. No external tools required. Uses GitHub environments for staging and production, and repository secrets for configuration.

Safety and Workflow

Environment approvals required for production
Healthcheck verification blocks bad deploys
Prevents overlapping production runs
Clear promotion path from test to production

Required Setup

Create two environments in GitHub: staging and production
Add required reviewers for production
Configure repository secrets:
- REGISTRY, REGISTRY_USERNAME, REGISTRY_PASSWORD
- CLOUD_PROVIDER (aws, gcp, azure, none)
- STAGING_DEPLOY_SSH_KEY, PROD_DEPLOY_SSH_KEY (if needed)
- KUBE_CONFIG_BASE64 (for Kubernetes)
- Cloud credentials such as AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, or GCP_SA_KEY
- App secrets like DATABASE_URL, API_URL, HEALTHCHECK_URL

Acceptance Criteria

Pull requests automatically run tests and report results
Pull requests labeled “preview” deploy to staging
Merge to main builds and deploys to production after approval
Failed tests or failed healthchecks block deployment

Deliverables and Handoff

Committed workflows, scripts, and documentation in your repo
Completed assessment report
Customized deploy.sh aligned with your environment
Short runbook explaining ongoing CI/CD management

Post-Starter Add-Ons

Terraform or Helm Infrastructure as Code
Blue/Green or Canary deployment setup
Code scanning and dependency policies
Observability integration (logs, metrics, traces)
Cost and performance monitoring

Included: 3-Month Certified Break/Fix by Kimbodo DevOps for ongoing CI/CD support and issue resolution.

It provides an automated CI/CD foundation, a forward roadmap, and confidence in every release without the expense of full-scale DevOps management.

Kimbodo DevOps CI/CD Starter