Command failed with exit code 129

[fool]

This seems like a problem in your code rather than in our services, but happy to help you troubleshoot. I suppose as a start that this doesn’t happen when you build locally?

This article has our best build debugging advice:

[Support Guide] Debugging Netlify site builds

Last reviewed by Netlify Support - August, 2023 Note: This article is only about builds within Netlify’s Continuous Integration (CI) environment, as triggered from git commits or from incoming build webhooks. You can learn more in depth about how Netlify builds your site in this article about how our build bots build sites. Some background There are a fair number of reasons that a build could fail in Netlify’s CI environment, even if building works locally. Testing locally is always the place …

wherein you’ll see that number 1 is making sure it builds locally, but #2 is being sure that you’ve explicitly set all of the versions for things like yarn and node

Some other things to consider:

• the error comes from yarn, so I’d guess yarn is what is failing.

• I am somewhat of a unix whiz but that isn’t a typical exit code. That is what the numbered exit codes are though - unix exit statuses. This article suggests that it is probably an exit code of 1 with some modifier, and that is a pretty generic failing exit as you can see in that doc, so not a lot of guidance there.

• since you use gatsby v4, you really should be using the updated plugin, which is the only version with full Gatsby4 support:

 ❯ Outdated plugins
7:36:43 PM:    - @netlify/plugin-gatsby@1.0.3: latest version is 2.1.2
7:36:43 PM:      Migration guide: https://ntl.fyi/gatsby-plugin-migration
7:36:43 PM:      To upgrade this plugin, please uninstall and re-install it from the Netlify plugins directory (https://app.netlify.com/plugins)

While none of those may directly resolve the problem, I think they are all worth looking into to see if any do. If not, let us know what if any changes you observe when you try following the advice (e.g. about upgrading the gatsby plugin) as that will be useful details to feed into future steps of our troubleshooting.