jaeger-2/2.14.1 package update

[octo-sts]

Commit: 9173e343bfabb4ce8ff04d5b60c4d34058e5744a

Note: If you need to make manual changes to this PR, apply the skip:staging-update-bot label so the reconciler won't overwrite them.

[octo-sts]

⚙️ Build Failed: Configuration

cp: target 'cmd/query/app/ui/actual': No such file or directory

Build Details

Category	Details
Build System	Wolfi Linux package build system with npm/vite
Failure Point	cp -r jaeger-ui/packages/jaeger-ui/build/* cmd/query/app/ui/actual

Root Cause Analysis 🔍

The target directory 'cmd/query/app/ui/actual' does not exist when attempting to copy built UI assets. The build process successfully compiled the JavaScript/TypeScript components with npm and vite, but the subsequent file copy operation failed because the destination directory structure was not properly created or does not exist in the expected location.

---

🔍 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: melange.yaml

• modification at line pipeline[1].runs (subpackages[0].pipeline[1].runs)
  Original:

          ## Only run this step if building for all-in-one package
          ## This copies the build artifact into a go package
          COMPONENT="${{range.key}}"
          if [[ "$COMPONENT" = "all-in-one" ]]; then
            cp -r jaeger-ui/packages/jaeger-ui/build/* cmd/query/app/ui/actual
            find cmd/query/app/ui/actual -type f | grep -v .gitignore | xargs gzip --no-name
            touch -t "$(date -r jaeger-ui/packages/jaeger-ui/build/index.html '+%Y%m%d%H%M.%S')" cmd/query/app/ui/actual/index.html.gz
          fi

Replacement:

          ## Only run this step if building for all-in-one package
          ## This copies the build artifact into a go package
          COMPONENT="${{range.key}}"
          if [[ "$COMPONENT" = "all-in-one" ]]; then
            mkdir -p cmd/query/app/ui/actual
            cp -r jaeger-ui/packages/jaeger-ui/build/* cmd/query/app/ui/actual
            find cmd/query/app/ui/actual -type f | grep -v .gitignore | xargs gzip --no-name
            touch -t "$(date -r jaeger-ui/packages/jaeger-ui/build/index.html '+%Y%m%d%H%M.%S')" cmd/query/app/ui/actual/index.html.gz
          fi

Content:

Add 'mkdir -p cmd/query/app/ui/actual' before the cp command to ensure the target directory exists

Click to expand fix analysis

Analysis

No similar past fixes were provided, but analyzing the current build failure reveals the root cause: the target directory 'cmd/query/app/ui/actual' does not exist when attempting to copy built UI assets. The build process successfully compiles the JavaScript/TypeScript components but fails during the file copy operation because the destination directory structure is missing. This is a common issue in multi-step build processes where intermediate directories need to be created before file operations.

Click to expand fix explanation

Explanation

The fix addresses the root cause by ensuring the target directory 'cmd/query/app/ui/actual' exists before attempting to copy files into it. The 'mkdir -p' command creates the directory and any necessary parent directories if they don't exist, and the '-p' flag prevents errors if the directory already exists. This is placed immediately before the cp command that was failing, ensuring the directory structure is ready for the file copy operation. The rest of the pipeline remains unchanged, maintaining the existing build logic while fixing the missing directory issue.

Click to expand alternative approaches

Alternative Approaches

• Move the 'rm -rf cmd/query/app/ui/actual/*' and 'mkdir -p cmd/query/app/ui/actual' commands to the first pipeline step along with the npm build process
• Use 'cp -r jaeger-ui/packages/jaeger-ui/build cmd/query/app/ui/actual' instead of the wildcard approach, which would copy the entire build directory as a subdirectory
• Add error checking after the npm build step to verify the build output exists before attempting the copy operation

---

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

[debasishbsws]

Hey @srishtih are you working on this one seems like a major refactoring and you are assign to the ticket https://github.com/chainguard-dev/internal-dev/issues/25029 ?

[srishtih]

@debasishbsws I was working on jaeger-iamguarded, so there was some overlapping there.
Here's a PR that fixes the issue: #77198
There's also a thread in #customer-sucess about notifying existing customers of this change. Please feel free to take over this.

[aborrero]

marking as blocked as there are some refactors going on by @srishtih, see also https://chainguard-dev.slack.com/archives/C09PASNRT54/p1767878673440359

[AmberArcadia]

Closing due to stereo migration to reduce confusion