drupal-11/11.2.1 package update

[octo-sts]

[octo-sts]

🔄 Build Failed: Git Checkout Error

FAIL Expected commit 3072192bda268fcce6c22b5bd02935a508c41bb2 for 11.2.1, found 8d7c00164c4191bab8c2d6ea67ab61256112649f

Build Details

Category	Details
Build System	git
Failure Point	git checkout operation for drupal-11

Root Cause Analysis 🔍

The git tag 11.2.1 in the Drupal repository points to a different commit hash than what was expected in the build configuration. This suggests either the tag was moved in the upstream repository or there's an incorrect expected commit hash in the Wolfi package definition.

---

🔍 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

Suggested Changes

File: drupal-11.yaml

• replace at line 79 (pipeline git-checkout section)
  Original:

      expected-commit: 3072192bda268fcce6c22b5bd02935a508c41bb2

Replacement:

      expected-commit: 8d7c00164c4191bab8c2d6ea67ab61256112649f

Content:

Update the expected-commit hash to match the actual commit that the Drupal 11.2.1 tag points to

• replace at line 86 (pipeline git-checkout section (second checkout))
  Original:

      expected-commit: 3072192bda268fcce6c22b5bd02935a508c41bb2

Replacement:

      expected-commit: 8d7c00164c4191bab8c2d6ea67ab61256112649f

Content:

Update the expected-commit hash in the second git-checkout to match the actual commit that the Drupal 11.2.1 tag points to

Click to expand fix analysis

Analysis

The similar fixed build failure was related to a git tag pointing to a different commit hash than expected in the build configuration. In the GitLab Runner example, the fix was to update the expected-commit hash in the git-checkout pipeline step to match the actual commit that the tag pointed to. This is a common issue in Git-based build systems where tags might be moved or updated by upstream maintainers, or when tags point to tag objects rather than directly to commits.

Click to expand fix explanation

Explanation

The current build failure occurs because the git tag 11.2.1 in the Drupal repository points to commit 8d7c00164c4191bab8c2d6ea67ab61256112649f, but the build configuration is expecting it to point to commit 3072192bda268fcce6c22b5bd02935a508c41bb2.

This mismatch can happen for several reasons:

1. The upstream repository maintainers may have moved the tag to point to a different commit (perhaps after fixing an issue in the release)
2. The tag might be pointing to a tag object rather than directly to a commit
3. There could have been an error when initially recording the expected commit hash in the Wolfi package definition

The fix is straightforward: update the expected-commit values in both git-checkout steps to match the actual commit hash that the 11.2.1 tag now points to. This allows the build to proceed with the current state of the upstream repository. This is the same approach used in the similar fixed issue where the expected commit hash was updated to match the actual commit hash for the GitLab Runner tag.

This approach acknowledges that upstream repositories sometimes update their tags, and our build system needs to adapt to these changes rather than enforce a specific commit hash that might no longer be valid.

Click to expand alternative approaches

Alternative Approaches

• Reach out to the Drupal maintainers to understand why the tag was moved, if there were critical fixes that might warrant additional attention
• Add a verification step in the pipeline to check if the tag was moved intentionally by looking for signed tags or release notes
• Use a specific commit hash instead of a tag for more immutable builds, though this makes version updates more complex

---

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

[octo-sts]

superseded by #57653