Skip to main content

csph deployments builds fix

apply the fix a failed build offers (its branch or root folder), then start a build

🔧 Apply the fix a failed build offers, then start a build.

When ComputeSphere can tell what a failed build needs, the build offers one fix: a branch that exists in place of one that doesn't, or the folder your app moved to in place of a root folder that isn't in the repository. This command shows that fix, asks you, and applies it. The service's branch or root folder is changed and a new build starts, under the environment's deploy policy.

The fix is exactly the one the build offers: you can't change its branch or folder here. If anything it was worked out from changed since the build failed, nothing changes and the command says why.

It asks for confirmation first; --yes skips the question. Without a terminal (CI, a pipe, --no-input) it refuses to run unless --yes is given.

Usage​

csph deployments builds fix <build-id> [flags]

Options​

Command Specific​

--account <string>
account ID
--deployment <string>
deployment ID (required)
--wait
wait for the new build to succeed, fail or be canceled; progress goes to stderr

--wait-timeout <duration> (default "30m0s")

how long --wait waits before giving up (exit code 8: still pending)

-y, --yes

skip the confirmation prompt

Formatting​

For more information about formatting options, see Formatting.

--fields <strings>
output JSON with the specified fields
--jq <string>
filter JSON output with jq expression

-o, --output <string>

output format: [table|plain|csv|json|yaml]
--template <string>
format JSON using a Go template

Available Fields​

approved_at, approved_by, awaiting_approval_at, build_arg_source_counts, build_arg_sources, build_duration_seconds, built_at, cache_hit_ratio, canceled_at, commit_author, commit_message, commit_sha, created_at, declared_build_args, deployed_by, deployment_id, duration_seconds, environment_id, failure_message, failure_reason, finished_at, fix, git_ref, id, image_digest, image_signature, image_size_bytes, manifest, mode, object, phases, pipeline_tier, pre_deploy_command, promoted_from, reject_reason, rejected_at, rejected_by, service_id, source_kind, source_ref, started_at, status, trigger_source

Inherited​

--config <string>
config file (default is $HOME/.config/computesphere/configuration.yaml)
--debug
enable debug logging

-h, --help

show this help message

-i, --interactive

run interactively (prompts, pickers, table browser)
--log-level <string>
log level: [trace|debug|info|warn|error|fatal|panic|disabled||api]
--no-color
disable color output
--no-input
disable interactive mode

Examples​

# apply a failed build's fix (asks first)
> csph deployment builds fix <build-id> --deployment <deployment-id>

# apply it without asking, then wait for the new build
> csph deployment builds fix <build-id> --deployment <deployment-id> --yes --wait

See also​