| commit | 5906717d201a962a8e89e281529be1065a26944b | [log] [tgz] |
|---|---|---|
| author | Luca Milanesio <luca.milanesio@gmail.com> | Tue Oct 14 10:20:00 2025 -0700 |
| committer | Luca Milanesio <luca.milanesio@gmail.com> | Tue Oct 14 10:25:21 2025 -0700 |
| tree | a986c7c7f334ed6cbbf607beda81af9548ec6e30 | |
| parent | 00c958123214dbf7de9c59d1fbc365fca1562f77 [diff] |
Workaround to avoid a hard shutdown when testing the release When running the release on a Docker container with Debian, the start-stop-daemon is not able to send the HUP signal to the Gerrit JVM, causing the shutdown of the server with a KILL signal. Ending the JVM execution following a KILL does not respect the operations triggered during the shutdown sequence, including also the flushing of Lucene in-memory data. The result of using start-stop-daemon is therefore the disappearance of the changes created just before the shutdown, which was making the gerrit-upgrade-test.sh fail. Bug: Issue 450577969 Change-Id: Ia2c6bac3f1d8ed798a277f4e78e2cf29b627d7b3
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/