I have a monorepo with 2 folders: /back and /front
The front is a Gatsby static website.
I’ve setup 2 different creates sites, with correct /front root folder for both (because I need to deploy the same app with 2 distinct build settings / env variables). (Actually both sites existed monorepo support, but we “relinked them” as the doc said to do.
What I expect is that:
- all commits in /back do not trigger a /front build
- all commits in /front do trigger a /front build
What I see in practice:
- all commits in /front do trigger a /front build
- some commits in /back sometimes trigger a front build, which is unexpected
I’ve noticed that just after a /front commit (leading to an expected build), the 1st /back commit does often trigger a build, and subsequent /back commits are appropriately cancelled.
Also, something weird just happened. As my 2 sites are actually configured the same (/front root folder), I would expect them to behave the same. But instead of that, I just commited in /back, and site1 did trigger a /front build, while site2 didn’t! So the same configuration, with the same github repo, and the same git commit, did actually trigger different results.
Unfortunatly I can’t publish my team name publicly but if that helps you can ask me in private for more infos.
Maybe that link helps if the id is unique across all teams, it’s the build that triggered on site1, while site2 did cancel: Netlify App<HIDDEN_TEAM_NAME>/builds/5df284c0d00af00007e901f8
If that helps to reproduce, we are also using GitHub - axe312ger/gatsby-plugin-netlify-cache: Caches your Gatsby .cache and public folder to speed up your build time by 10x