| commit | eae557cf65c82b4647fb7e3af2866b7025559fb0 | [log] [tgz] |
|---|---|---|
| author | Andrew Geissler <geissonator@yahoo.com> | Mon Oct 13 11:29:46 2025 -0500 |
| committer | Andrew Geissler <geissonator@yahoo.com> | Mon Oct 13 11:34:42 2025 -0500 |
| tree | e255ed846d57bf7707a8b2f52ba36b2ec4ff2701 | |
| parent | a0cb598e2f51e75a95418f0d87f783f9e35b39d6 [diff] |
build-unit-test-docker: utilize https for llvm install Some of our internal networks have started to completely block http. This llvm.sh script utilizes a http address by default for some wget commands. An issue[1] has been opened on the llvm project but for now just utilize a workaround to tell the script to use https. Tested: - Confirmed script now correctly builds in environment without http support [1]: https://github.com/llvm/llvm-project/issues/163216 Change-Id: Iadcb05e94480c3a91dc65c33e41f274ac545fd99 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Build script for CI jobs in Jenkins.
Formatting linters sometimes change stylistic output across releases. Separately, some linters are not version-pinned in the CI container, as pinning would drive either frequent maintenance with upgrades or stagnation of the code-base against older versions.
The combination may result in inconsistent formatting opinions across CI worker nodes[^1].
If you see such behaviour consider changing the thing to force a container refresh.
[^1]: The collection of container builds across all worker nodes may not hold a consistent set of tool versions despite being built from the same specification: The inconsistencies emerge from the cadence of upstream tool package updates beating against the cadence of container rebuilds on the worker nodes.