Adding VersionStream for gitlab-runner-18.1

[octo-sts]

No description provided.

[octo-sts]

🔄 Build Failed: Git Checkout Error

FAIL Expected commit 4e717029caf97ec9d98fb87cfa7cee462ac0f81c for v18.1.0, found 0731d300775d6114bb4b5ffffc9f0f0af0005d37

Build Details

Category	Details
Build System	melange
Failure Point	git checkout step during melange build process

Root Cause Analysis 🔍

The build expected a specific commit hash (4e717029caf97ec9d98fb87cfa7cee462ac0f81c) for the tag v18.1.0, but found a different commit hash (0731d300775d6114bb4b5ffffc9f0f0af0005d37) when checking out the repository. This mismatch between expected and actual commit hashes caused the build to fail.

---

🔍 Build failure fix suggestions

Found similar build failures that have been fixed in the past and analyzed them to suggest a fix:

Similar PRs with fixes

• Adding VersionStream for gitlab-runner-17.11 #51032
• Adding VersionStream for gitlab-kas-17.8 #39813
• Adding VersionStream for gitlab-kas-17.9 #43405

Suggested Changes

File: gitlab-runner-18.1.yaml

• replace at line 31 (pipeline > git-checkout > expected-commit)
  Original:

      expected-commit: 4e717029caf97ec9d98fb87cfa7cee462ac0f81c

Replacement:

      expected-commit: 0731d300775d6114bb4b5ffffc9f0f0af0005d37

Content:

Update the expected-commit hash to match the actual commit hash for v18.1.0

Click to expand fix analysis

Analysis

After analyzing the similar fixed build failures, I've identified a common pattern: in all cases, the expected commit hash in the Melange YAML file didn't match the actual commit hash for the specified tag in the repository. The fixes consistently involved updating the expected-commit value in the git-checkout step to match the actual commit hash found for that tag.

This issue occurs because Git tags can sometimes point to tag objects rather than directly to commit objects, or because the tag reference may have changed over time. When a tag is annotated (not lightweight), it contains additional metadata and points to a tag object, which then points to the commit object.

In all three examples, the solution was to update the expected-commit value in the Melange YAML file to match the actual commit hash that the tag resolves to, rather than trying to change the tag or repository.

Click to expand fix explanation

Explanation

The build is failing because the Melange YAML file expects the tag v18.1.0 to point to commit 4e717029caf97ec9d98fb87cfa7cee462ac0f81c, but it actually points to commit 0731d300775d6114bb4b5ffffc9f0f0af0005d37. This mismatch causes the git-checkout step to fail with the error message "FAIL Expected commit 4e717029caf97ec9d98fb87cfa7cee462ac0f81c for v18.1.0, found 0731d300775d6114bb4b5ffffc9f0f0af0005d37".

The suggested fix updates the expected-commit value in the Melange YAML file to match the actual commit that the tag v18.1.0 points to. This is exactly the same approach used in all three similar fixed build failures examined (#51032, #39813, and #43405).

When the melange build process checks out the repository at tag v18.1.0, it will now expect commit hash 0731d300775d6114bb4b5ffffc9f0f0af0005d37, which matches the actual commit hash for that tag, allowing the build to proceed successfully.

This fix is simple, direct, and minimally invasive, addressing the root cause of the issue without introducing additional risks or changes to the build process.

Click to expand alternative approaches

Alternative Approaches

• An alternative approach would be to check out the repository using the specific commit hash (0731d300775d6114bb4b5ffffc9f0f0af0005d37) directly instead of using the tag v18.1.0. This would bypass the tag-to-commit resolution, but it would make the configuration less maintainable as it wouldn't clearly indicate which version is being built.
• Another approach would be to use a git command to resolve the tag to a commit hash dynamically during the build process, rather than hardcoding the expected commit hash. However, this would add complexity to the build process and wouldn't follow the established pattern used in the Wolfi OS package builds.

---

Was this comment helpful? Please use 👍 or 👎 reactions on this comment.