| commit | ecd354d3c71b061f7bdaec4ee23b77e14a0335f0 | [log] [tgz] |
|---|---|---|
| author | Andrew Geissler <geissonator@yahoo.com> | Mon Sep 29 08:55:16 2025 -0500 |
| committer | Andrew Geissler <geissonator@yahoo.com> | Mon Sep 29 08:55:16 2025 -0500 |
| tree | 1f2b8ec7208c5a9e7ead1bf3d3c8277f1e18a026 | |
| parent | 927ded2fe2a63bf639d00522ce67fe2d2be5e862 [diff] |
userid-validation: add scaleway CLA update has been processed and there is an active user in gerrit so add to approve list Change-Id: I5d05624bf6e623d30c6e6a52ce7c01051f9c5cd4 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.