Avoid looking for plugin's artifacts in subdirectories

The checks plugin stores its tests into an artifact called
checks.jar under the javatests directory tree. Do not recurse
subdirectories when looking for the plugin artifact, so
that test artifacts are not discovered.

Bug: Issue 14424
Change-Id: If352415b6c17f6e17552eb6376a6d9a5b6c943c7
1 file changed
tree: 6b6153a79b1b550c3c51c8f5ff9567232ed9a5e9
  1. .gitignore
  2. Jenkinsfile
  3. README.md
  4. jenkins-docker/
  5. jenkins/
  6. vars/
  7. worker/
  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 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/