By leolleo
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?
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!
This comment has been deleted
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
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.
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.