Bazel: Trigger PolyGerrit verification for .bzlmod changes

Include `.bzlmod` files in the Bazel-related change detection so that
PolyGerrit validation is triggered when module definitions are modified.

This ensures UI verification runs for Bazel module changes, aligning
behavior with existing handling of WORKSPACE, BUILD, and .bzl files.

Change-Id: I7ce01a51319aeb946892930fd1a5ded05a039ed3
1 file changed
tree: 320afcbe7424984e95aa6936fa8850da8dcbe041
  1. jenkins/
  2. jenkins-docker/
  3. jenkins-internal/
  4. vars/
  5. .gitignore
  6. Jenkinsfile
  7. README.md
  8. yamllint-config.yaml
README.md

Gerrit CI scripts

Providing jobs

This project uses Jenkins Jobs Builder [1] to generate jobs from yaml descriptor files.

To add new jobs reuse existing templates, defaults etc. as much as possible. E.g. adding a job to build an additional branch of a project may be as easy as adding the name of the branch to an existing project.

To ensure well readable yaml-files, use yamllint [2] to lint the yaml-files. Yamllint can be downloaded using Python Pip:

pip3 install --require-hashes yamllint

To run the linter, execute this command from the project's root directory:

yamllint -c yamllint-config.yaml jenkins/**/*.yaml

Yamllint will not fix detected issues itself.

[1] https://docs.openstack.org/infra/jenkins-job-builder/index.html [2] https://pypi.org/project/yamllint/