Hi, @adalita. When I checked it looked like it was still timing out at 45 minutes. This is the maximum timeout when the build time limit is 30 minutes not 60. (The maximum is the build time limit plus an additional 15 minutes for post processing hence the timeout at 45.)
When I examined the settings, I saw this site was still set for 30 minutes. I’ve just increased it to one hour now. Would you please trigger another build now?
There are a few other things I want to mention.
First and most important
Please change the build command from this:
./build && ps auxw ; false
./build && ps -ef
Having the build command ending in
false means all build return an exit code of 1 and all non-zero exit codes will cause builds to fail. The build command will always fail while this is part of the build command.
ps auxw change to
ps -ef is merely cosmetic as it is serving the same purpose which I assume is debugging to see if there are defunct node background processes. The
-ef option change will show parent process ids and I believe that information would be important for troubleshooting the defunct processes (if that turns out to be the case as it could be just a long build instead).
The second issue is that I want to point out that the
ps -ef (or
ps auxw if your prefer) is never in the logs. The absence of this debugging output strongly suggests that the build is still running (and that this is not defunct background processes).
The third issue is the build time itself.
Gatsby does cache successful builds and our build system will reuse that cache if it exists. This means that once a build is successful, future build should then be “incremental”. This means that one the cache is created only changed files will require full rebuilds and therefore the builds should be faster … once there is a successful build. A successful build is required first as only successful build caches are reused. I see successful manual deploys but no successful site builds at Netlify for this specific site yet.
To summarize this reply:
- the build time limit wasn’t increased to 60 before but it has been now
- the “
; false” (including the semi-colon) should be removed from the build command
- once a build is successful the gatsby caching should improve future site builds at Netlify
Would you please build again and let us know if it succeeds or not?