From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

&gt; A change in `buildSrc` causes the whole project to become out-of-date.
&gt; Thus, when making small incremental changes, the `--no-rebuild` command-line option is often helpful to get faster feedback. Remember to run a full build regularly.
(<https://docs.gradle.org/current/userguide/organizing_gradle_projects.html#sec:build_sources|ref>)

&gt; `--no-rebuild`: Do not rebuild project dependencies. Useful for debugging and fine-tuning `buildSrc`, but can lead to wrong results. Use with caution!
(<https://docs.gradle.org/current/userguide/command_line_interface.html#sec:command_line_execution_options|ref>)

I just tried this flag and my build immediately failed because it didn't rebuild the conventions plugin included build, which is basically what I expected that flag to do based on the "Do not rebuild project dependencies" description. The other parts of the docs around this don't make sense to me though, how is this useful for iterating on conventions plugins if using this flag prevents them from being rebuilt?