BCR support

[bu3]

Hi,

any plan to enable bcr support for this rule? I see something was already happening but I didn't manage to find the rule on BCR.
In case I could try to help.

Thanks

[manuelnaranjo]

We're not using this rules in BCR yet, but we may change that some time this year and we would do it, but of course PRs are always welcomed

[bu3]

Hi @manuelnaranjo I sent this PR to get started.
I have already started to change BCR registry on my machine and I will send a PR eventually and I will ping you in there when ready

[bu3]

Hey @manuelnaranjo I created this PR for BCR registry.
The current release and the current version exported don't match.
In the registry I have to define the version as 0.0.0 as per the exported MODULE.bazel file, while the release is v0.0.1.
That's why I was trying to fix the file in main.

BCR registry tooling seems to be happy with my changes anyway:

➜  bazel-central-registry git:(pitest_bcr) bazel run -- //tools:bcr_validation --check=rules_pitest@0.0.0
INFO: Analyzed target //tools:bcr_validation (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
Target //tools:bcr_validation up-to-date:
  bazel-bin/tools/bcr_validation
INFO: Elapsed time: 0.103s, Critical Path: 0.00s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
INFO: Running command line: bazel-bin/tools/bcr_validation <args omitted>


+++ Module versions to be validated:


rules_pitest@0.0.0


+++ Validating rules_pitest@0.0.0


BcrValidationResult.GOOD: The module exists and is recorded in metadata.json.

BcrValidationResult.GOOD: The source URL matches one of the source repositories.

BcrValidationResult.GOOD: The source URL doesn't look unstable.

BcrValidationResult.GOOD: The source archive's integrity value matches.

BcrValidationResult.NEED_BCR_MAINTAINER_REVIEW: Module version rules_pitest@0.0.0 is new, the presubmit.yml file should be reviewed by a BCR maintainer.

BcrValidationResult.GOOD: The presubmit.yml file is valid.

BcrValidationResult.GOOD: Checked in MODULE.bazel matches the sources.



+++ Verifying attestations


BcrValidationResult.GOOD: rules_pitest@0.0.0: No attestations to check.

BcrValidationResult.GOOD: No module name conflict found.

I set yourself as the maintainer of the code in that PR with a fake email. I hope it is ok

[bu3]

Here we go: https://github.com/bazelbuild/bazel-central-registry/tree/main/modules/rules_pitest

[bu3]

It does not work properly though.
The MODULE.bazel exports a different name.

➜  sfdc-bazel git:(pitest-reprise) ✗ btest projects/services/examples/pitest:pitest_mutate
Starting local Bazel server and connecting to it...
ERROR: Error computing the main repository mapping: in module dependency chain <root> -> rules_pitest@0.0.0: the MODULE.bazel file of rules_pitest@0.0.0 declares a different name (com_bookingcom_rules_pitest)