| commit | 735b36277f03884216237b5f05b63ea7334d034b | [log] [tgz] |
|---|---|---|
| author | Thomas Draebing <thomas.draebing@sap.com> | Sun Feb 09 10:22:52 2020 +0100 |
| committer | Luca Milanesio <luca.milanesio@gmail.com> | Sun Feb 09 16:18:56 2020 +0000 |
| tree | d4ad983796693f810fc91e55d729b5c2229746d0 | |
| parent | 0fab0a41b8f94749dac2128f19cf98811945be66 [diff] |
Install npm-packages before running polygerrit tests
The PolyGerrit tests during the Gerrit-verifier-bazel job failed,
because some npm-packages were not found. Since recently these packages
were meant to be installed to the local workspace during the job run,
but this was so far only done for Gerrit-codestyle builds.
Since these tests are also run in the Gerrit-bazel-{branch}-jobs,
the build step installing the packages is now also performed in these
jobs.
Change-Id: I25053488740131450e0f5ee36149aafe1a6f2d3a
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/