Question
App connected to GitLab doesn't pull latest commit on deployment
- Posted on February 15, 2021
- Next.jsDigitalOcean App Platform
Asked by phegman
I have a DO App that is deploying a static site connected to GitLab. If I manually trigger a deployment it doesn’t pull the latest commit. It appears to be pulling the commit that was used for the initial deployment when I created the App. Is there anyway to clear the build cache and force it to pull the latest commit?
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.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
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.
Hello, this should be resolved now.
Same thing happened to me with github instead of gitlab. automatic deployment did not fix issue. Had to completely destroy app and create again with Automatic deployment enabled
Hello, thanks for bringing this to attention. We have investigated this and confirmed there is an issue in certain scenarios when using GitLab and create-deployment CLI option and combination of these settings. We should have a fix shortly. You should not have to update
doctlto resolve this once we have it fixed. Unfortunately in the mean time I think the only workaround is to enable automatic deployment on code changes. This can be manage in a stricter sense if needed, if you use a branch that you control merges to and set that as the source. We will update this community question when we confirm the fix is rolled out.