commit | e554a54b9a23507d5db60e2885c99789ac70a31b | [log] [tgz] |
---|---|---|
author | David Ostrovsky <david@ostrovsky.org> | Fri Feb 19 19:40:33 2021 +0100 |
committer | David Ostrovsky <david@ostrovsky.org> | Tue Feb 23 07:13:15 2021 +0100 |
tree | ed54058983b08fa4fce1d8e2cb8570c8b6547aae | |
parent | 42dfbb525bf92375f1f063b5723980b240d0c3e4 [diff] |
Remove --test_summary=detailed option It seems that bazel doesn't report whether or not test result was cached and the execution was skipped, when this option is passed, so switch to the default test summary (short), e.g.: //javatests/com/google/gerrit/acceptance/server/mail:MailIT \ (cached) PASSED in 19.6s Change-Id: Ib8c6580058ab458ea8f127821e623f7882858fd7
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 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/