Fix promote job: use explicit paths in metalink put step#403
Merged
Conversation
Concourse's inputs:detect cannot resolve glob patterns like compiled-linux-*/* to actual artifact names. Only version-semver was detected from the version param, so compiled-linux-amd64 and compiled-windows-amd64 task outputs were not mounted into the resource container. filepath.Glob() in the metalink resource's out script found zero files, producing a metalink with no <file> nodes, causing: 'bad metalink: content error: missing file node'. Replace globs with explicit directory names in the files param so inputs:detect can resolve them correctly.
KauzClay
approved these changes
Feb 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Concourse's inputs:detect cannot resolve glob patterns like
compiled-linux-*/*to actual artifact names. Only version-semver was detected from the version param, so compiled-linux-amd64 and compiled-windows-amd64 task outputs were not mounted into the resource container. filepath.Glob() in the metalink resource's out script found zero files, producing a metalink with no nodes, causing: 'bad metalink: content error: missing file node'.Replace globs with explicit directory names in the files param so inputs:detect can resolve them correctly.