CorefinityCorefinityDocs
Open the Control PanelControl Panel
Deployments · 52 of 65

corestack_enterprise_deployment_trigger

Deploy on a CoreStack Enterprise environment.

Scope writeRuns as a taskNo secrets returned
On this page

When to use it

Deploy on a CoreStack Enterprise environment, one of two ways:

  • Start a waiting deployment (deployment_id): an environment that deploys git pushes by hand keeps each push waiting (pending) until someone presses Deploy. This is that button: the deployment is built from its pipeline as it is now, or on another pipeline of the environment (pipeline_id).
  • Deploy a commit (repository_id + commit): a new deployment of that commit of one of the environment's repositories, through the pipeline the repository deploys with.

A task follows the deployment to its end; poll it, or read corestack_enterprise_deployment_get. Cancelling the task cancels the deployment. Uploading a release archive is the public API's POST /api/environments/{environment}/deployments (a file body); the same two ways are its POST …/deployments/{deployment}/run and the same POST with git.

Ask for it

Prompt
Using the Corefinity MCP server, call corestack_enterprise_deployment_trigger with enterprise_env_id 1530, repository_id 812, commit 4f2c9a1e0b7d3c5a6e8f9b0c1d2e3f4a5b6c7d8e, notes Hotfix for the checkout page. (Deploy on a CoreStack Enterprise environment.) Tell me what it returned.

Inputs

commitstring

With repository_id

deployment_idinteger

A waiting deployment to start. At least 1.

enterprise_env_idintegerRequired

A CoreStack Enterprise environment's id; for CoreStack or CoreCluster use the corestack_deployment_* tools. At least 1.

namestring

With a commit only Up to 255 characters.

notesstring

With a commit only Up to 10,000 characters.

pipeline_idinteger

With deployment_id only, another pipeline of the environment to start it on At least 1.

repository_idinteger

With commit, a new deployment of that repository of the environment At least 1.

Give deployment_id, or repository_id and commit: never both, never neither.

Example call

tools/call
{
  "name": "corestack_enterprise_deployment_trigger",
  "arguments": {
    "enterprise_env_id": 1530,
    "repository_id": 812,
    "commit": "4f2c9a1e0b7d3c5a6e8f9b0c1d2e3f4a5b6c7d8e",
    "notes": "Hotfix for the checkout page"
  }
}

If it is refused

ReasonWhat to do
invalid_argumentsNeither or both ways given, pipeline_id with a commit, a commit that is not a full SHA, or a repository that is not this environment's (field repository_id); a CoreStack or CoreCluster environment (field enterprise_env_id).
staleThat deployment is not waiting any more, or the environment has already moved past it, or the pipeline chosen — for a commit, the pipeline its repository deploys with — is no longer available in the environment. Read it again.
busyThe same start is still being applied. forbidden: the person's role lacks the Create Deployments permission (Deploy Deployments to start a waiting deployment). The message names it and says an owner of the company can grant it in Roles; details.permission is createDeployments (or deployDeployments).
no_namespaceThe environment has no namespace on its cluster, so there is nothing to deploy to. Nothing is created; the Control Panel's Deploy form and the REST API refuse it in the same words. Staff must look at the environment.
tenant_mismatchThe object does not exist or the token may not see it. Check the id.
pin_refusedThe grant is limited to chosen clusters, sites or environments, and this call is outside them. Open the link in the answer to widen it.
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