We have a monorepo like the following:
.
├── apps/
│ ├── web
│ ├── sanity
│ └── storybook
└── libs/
├── ui-library
├── another-library
└── ...etc
web, sanity, and storybook all deploy separately to netlify. When something in one of the libaries (libs) changes, we need to trigger rebuilds of various apps that consume them which seems to necessitate a custom ignore script that will look outside the base directory of a deploy for changes in other directories/files. Consistent with the default ignore behavior, if there is a change in only one app we do not want to re-deploy the others.
The reason we need to be able to trigger a build from admin is because our web app (and possibly others in the future) consume data from APIs. If these external data sources change, we need to rebuild. we plan to utilize webhooks to trigger rebuilds, but we also need (for reassurance of uptime/data accuracy) to be able to manually trigger a rebuild in case of a webhook failure, a botched ENV var entry, etc - who knows. not being able to control deploys properly is simply not acceptable in an enterprise environment. Also since netlify doesn’t support NextJS’s ISR, we will be relying on rebuilds for any and all content changes unfortunately.
Let me know if you need more info, looking forward to a solution.