| commit | 227c727516b9d2b207e6b3695f0c923742ef69fd | [log] [tgz] |
|---|---|---|
| author | Frank Borden <frankborden@google.com> | Tue May 09 10:51:58 2023 +0200 |
| committer | Frank Borden <frankborden@google.com> | Fri Jun 09 09:50:21 2023 +0000 |
| tree | 3331d2981f3262488cbfdf64c3d2e5a08f0f3a6e | |
| parent | ac310e0a379728486af2b5ff2f0b2ad9d52487ca [diff] |
Disable polygerrit checks on master branch All master branch FE verification is now handled by LUCI [0] and submits are gated on the Frontend-Verified submit requirement that LUCI votes to satisfy. This includes type checking, test running, and linting. Now that Verified and CodeStyle submit requirements are not needed for FE-only changes on master branch [1], Jenkins should not waste time running these builds. Until LUCI recipes are added for release branches, non-master branches still need Jenkins verification. [0]: Change 372706 [1]: Change 373219 Change-Id: Iaefaac42b9ccccc1320531a581871384357ef115
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/