Builds and deployments
Follow immutable builds, health-gated deployments, retries, redeploys, and rollbacks.
A build turns one source revision into an artifact. A deployment applies an artifact and runtime configuration to one service in one environment.
Follow a deployment
Select a service node and open Deployments. Status moves through the available build and runtime phases, such as queued, building, deploying, healthy, failed, or stopped.
Open a deployment to inspect:
- source revision and trigger;
- build or runtime class;
- start and completion timestamps;
- artifact identity when available;
- build output;
- runtime health; and
- normalized failure details.
Immutable artifacts
GitHub Actions and agent-prepared releases register complete, digest-pinned OCI artifact manifests. A mutable image tag or source commit by itself is not an accepted release identity.
The deployment target never calls the private runtime provider directly from GitHub. GitHub authenticates to Autodisc with OIDC, Autodisc verifies the repository and workflow identity, and the canonical deployment coordinator performs the runtime operation.
Redeploy
Redeploy when runtime configuration changed or you intentionally need a new deployment of the current source. A redeploy may rebuild source-based services. An immutable rollback should reuse the earlier artifact rather than rebuild it.
Failure recovery
- Open the failed deployment.
- Identify whether failure occurred during dependency installation, build, image pull, startup, routing, or health.
- Read the bounded output for the affected phase.
- Correct source, commands, variables, or networking.
- Create a new revision or redeploy.
A failed health gate must not silently replace the last healthy active release.
GitHub Actions
For Actions-managed repositories, the implemented API can bind an allowed workflow, exchange GitHub OIDC for a short-lived session, and register digest-pinned artifacts for a published Change Request revision.
The customer-facing create-deployment and follow-events endpoints are not implemented yet. Artifact registration must not be shown as deployment success. Apply the approved revision from the project workspace and verify its build, rollout, health, and application behavior.
See APIs and automation for the exact supported boundary.