Limit build minutes / smartly build projects

[seiyria]

Hi!

I was wondering if it’s possible to limit a particular project to, say, X builds / day.

Similarly, I was wondering if it was possible to auto-detect project changes and either build or not build accordingly. For example, if I have a monolith project (frontend and backend) and I only want to rebuild the project when the frontend changes, would you have any recommendation on how to do that easily / automatically?

Thank you!

[perry]

Hi there, I don’t have specific answers at this time, but, this thread:

[Support Guide] How can I optimize my Netlify build time?

Last reviewed by Netlify Support - August, 2023 If you are interested in learning more about how our bots approach building sites, these three articles are a great place to start: How our Build Bots build sites The last major upgrade to our build environment and perhaps least-loved but most useful, how to debug your builds So you might think, it’s great that Netlify builds every commit from my repos…but isn’t that a bit wasteful? The answer is, it depends, but we can at least give you…

is a great starting point for optimizing builds, as is this one:

Build Time Optimization Help

Hello With the recent changes regarding Build Times, I was hoping someone could share any and all tips regarding how to optimize my build times. I am currently sitting at 8 minutes for my project. That means I can possibly reach a max of 37 updates in a month. Can anyone help me figure out why netlify tries to upload 500+ files on every single tiny change. [image] In case this could be useful for others, so far what I have found out today regarding optimizing build times: Stopping …

[seiyria]

Hi! This has helped a bit, I realize I could turn off deploy previews for a handful of my projects that are fairly low traffic but build intensive.

I’m still not sure what to do with my monorepos, though. Maybe I should make Travis CI send a notification via webhook if my client changes? Is there an example of something like that?

[luke]

Hi, @seiyria. For monorepos, our build in method for testing when to build is the setting build.ignore. Here is an example from a netlify.toml file:

[build]
  ignore = "git diff --quiet HEAD^ HEAD sub_dir/"

The build ignore command works be checking the exit code of the command run. In the git diff command above, the exit code will be non-zero if there has been a change somewhere in that subdirectory (sub_dir/) between the most recent commit and its parent commit.

I point out the “non-zero” because, in most cases, a non-zero exit code means an error and, in most cases, a process will stop on a non-zero exit.

With build.ignore, the non-zero means there is a difference which is what we testing for and we only want to build if that difference exist. So, the build.ignore continues on a non-zero exit - instead of stopping. (This is just something to keep in mind when writing custom build.ignore commands.)

Regarding limiting to X builds a day, there is no such option at this time.

If there are other questions about this, please let us know.

[seiyria]

@luke thank you! this helps a lot.

[tnir]

Can I vote for this feature request? I want to have this kind feature without adding(/modifying) netlify.toml to the project.

[perry]

can you describe a little more how this would be beneficial? knowing more about your use case is helpful in deciding how to implement.