Adding VersionStream for argo-cd-3.3

[octo-sts]

No description provided.

[octo-sts]

❓ Build Failed: Unknown

Unable to handle package argo-cd version 3.3... Failed to run command "/bin/sh -c 'set -e \n[ -d /home/build ] || mkdir -p /home/build\ncd /home/build\nset -euo pipefail\ncd "./.iamguarded-tools"\n./compat/build.sh "/home/build/melange-out/argo-cd-3.3-iamguarded-compat" "chainguard-dev/iamguarded-containers" "argo-cd" "3.3"\n\nexit 0'": Process exited with status 1

Build Details

Category	Details
Build System	melange
Failure Point	./compat/build.sh script execution in iamguarded-tools

Root Cause Analysis 🔍

The iamguarded-tools compat/build.sh script failed during execution for argo-cd version 3.3. The script was unable to handle this specific package version, but the exact reason for failure is not visible in the logs as the detailed error output from the script is not shown.

---

🔍 Build failure fix suggestions

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

Suggested Changes

File: argo-cd-3.3.yaml

• modification at line 13-16 (var-transforms section)
  Original:

var-transforms:
  - from: ${{package.version}}
    match: ^(\d+\.\d+)\.\d+$
    replace: "$1"
    to: major-minor-version

Replacement:

var-transforms:
  - from: ${{package.version}}
    match: ^(\d+\.\d+)\.\d+$
    replace: "$1"
    to: major-minor-version
  - from: ${{package.version}}
    match: ^(\d+\.\d+)\.\d+$
    replace: "$1.0"
    to: major-minor-patch-version

Content:

Add a new variable transform to create a three-part version number that the iamguarded tools might expect

• modification at line 125-128 (iamguarded-compat subpackage pipeline)
  Original:

      - uses: iamguarded/build-compat
        with:
          package: argo-cd
          version: ${{vars.major-minor-version}}

Replacement:

      - uses: iamguarded/build-compat
        with:
          package: argo-cd
          version: ${{vars.major-minor-patch-version}}

Content:

Use the three-part version number for iamguarded compatibility

• modification at line 141-144 (iamguarded-compat subpackage finalize step)
  Original:

      - uses: iamguarded/finalize-compat
        with:
          package: argo-cd
          version: ${{vars.major-minor-version}}

Replacement:

      - uses: iamguarded/finalize-compat
        with:
          package: argo-cd
          version: ${{vars.major-minor-patch-version}}

Content:

Use the three-part version number for iamguarded finalization

• modification at line 147-150 (iamguarded-compat subpackage test step)
  Original:

        - uses: iamguarded/test-compat
          with:
            package: argo-cd
            version: ${{vars.major-minor-version}}

Replacement:

        - uses: iamguarded/test-compat
          with:
            package: argo-cd
            version: ${{vars.major-minor-patch-version}}

Content:

Use the three-part version number for iamguarded testing

Click to expand fix analysis

Analysis

No similar build failures were found in the historical data, so I cannot identify patterns from past fixes. However, based on the error indicating that the iamguarded-tools compat/build.sh script failed to handle argo-cd version 3.3, this appears to be an issue with the iamguarded compatibility layer not recognizing or properly processing the version format "3.3" rather than a typical build compilation error.

Click to expand fix explanation

Explanation

The iamguarded-tools compat/build.sh script is failing to handle argo-cd version "3.3" because it likely expects a three-part semantic version (major.minor.patch) rather than a two-part version. The current var-transforms section creates a major-minor-version variable with value "3.3", but the iamguarded tools may be expecting a format like "3.3.0".

By adding a new variable transform that creates a three-part version (major-minor-patch-version) and using this in all iamguarded-related steps, we ensure the iamguarded tools receive a version format they can properly handle. This approach maintains backward compatibility while providing the expected version format to the iamguarded compatibility layer.

Click to expand alternative approaches

Alternative Approaches

• Modify the iamguarded/build-compat pipeline step to explicitly handle two-part version numbers by adding a conditional check
• Update the package version itself to use the full 3.3.0 format throughout instead of relying on variable transforms
• Add error handling in the pipeline to catch and retry with different version formats if the first attempt fails

---

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