CorefinityCorefinityDocs
Open the Control PanelControl Panel
Deployments · 50 of 65

corestack_enterprise_deployments_list

CoreStack Enterprise deployments.

Scope readNo secrets returned
On this page

When to use it

List a CoreStack Enterprise environment's deployments, newest first: what ran, whether it worked, which commit it deployed and which deployment is live (is_current). Use corestack_enterprise_deployment_get for one deployment's state and what can be done with it now.

These tools are for CoreStack Enterprise environments only. A CoreStack or CoreCluster site's deployments are the corestack_deployment_* and corestack_deployments_* tools (by site_id): they answer the site's deployment settings and run the site's own rules, so they are separate tools. The same list is the public API's GET /api/environments/{environment}/deployments with limit, cursor or status.

Ask for it

Prompt
Using the Corefinity MCP server, call corestack_enterprise_deployments_list with enterprise_env_id 1530, status failed, limit 10. (CoreStack Enterprise deployments.) Tell me what it returned.

Inputs

cursorstring

The last answer's next_cursor, for the next page Up to 40 characters.

enterprise_env_idintegerRequired

The CoreStack Enterprise environment's id At least 1.

limitinteger

Items per page (25) 1 to 100.

statusstring

Only deployments in this status: scheduled, running, failed, succeeded, cancelled, pending (waiting to be deployed by hand), queued

scheduledrunningfailedsucceededcancelledpendingqueued

Each item: id, environment_id, name, status, git_commit, repository_id, pipeline_id, trigger (manual, api, webhook), rollback_of_deployment_id, attempt_id, is_current, created_at and error: why a failed deployment failed, the same line the public API's list gives (null unless it failed). A new release whose container keeps exiting fails as soon as that is clear, and its error starts Application failure: and names the container, its exit code and its last message.

A deployment started by a git push also says what the push said about its commit, as its page shows it: git_commit_url (the commit on the provider), git_author {name, avatar_url} and git_merge_request {ref (!12 for a GitLab merge request, #12 for a GitHub or Bitbucket pull request), kind (merge_request or pull_request), url}. Each is null when the push did not say, and for every deployment not started by a push; a link is only ever an https address on the repository's provider. The public API's list gives the same three keys.

next_cursor is null on the last page.

Example call

tools/call
{
  "name": "corestack_enterprise_deployments_list",
  "arguments": {
    "enterprise_env_id": 1530,
    "status": "failed",
    "limit": 10
  }
}

If it is refused

ReasonWhat to do
invalid_argumentsThis is a CoreStack or CoreCluster environment; name it by its site_id in the corestack_deployments_* tools. Field cursor: that page does not exist; list again from the start.
tenant_mismatchNo environment with that id is yours (or a client's of your agency).
pin_refusedA token limited to some sites cannot reach a CoreStack Enterprise environment; the person can widen it to everything in the company.
scope_requiredThe token lacks a scope this call needs. Open the link in the answer to add it, then call again.
rate_limitedToo many calls. Wait for the number of seconds the answer names.
temporarily_unavailableThe Control Panel could not answer just now. Nothing was started; try again shortly.
internal_errorSomething went wrong on our side. Quote the trace id to support.

The same task elsewhere

Was this helpful?
Open in ClaudeOpen in ChatGPT