Concurrent Netlify builds getting skipped, only last one remains applicable when in queue

Support
, , , , , ,
1

We are using a CMS called Optimizely (EPiServer) integrated with Netlify. Whenever content changes are made and published in the CMS, a Netlify build is triggered via webhooks configured from the CMS. However, we’ve encountered an issue where if additional changes are made and published while a build is still in progress, subsequent builds are not triggered. Only the last published change initiates a build, while the earlier changes are skipped.

Is there a way to ensure that if, for example, 10 content changes are made, all 10 corresponding builds are queued and executed one after the other, rather than only the final change triggering a build?

We are using incremental builds, so only the page-specific changes are built. A full rebuild is not feasible due to the large volume of content, and invoking all CMS APIs for a small content change is causing server crashes.

2

Have you tried continuous deployment? Create deploys | Netlify Docs

3

This is not related to GitHub. I’m referring to CMS changes, where modifying content triggers a build.

4

@Umang Read the documentation here:

It seems what you may want would be a Custom ignore command where you have it set to “never ignore”.

That seems to be an exit code of 1 as per:

An exit code of 1 indicates the contents have changed and the build process continues as usual.

But it may not have any impact due to this other note:

The ignore command won’t cancel a build triggered by a build hook, regardless of exit code.

1 Like