Epic Goal

• Make all cloud infra team repositories have consistent build version encoding, utilizing the best practices as defined by ART. All components should use the "OS_GIT_VERSION" environment variable as the primary source of truth, with "git describe" and clear failure messages as the backups.

Why is this important?

• Having consistent and repeatable builds ensures that the release pipelines will run smoothly. In scenarios where our build scripts are not utilizing the latest build configurations we run the risk of build system failures which lead to regressions in the creation of valid release payloads.

Scenarios

1. A recent slack thread from sdodson_jira highlights the possibility for our build scripting to fail when there are inconsistencies, or flakes, with our build infrastructure. If our build scripts had better redundancies, in the form of utilizing different version variables, then the build pipeline would have been more durable to pipeline failures.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• All team repositories that have built components for the release payload utilize the "OS_GIT_VERSION" environment variable when injecting a version in the compilation commands.

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. This CVO PR Bug 1826349: hack/build-go: Use OS_GIT_VERSION if available contains a good example.

Open questions::

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• DEV - Downstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>