| commit | 8cf2cdc7c0b9b170d78853451c4a290f78e00ec9 | [log] [tgz] |
|---|---|---|
| author | Paladox none <thomasmulhall410@yahoo.com> | Tue Oct 25 22:46:31 2022 +0000 |
| committer | Paladox none <thomasmulhall410@yahoo.com> | Wed Mar 22 22:37:42 2023 +0000 |
| tree | 377da96dfa950602c8ef8c9fcc2db015e3425989 | |
| parent | c1a45b54ad1d8407dec96ffb8aedef8fd7fa42f0 [diff] |
docker: generate chrome-vers.mk under agent-chrome build step * Fixes an issue where chrome-vers.mk is not created when building but was created when publishing which broke things. * Fixes an issue with generating chrome-vers.mk under a Mac. We use printf instead of echo, see [0]. * Make sure "latest" is inserted into chrome-vers.mk. The agent-bazel image uses chrome-vers.mk. Some images depended on agent-bazel and used "latest" but because "latest" wasn't in the file it failed to use the image. This issue is now fixed so that agent-bazel successfully creates a "latest" image locally. [0] https://stackoverflow.com/questions/11675070/makefile-echo-n-not-working Change-Id: I520a08d52c1dfda3e623be436682fcb03ab26212
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/