Repository navigation
Fix Jenkins artifact paths and surface download failures - #218
Merged
Merged
Conversation
Use Jenkins' artifact relativePath from the build API response instead of assuming every artifact is stored under an artifacts directory. This allows jobs such as Builders-Utilities to download artifacts from their actual build output location. Log the resolved download URL before transfer and report runtime failures during release preparation or download with the affected plugin name, so invalid artifact paths and other preparation errors are visible in the server log. Closes OakLoaf#141
OakLoaf
requested changes
Sep 28, 2026
OakLoaf
left a comment
OakLoaf
left a comment
Owner
There was a problem hiding this comment.
Just a compile-time error, this format will make it follow the same convention as the error logged above
…ater/PluginData.java Co-authored-by: Oak <55620516+OakLoaf@users.noreply.github.com>
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
2 participants
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.
Use Jenkins' artifact relativePath from the build API response instead of assuming every artifact is stored under an artifacts directory. This allows jobs such as Builders-Utilities to download artifacts from their actual build output location.
Log the resolved download URL before transfer and report runtime failures during release preparation or download with the affected plugin name, so invalid artifact paths and other preparation errors are visible in the server log.
Closes #141