1
Source and branch policy
Trigger on pull requests and protected GitHub branches. Require review before production deploys.
Deployment workflow builder
CI/CD Pipeline Template Generator
A CI/CD pipeline template generator creates a structured release workflow with build, test, security scan, artifact, deployment, verification, and rollback stages. Use this free tool to draft a deployment pipeline your team can adapt to any CI provider.
Pipeline inputs
Choose a stack and release path to generate a vendor-neutral deployment pipeline.
Generated plan
Customer Portal CI/CD pipeline
Next.js web app release flow for Kubernetes, with build-once promotion and explicit deployment gates.
2
Install and cache dependencies
Use npm with a lockfile cache keyed by the lockfile hash.
3
Quality gates
Run linting, type checks, and npm test before building artifacts.
4
Build artifact
Run npm run build and publish one immutable artifact for downstream environments.
5
Security scan
Run dependency audit, secret scanning, and container/image scanning before deployment approval.
6
Preview environment
Deploy pull requests to an isolated preview URL and attach smoke-test results to the PR.
7
Staged deploy
Promote the same artifact through Preview, Staging, Production on Kubernetes.
8
Rollback and verification
Keep the previous artifact available, verify health checks after rollout, and document the rollback command.
Template outline
# CI/CD pipeline template for Customer Portal
name: customer-portal-pipeline
on:
pull_request:
push:
branches: [main]
stages:
- validate
- test
- build
- security
- preview
- deploy-preview
- deploy-staging
- deploy-production
- verify
jobs:
validate:
runs-on: ubuntu-latest
steps:
- checkout
- setup npm cache
- install dependencies from lockfile
- lint and typecheck
test:
runs-on: ubuntu-latest
needs: validate
steps:
- run: npm test
build:
runs-on: ubuntu-latest
needs: test
steps:
- run: npm run build
- publish immutable artifact
security:
runs-on: ubuntu-latest
needs: build
steps:
- dependency audit
- secret scan
- image or artifact scan
preview:
runs-on: ubuntu-latest
needs: build
if: pull_request
steps:
- deploy preview environment
- run smoke tests
- comment preview URL on PR
deploy-preview:
runs-on: ubuntu-latest
needs: security
environment: preview
steps:
- deploy artifact to Kubernetes
- run health check
- record release evidence
deploy-staging:
runs-on: ubuntu-latest
needs: deploy-preview
environment: staging
steps:
- deploy artifact to Kubernetes
- run health check
- record release evidence
deploy-production:
runs-on: ubuntu-latest
needs: deploy-staging
environment: production
steps:
- deploy artifact to Kubernetes
- run health check
- record release evidence
verify:
runs-on: ubuntu-latest
needs: deploy-production
steps:
- verify production URL
- keep previous artifact rollback-ready
- notify owners with release summary
What makes a reliable CI/CD pipeline?
Reliable pipelines separate validation from release, build one immutable artifact, and promote that artifact through each environment instead of rebuilding at every step. That keeps test evidence connected to the exact code that reaches users.
The template also includes operational checks teams often skip early: ownership, security gates, environment approvals, smoke tests, deployment evidence, and a rollback path.
Frequently asked questions
What is a CI/CD pipeline template?
A CI/CD pipeline template is a reusable release workflow that defines build, test, security, artifact, deployment, verification, and rollback stages.
Should CI and CD be in the same pipeline?
They can be in the same workflow when deploy jobs have clear environment gates. Many teams use one build artifact, then promote it through staging and production.
What should a deployment pipeline include?
A deployment pipeline should include branch policy, dependency install, tests, build artifacts, security checks, environment approvals, smoke tests, and rollback instructions.
How do you avoid rebuilding for every environment?
Build one immutable artifact after tests pass, store it with a version or digest, and deploy that same artifact to each environment.
Is the generated pipeline tied to GitHub Actions?
No. The output is vendor-neutral, so you can adapt it to GitHub Actions, GitLab CI, Azure Pipelines, CircleCI, Buildkite, or another CI/CD system.
Related tools
Turn release work into portfolio proof
NitroBuilds helps developers show shipped projects, production links, stack choices, screenshots, and release evidence in one public portfolio.
Add a project