fix: include tarballs in snapshot artifact upload by matching on version#286
Merged
bastelfreak merged 1 commit intoOpenVoxProject:mainfrom Apr 30, 2026
Merged
Conversation
Signed-off-by: Simon Lauger <simon@lauger.de>
nmburgan
approved these changes
Apr 29, 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
3 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.
The
vox:uploadrake task fails to upload tarballs for snapshot builds because the tarball filename uses a different version format than RPM/DEB packages.ezbake generates the tarball name from the git tag (e.g.
8.13.0.SNAPSHOT.2026...) while RPM/DEB packages use the version-release format fromezbake.rb(e.g.8.13.0-0.1SNAPSHOT.2026...). The existing glob only matches the version-release format, so the tarball is never found and not uploaded to S3.This adds a separate glob that matches tarballs by version, covering both naming conventions. Tagged releases are not affected since the glob already matches those correctly.