I’ve deployed a production version of my static application using manual deploy. However, my staging version which uses automatic deploy has features that the other don’t, even if I redeploy de production version, which the build gets skipped. Is there any solution/workaround to this scenario?

2 comments

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.

×
Submit an Answer
3 answers

I think @bobbyiliev may be onto something with the git branch. That said, you can manually trigger a deploy by clicking the “Deploy” button in the top right of your apps control panel. That should check for new commits in your repo, rebuild if necessary, and deploy.

If you want to force a rebuild you can do so with doctl, DigitalOcean’s command-line utility. First, find the app’s ID with doctl app list, and then create a new deployment with the --force-rebuild option. Ex. doctl app create-deployment --force-rebuild 42a33f83-5093-44c7-acb5-53f0a218b732.

If that doesn’t resolve the issue, please contact support.

  • Hey @cbaker thank you for the reply!

    I’ve made a workaround by temporarily activating auto deploy and making a commit, that worked back at the day. If the issue arises again I’ll try out the doctl suggestion. Currently I’ve opened a ticket.

Hi there,

This is quite interesting, it sounds like that you might be using a different branch, have you cross-checked that you are using the correct branch?

Regards,
Bobby