CodeOwnerSubmitRule: Fix exception logging

Rule errors are only returned in case an exception is caused by a user
misconfiguration (e.g. an invalid OWNERS file). In this case it is
sufficient to log a warning (without stacktrace).

For other exceptions CodeOwnerSubmitRule throws a
CodeOwnersInternalServerErrorException that will be logged on a higher
level. Hence CodeOwnerSubmitRule doesn't need to write an error log in
this case.

Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: I2000893ce343d56073c2e10096eb6be8dfc9cd61
1 file changed
tree: f7f7d739cdb0159ea3534c94b1603f47b670bead
  1. java/
  2. javatests/
  3. proto/
  4. resources/
  5. test/
  6. ui/
  7. .eslintrc.json
  8. .gitignore
  9. .gitreview
  10. bower.json
  11. BUILD
  12. LICENSE
  13. package-lock.json
  14. package.json
  15. README.md
README.md

Gerrit Code Review code-owners plugin

This plugin provides support for defining code owners for files in a repository.

If the code-owners plugin is enabled, changes can only be submitted if all touched files are covered by approvals from code owners.

Also see resources/Documentation/about.md.

IMPORTANT: Before installing/enabling the plugin follow the instructions from the setup guide, see resources/Documentation/setup-guide.md.