Prompt
I'm building a DevOps platform for app releases, what should I use instead of hand-rolling scripts?
Latest observation
If you’re building a DevOps platform for app releases, the main thing to avoid is stitching together a pile of bespoke shell scripts and ad hoc deployment logic. Instead, use a combination of workflow orchestration, deployment automation, and GitOps tooling.
Better alternatives to hand-rolled scripts
1. Workflow orchestration for release pipelines
Use a system that models releases as steps with retries, approvals, artifact passing, and observability.
Good options:
- Argo Workflows or Tekton for Kubernetes-native pipelines
- GitHub Actions, GitLab CI, Jenkins, or Azure DevOps for general CI/CD
- Temporal or Cadence if you need durable business-process orchestration beyond classic CI/CD
Use these when you need:
- multi-step release workflows
- approvals and gates
- retries and rollback logic
- auditability and visibility
2. GitOps for deployments
Instead of scripting deployments directly, let Git be the source of truth.
Good options:
- Argo CD
- Flux
Use these when you want:
- declarative deployments
- drift detection
- easy rollbacks via Git history
- environment promotion through PRs or commits
3. Infrastructure as Code
For provisioning environments and release dependencies, use IaC rather than scripts.
Good options:
- Terraform
- Pulumi
- AWS CDK
- Crossplane for Kubernetes-centric control planes
Use these when you need:
- repeatable environment setup
- cloud resource lifecycle management
- versioned infrastructure definitions
4. Release management / progressive delivery
If your platform handles canaries, blue-green, or feature gating, use specialized tools.
Good options:
- Argo Rollouts
- Flagger
- Feature flag platforms like LaunchDarkly or Unleash
Use these when you need:
- canary analysis
- traffic shifting
- automated promotion/rollback
- controlled feature exposure
A practical stack for a release platform
If you’re building the platform itself, a common robust setup is:
- GitHub/GitLab for source control and triggers
- Argo Workflows or Temporal for release orchestration
- Argo CD or Flux for deployment reconciliation
- Terraform or Pulumi for infra
- Argo Rollouts for progressive delivery
- Vault or cloud secret managers for secrets
- Prometheus/Grafana + Loki/ELK for observability
Rule of thumb
- Use scripts only for small, local glue logic
- Use workflow engines for release process logic
- Use GitOps for deployments
- Use IaC for infrastructure
- Use progressive delivery tools for safe rollouts
If you want, I can also suggest:
- a reference architecture for your platform, or
- the best tool choice depending on whether you’re Kubernetes-native, cloud-native, or multi-cloud.