RFR: 1691: Run Jcheck twice in CheckRun if .jcheck/conf has changed

[Zhao Song]

On Wed, 7 Dec 2022 21:18:17 GMT, Erik Joelsson <erikj at openjdk.org> wrote:

>> When a pr is created, pr bot will run jcheck to check whether this commit is good. However, currently, we only run jcheck with the configuration from the target branch. Sometimes, user wants to modify jcheck configuration and accidentally messes up the format. In this case, pr bot would not be able to find this problem. After this commit with badly formatted jcheck configuration integrated, all the jcheck will fail and our bot gets stuck into a retry loop.
>> 
>> In this patch, if jcheck configuration file is updated, the bot will run jcheck twice, once with the configuration in the target and once with the new one in the source. So if the new configuration has any problem, it will became an integration blocker.
>
> bots/pr/src/main/java/org/openjdk/skara/bots/pr/CheckRun.java line 1083:
> 
>> 1081:                 var additionalConfiguration = AdditionalConfiguration.get(localRepo, localHash, pr.repository().forge().currentUser(), comments);
>> 1082:                 checkablePullRequest.executeChecks(localHash, censusInstance, visitor, additionalConfiguration, true);
>> 1083:                 if (localRepo.isFileUpdated(".jcheck/conf")) {
> 
> We probably don't need to run the second round if confOverride is set.

Good point!

-------------

PR: https://git.openjdk.org/skara/pull/1439