| commit | 1a383f41977d68ae18f981caf7a64c4d5efc697c | [log] [tgz] |
|---|---|---|
| author | Antonio Barone <syntonyze@gmail.com> | Thu Jul 31 12:13:36 2025 +0300 |
| committer | Antonio Barone <syntonyze@gmail.com> | Thu Jul 31 12:22:08 2025 +0300 |
| tree | f5785f91419697eaf43d80d4b69bd6cdf89672bb | |
| parent | 356169507db1201934de6b661ec3400c72407ad7 [diff] |
Allow progressive console output to work without reloads
When a validation job starts, the Gerrit "Checks" tab links to the
`/job/Gerrit-verifier-pipeline/job/XX/YY/console` page, which uses
AJAX to fetch console output via the `.../logText/progressiveHtml`
endpoint.
Because this endpoint was not explicitly whitelisted, Jenkins returned
HTTP 403 responses, triggering repeated page reloads per the script logic:
if (rsp.status === 403) {
location.reload();
return;
}
This change whitelists the `progressiveHtml` endpoint so that console
output can be progressively appended to the page without triggering
reload loops.
Bug: Issue 435246546
Change-Id: I8e98a525704883c81e80fcc5d1f3c61379ad3bd8
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/