Orqestria Download
← Back to the catalog

Skill · Version 1.0.0

CI/CD and release pipelines

Structures verification and deployment around immutable release artifacts, coordinated state changes and evidence of the active version.

cicd-release-engineering

See how it helps

When is it useful?

Use when deployment needs a traceable artifact and coordinated application, database and worker changes.

What does it help you do?

  • Orders frozen installation, checks, tests and build into bounded pipeline stages.
  • Promotes the same immutable artifact and serializes deployments per environment.
  • Connects running version evidence with migration, worker and recovery sequencing.

Try asking this

Design a release pipeline that queues overlapping deployments and exposes the active commit identifier. Start two releases close together and make the older build finish last. It must not overwrite the newer active revision or publish a different artifact.

Detailed documentation

Read the skill’s original instructions, examples and checks in their authored language.

Details…Show less

CI/CD & Release Engineering

Design pipelines so every commit goes through fast, deterministic verification, and every release promotes a single traced artifact through environments in a safe, repeatable order.

Pipeline Stage Architecture & Concurrency

Structure workflows into explicit stages with fail-fast ordering and concurrency protection:

  1. Fast Verification Stage (PR & Branch Push):
    • Run install (frozen lockfile) $\rightarrow$ lint + typecheck $\rightarrow$ unit/integration tests $\rightarrow$ build check.
    • Use CI concurrency groups:
      • On pull requests: cancel-in-progress: true keyed by workflow + PR/branch so superseded commits free runners immediately.
      • On deployments/releases: cancel-in-progress: false (queue or serialize per target environment) so an in-flight production rollout or migration is never killed mid-execution by a second merge!
  2. Build Once, Promote Everywhere:
    • Compile and package the release artifact once from the verified commit SHA, attach provenance metadata (git_sha, version, build_timestamp), and promote that exact immutable image digest (@sha256:...) or signed archive from staging to production—never rebuild from source per environment.
  3. Explicit Job Timeouts:
    • Set an explicit timeout-minutes on every CI job so hung network calls or deadlocked tests fail predictably instead of burning runner quota for 6 hours.

Safe Deployment Ordering: App, Migrations & Workers

Rolling out code that changes database schemas, queue payloads, or API contracts requires backward-compatible sequencing (Expand and Contract):

Step Action Why Order Matters
1. Pre-Deploy (Expand Schema) Apply additive, backward-compatible migrations (ADD COLUMN NULL, new table, CREATE INDEX CONCURRENTLY) Old running app instances and workers continue functioning without errors while the migration runs.
2. Roll Out New App & Workers Deploy new application instances and drain/restart queue workers once health/readiness checks pass New code starts writing to new columns/formats while still tolerating in-flight old queue jobs.
3. Post-Deploy Verification Run smoke checks against critical user/system paths and monitor error rate & latency Confirms the new version serves traffic cleanly before removing old instances or columns.
4. Contract (Later Release) Drop deprecated columns or old job handlers in a subsequent release after all old instances and queued payloads have drained Prevents column does not exist crashes during rolling deploys or rollbacks.

Release Versioning & Traceability

  • Expose the running build's version and commit_sha via a lightweight health/version endpoint or response header and inject it into telemetry (service.version) so any error in logs or monitoring maps immediately to the exact commit.
  • Never rely on a mutable tag like :latest as the sole identifier of a production release.

Included files 1

  • SKILL.md

About this skill package

cicd-release-engineering

cicd-release-engineering: Make releases reproducible with clear build pipelines, infrastructure configuration, monitoring and recovery checks.

Details…Show less

cicd-release-engineering

cicd-release-engineering: Make releases reproducible with clear build pipelines, infrastructure configuration, monitoring and recovery checks.

Includes the complete skill and its supporting files (1 files). The exact authored scope is preserved below.

Original skill description (source language)

Use when designing, implementing, or debugging CI/CD pipelines, concurrency controls, deployment ordering, database migration rollout coordination, or versioned release workflows.

Install the skill, review its source and trust settings, then enable it for the relevant project or agent.

Requirements

  • Orqestria installed on your computer.