shell step "..." has no image and this environment does not allow host shell
A SHELL step without an image wants to run on the host, but the environment does not allow it. Give the step an image. See Environments.
no Dockerfile found at "..."
dockerfile_path is wrong. Check the Dockerfile path in the repository.
kaniko_build requires a registry_id on the step, or the GHCR_USERNAME and GHCR_TOKEN variables
The Kaniko build has no registry to push to. Define a registry under Infrastructure > Registries and pick it on the step with registry_id.
trivy scanner is not installed in namespace "..."
Press Install Trivy on the environment page.
no namespace configured and no K8sNamespace host fact available
A Kubernetes step is not running on a Kubernetes agent, or the namespace could not be determined. Set namespace on the step, or run it in a Kubernetes environment.
needed artifact "..." not found
The artifact requested with needs_artifacts was not found. Check that the run that produces it succeeded and that the name is right.
supply chain policy: ...
The image failed the environment's supply chain policy (signature, SBOM or critical vulnerabilities). See Supply chain security.
... was withdrawn: ...
The pipeline uses a withdrawn step pack version. Update the pipeline to another version. See Step packs.
Tip: You do not have to run a failed run from scratch. Rerun failed steps on the deployment page reuses the steps that succeeded. See Deploy verification and rollback.
On GitLab and Azure DevOps you can see the response to each webhook delivery on the SCM side: Recent events on the project's Settings > Webhooks page on GitLab, and the subscription history under Project Settings > Service hooks on Azure DevOps. When EJO ignores an event it answers 200 with "status": "ignored" and a reason.
Check the binding's triggers and commit branch. If the same webhook arrives twice, no second deployment is created.
no repository binding for this repo
There is no binding for this repository, or the name on the binding is not exactly what the SCM sends (GitHub owner/repo, GitLab path_with_namespace, Azure DevOps org/project/repo).
event branch does not match the bound branch
The push went to a branch other than the binding's commit branch.
this event type is not enabled on the repository binding
The event's trigger is off on the binding (for example Pull request or Tag).
draft pull request or draft merge request
Draft PRs do not start runs. Mark the PR as ready.
Clone fails on a PR from a fork
Fork PRs get no clone credentials, so cloning a private repository fails for them.
SCM token is not configured; copy the delivery URL and secret into the SCM UI on the webhook
The hook could not be created automatically. Enter the URL and secret under the project's Settings > Webhooks on GitLab by hand.
401 invalid webhook token under Recent events
The Secret token on GitLab does not match the webhook secret in EJO.
500 gitlab webhook secret is not configured on the master under Recent events
EJO has no saved webhook for GitLab. Create one under Settings > Webhooks.
gitlab token is not configured; merge gate requires gitlab.token ... when saving a binding
The merge gate needs a token. Keep Block merge until this pipeline succeeds off until a token is set.
The merge button is not blocked
The token lacks the api scope or enough permission on the project. Turn on Pipelines must succeed on GitLab by hand; the main pipeline still stays WAITING.
gitlab token is not configured or gitlab group "..." was not found on an SCM group
Group scans need a token; check the group path and the token's access.
Private repositories cannot be cloned, statuses and pull request comments do not show
No Azure DevOps PAT is set in EJO, or the PAT lacks Code (Read) and Code (Status). See Connect your source control.
SCM token is not configured; copy the delivery URL and secret into the SCM UI on the webhook
The service hooks could not be created automatically. Add them under Project Settings > Service hooks for Code pushed, Pull request created and Pull request updated by hand.
401 invalid webhook secret in the service hook history
The X-Ejo-Webhook-Secret header is missing or the secret does not match.
500 azure devops webhook secret is not configured on the master in the service hook history
EJO has no saved webhook for Azure DevOps. Create one under Settings > Webhooks.
azure devops PAT is not configured; merge gate requires azure_devops.pat ... when saving a binding
The merge gate needs a PAT. Keep the merge gate off until a PAT is set.
The merge button is not blocked
The PAT lacks Policy (Read & write). Add a branch policy on the target branch that requires the status with genre ejo and name pipeline by hand; the main pipeline still stays WAITING.
The preview is not removed after the PR closes
The Pull request updated service hook is missing. Completed and abandoned PRs arrive with that event.
use organization/project on an SCM group
An Azure DevOps group must be entered as org/project.