corestack_ deployments_ pipeline_ check
Check pipeline lines.
When to use it
Check lines for a pipeline stage before you save them: each line's verdict, badges and suggestion, and whether the build would open tunnels to the environment's services. Nothing is saved or run.
A badge whose severity is blocking refuses the save of the stage. Every line of every stage runs in a shell of its own, so a line that is only cd <dir>, export NAME=..., source ..., . ... or set ... changes nothing for the next line: it carries the badge own_shell and the warning "Each line runs in its own shell, so this does nothing for the next line. Join them on one line, for example: cd web/app/themes/x && npm ci". The badge is blocking for a lone cd that a later line follows (corestack_ refuses it as line_own_shell), and a warning otherwise. Join the lines with && instead. A preset hook's last line is followed by the preset's next steps: checked here with the hook's lines alone it reads as a warning, but the save refuses it, and corestack_deployments_pipeline_get marks it blocking.
The same action in the public REST API, with the same checks, refusals and scope: POST / (binding_id).
Ask for it
Using the Corefinity MCP server, call corestack_deployments_pipeline_check with site_id 4211, stage build, lines ["npm ci","npm run build"]. (Check pipeline lines.) Tell me what it returned.Inputs
Default: the environment's default binding. At least 1.
Up to 200 items.
At least 1.
builddatabasepost_deployExample call
{
"name": "corestack_deployments_pipeline_check",
"arguments": {
"site_id": 4211,
"stage": "build",
"lines": [
"npm ci",
"npm run build"
]
}
}If it is refused
| Reason | What to do |
|---|---|
invalid_arguments | The arguments do not match the tool's input schema, or the Control Panel refused a field. Fix the fields named in the answer and call again. |
tenant_mismatch | The object does not exist or the token may not see it. Check the id. |
scope_required | The token lacks a scope this call needs. Open the link in the answer to add it, then call again. |
pin_refused | The grant is limited to chosen clusters, sites or environments, and this call is outside them. Open the link in the answer to widen it. |
rate_limited | Too many calls. Wait for the number of seconds the answer names. |
temporarily_unavailable | The Control Panel could not answer just now. Nothing was started; try again shortly. |
internal_error | Something went wrong on our side. Quote the trace id to support. |