commit | 4ce45656f5894a4ae5c048e0753a04b5ab10cae2 | [log] [tgz] |
---|---|---|
author | Andrew Geissler <geissonator@yahoo.com> | Wed Sep 10 13:57:54 2025 -0500 |
committer | Andrew Geissler <geissonator@yahoo.com> | Mon Sep 15 17:39:10 2025 +0000 |
tree | ed2fe4ef7109ac2169872cc58d8d5ed34a45b66e | |
parent | 1c84797d2cbb87f8b4abc3e2fc91966800e6f7d7 [diff] |
build-seed: add gb200nvl-obmc and remove palmetto Nvidia has provided a build server so add a system per their request. Palmetto was removed as it is no longer supported by IBM. Change-Id: Ia03affe3b6f879822552b1ce3c841e3c666a0f33 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.