Versioned binaries as debs for testing #423
Merged
+17
−10
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.
In addition to regular packages, we will publish extra ones, like
ghostferry-sharding_4bc2247. With this we will be able to install 2 packages with their binaries and they won't collide. This should allow for easier testing next versions.Tophat
Fetch deb packages from build and keep them in current directory - one for default build and one versioned (mind the architecture), I've attached example ones from release and current build, i.e.
ghostferry-sharding_1.1.0+20251002+4bc2247_arm64.debghostferry-sharding-1469325_1.1.0+20251216+1469325_arm64.debThen create following docker file
Build
podman build -f Dockerfile -t versioned-debs:latestThen run with
podman run -it versioned-debs:latest /bin/shand check we have all commands