Detect polygerrit test log under either bzlmod or workspace execroot The polygerrit web_test_runner path lookup used to branch on the presence of polygerrit-ui/pnpm-lock.yaml to pick between two execroot layouts: pre-bzlmod: ~/.cache/bazel/.../execroot/gerrit/bazel-out/... post-bzlmod: ~/.cache/bazel/.../execroot/_main/bazel-out/... That detection was indirect — pnpm and bzlmod are unrelated, and the presence of pnpm-lock.yaml could change for reasons that have nothing to do with the execroot name. The two branches were also otherwise identical. Replace both branches with a single wildcard on the execroot segment (execroot/*/), which matches `gerrit` and `_main` and any future rename. Drop the pnpm-lock.yaml check. Change-Id: I3e667bb6b260ec27f88417cb7a76881e5f583f86
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/