[ai-code-review plugin] Project configuration inheritance not working for large project hierarchies

[Shohei Nakagata]

Hello,

We are evaluating the ai-code-review plugin (stable-3.9) for our organization
with 1000+ Gerrit projects, but we've encountered a limitation with
configuration inheritance.

## Problem

The plugin does not inherit [plugin "ai-code-review"] settings from parent
projects, requiring us to configure each project individually.

Example of current behavior:
- Parent project defines: aiModel, aiSystemPrompt, enabledVoting
- Child project sets: isEnabled = true
- Result: Child does NOT inherit parent settings

This differs from other Gerrit configurations (access controls, submit rules)
which properly inherit from parent projects.

## Root Cause

ConfigCreator.java:75 uses `getFromProjectConfig()` instead of
`getFromProjectConfigWithInheritance()`:

```java
// Current
PluginConfig projectConfig = configFactory.getFromProjectConfig(projectName, pluginName);

// Proposed
PluginConfig projectConfig = configFactory.getFromProjectConfigWithInheritance(projectName, pluginName);
```

## Questions

1. Is this behavior intentional?
2. Would a patch to enable inheritance be acceptable?
3. Any backward compatibility concerns?

## Impact

For our scale (1000+ projects), manual configuration is not feasible. This is
currently blocking our adoption of the plugin.

Thank you for your time.

Best regards,
Shohei Nakagata

[Luca Milanesio]

Hi Shohei,

> On 18 Feb 2026, at 20:18, Shohei Nakagata <shohei....@craftsman-software.com> wrote:
>
> Hello,
>
> We are evaluating the ai-code-review plugin (stable-3.9) for our organization
> with 1000+ Gerrit projects, but we've encountered a limitation with
> configuration inheritance.
>
> ## Problem
>
> The plugin does not inherit [plugin "ai-code-review"] settings from parent
> projects, requiring us to configure each project individually.

Thanks for sharing your problem; it’s actually very timely, as I’ll present the new Gerrit v3.14 AI review capabilities tomorrow (see [1]) and the event will be live-streamed on YouTube (see [2]).

> Example of current behavior:
> - Parent project defines: aiModel, aiSystemPrompt, enabledVoting
> - Child project sets: isEnabled = true
> - Result: Child does NOT inherit parent settings
>
> This differs from other Gerrit configurations (access controls, submit rules)
> which properly inherit from parent projects.
>
> ## Root Cause
>
> ConfigCreator.java:75 uses `getFromProjectConfig()` instead of
> `getFromProjectConfigWithInheritance()`:
>
> ```java
> // Current
> PluginConfig projectConfig = configFactory.getFromProjectConfig(projectName, pluginName);
>
> // Proposed
> PluginConfig projectConfig = configFactory.getFromProjectConfigWithInheritance(projectName, pluginName);
> ```

The enablement of the AI Review functionality will controlled by the “AI Review” permission, which will follow the normal Gerrit project hierarchy rules.
See the open changes at [3].

>
> ## Questions
>
> 1. Is this behavior intentional?
> 2. Would a patch to enable inheritance be acceptable?
> 3. Any backward compatibility concerns?

Please do follow my talk tomorrow, as I will go through the different approaches to AI Review with Gerrit, including this plugin.

>
> ## Impact
>
> For our scale (1000+ projects), manual configuration is not feasible. This is
> currently blocking our adoption of the plugin.

Please do think carefully before adopting the plugin, watch my talk and make your choices consciously.

HTH

Luca.


[1] https://www.meetup.com/gerritmeets/events/312898799/
[2] https://tv.gerritforge.com <https://tv.gerritforge.com/>
[3] https://gerrit-review.googlesource.com/c/gerrit/+/553501/3

>
> Thank you for your time.
>
> Best regards,
> Shohei Nakagata
>

> --
> --
> To unsubscribe, email repo-discuss...@googlegroups.com
> More info at http://groups.google.com/group/repo-discuss?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/repo-discuss/9b780b58-02bc-4b08-bb2c-4385fea0d26an%40googlegroups.com.