If a build or deployment is running longer than expected, it may be caused by one of the following:
- The build is blocked by something in your build hook.
- The deployment is blocked by a long-running process in your deploy hook.
- The deployment is blocked by a long-running cron job in the environment.
- The deployment is blocked by a long-running cron job in the parent environment.
First, determine if the build has completed and is attempting to deploy. Access the environment’s build logs with the Platform.sh CLI:
$ platform logs <project ID>
Alternatively, you can click on the
Pending status icon on the Web UI to check its status.
There should be a line similar to
Re-deploying environment w6ikvtghgyuty-drupal8-b3dsina.
If that message is not visible, the project is most likely in a state of a blocked build, and it will be required to create a support ticket to have the build killed.
If the above message is visible, the project is in a stuck deployment.
SSH into the environment.
$ platform ssh
The long-running cron jobs on the environment can be found with the command
$ ps afx
and once the long-running process has been identified (
<PID>), it can be killed with the command
$ kill <PID>
You can find additional information about stuck builds and deployments following the link below.