Report this

What is the reason for this report?

App Platform: How to Stop Release Flow if Job Fails After Dockerfile Deployment

Posted on February 23, 2025
wz

By wz

In App Platform, I want to run a job after building and pushing a Dockerfile. Is it possible to stop the release flow if this job fails?

For example, I want to run a migration after the application is built, but if the migration fails, I don’t want to release it to production.

In POST_DEPLOY, it seems that the release is finished regardless of the migration result.



This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Hi there,

In DigitalOcean App Platform, the POST_DEPLOY phase runs after the release is already deployed, so a failed job there won’t block the release. To stop the release flow if a job fails (like a migration), you can move the migration step to the PRE_DEPLOY phase instead.

The jobs in PRE_DEPLOY run before the app is released—if the migration fails, the deployment should in theory stop and won’t reach production.

For detailed information on configuring deployment phases in DigitalOcean App Platform, refer to the App Specification Reference.

- Bobby

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.