I’m writing this post as a Support Engineer from Netlify. Some users are complaining about their builds being “stuck”. The reason why I’m bringing this to Hugo forums is to try and get some possible explanations as to why this can happen.
I’ve tried to narrow down the problems on Netlify end, but haven’t been able to reach to a conclusion. Not saying this is a Hugo problem, could be a change on our build systems, but I’d need some help narrowing it down. So, I’m looking for ideas to try and look for that might be causing this issue. Any advise is going to be super helpful.
For some context, this is the thread:
The problem is, the builds work fine once users trigger it with clearing cache, but if they don’t, they only get this:
> Start building sites … > hugo v0.85.0-724D5DB5+extended linux/amd64 BuildDate=2021-07-05T10:46:28Z VendorInfo=gohugoio
And that stays frozen for an indefinite time. We tried changing Hugo versions, tried deleting cache with
rm -rf, etc. Nothing works except for the clear cache button. More so, this is not happening for each build, some builds do work with cache.
So, is there something specific that might exist in the cache that could prevent Hugo from functioning properly? We usually cache
node_modules folder, and the user’s repo. Some of them were using a plugin, so that plugin was likely caching
resources folder too.
Are there any other users here with the same issue?
I have a few Hugo sites of myself, even tested a repo of one of the users, but all of it works fine.
Looking forward to any advice that I can collect.