[Edited as rejected by system for too many links and characters, after pasting the long deploy log]
I have followed the Netlify blog article “Enable Gatsby Incremental Builds on Netlify” of 23rd April to the letter. But the result has been an increase in build time, and all the files are still being built as before.
The Netlify site name: https://squawks3.netlify.app
The repo is based on Gatsby starter https://www.gatsbyjs.org/starters/hagnerd/gatsby-starter-blog-mdx/, modified to have 30+ demo blog articles and a list or index page with pagination. There are no other pages. When first deployed to Netlify 139 new files were uploaded.
All the steps in the Netlify blog article were applied after the 452pm build last night. So the next deploy after, at 503pm, created the Gatsby cache. Subsequent builds should have applied incremental building, but did not despite making only minor changes each time to one blog article.
Each time the deploy log said “Found a Gatsby cache. We’re about to go FAST.” but then builds the entire site (131 new files loaded, same as all but initial build). What is going wrong here?
The build settings (typical Gatsby) with public repo:-
The deploy log is too long for a screenshot, how can I copy and paste or send?