commit f6bb84c6da82f31096f8382474eef71d9b689dfb
author Oliver Newman <olivernewman@google.com> Fri May 14 16:44:59 2021 +0000
committer Oliver Newman <olivernewman@google.com> Fri May 14 16:44:59 2021 +0000
tree b8364a2f091cf7e80c40dcf2f539377e1ec92d7f
parent ab1adfec7f68b0bfffe7129dea964c041635c64a

[tricium] Use lucicfg to generate Tricium configs

Unfortunately, lucicfg currently enforces that each LUCI project only
defines one unique combination of CQ group and Tricium analyzer, which
makes it impossible to define different analyzers for different
repositories given our current setup, until the migration to LUCI CV.

Therefore, we can only declare one Tricium analyzer (tricium-infra) in
the main "fuchsia" LUCI project, the others have to remain separate.

That doesn't prevent us from merging these config files into global
integration, but that would require updating the central project
definitions in projects.cfg to point to integration.git, and these
projects will be completedly deleted once LUCI CV is ready.

Significant changes:
- Deleted all tricium-dev.cfg files. I'm pretty sure they're not useful
  anymore.
- Unset `path_filters` so the analyzers run on *all* changes, so we get
  spell checks and copyright checks even on files with random
  extensions.
- Changed the tools analyzer to use the "tricium-infra" builder, instead
  of "tricium-tools", which doesn't exist.

I chose to generate all project configs using a single `main.star` file
configured via `lucicfg -var` for simplicity, rather than having a
separate starlark file for each project. The lucicfg docs recommend
against relying on `lucicfg -var`, but this code should hopefully be
short-lived.

Fixed: 76644
Change-Id: I1216ce6fdbba497c839888d84833f83e2b3bc527
Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/config/+/530280
Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
Reviewed-by: Marc-Antoine Ruel <maruel@google.com>