GitHub Actions

Won CI by already being where the code was.

What it is sold for

Running builds, tests and deployments on repository events.

Used to build this site

• GitHub Actionschecks
  Every gate runs with if: !cancelled(), because a job that stops at the first failure was hiding the checks behind it.
  Evidence: .github/workflows/

Named alongside

These entries mention each other by name. It is a weak relationship and it is the only one the catalogue can show without inventing something.

Named by:

• RunMyJob
  CI runners billed by real usage rather than idle time, compatible with GitLab and GitHub workflows.

Same shelf

The rest of ci, cd and infrastructure, alphabetically. Sharing a category is a filing decision, not a relationship.

• Abstra
  Automation for finance operations, built as workflows rather than as spreadsheets.
• Ansible
  Agentless configuration management over SSH, with playbooks in YAML and no daemon on the target.
• AWS Step Functions
  Orchestrates AWS services as a state machine, so retries and failure branches are configuration rather than code.
• Buildstash
  Artifact and release management for teams shipping binaries: mobile, desktop, games, XR and embedded.
• Camunda
  Process orchestration for long-running work that spans people, systems and now agents, with the model as the executable.
• CircleCI
  A hosted CI platform, one of the older ones, now marketing itself around validating machine-written changes.
• Datadog
  Metrics, logs, traces and a great deal more in one platform. The default answer for large-scale monitoring, and priced like it.
• DeployHQ
  Deploys from a git host to servers with build steps, zero-downtime releases and one-click rollback.

All 34 in ci, cd and infrastructure