Introduce nano-nightly dockerhub registry for live network builds #4513
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.
Currently we create live, beta and test network builds twice a week and each of them is published to docker hub.
On Dockerhub, builds for live network are described as "Nano Production Builds" while it also has non release builds, which may create confusion.
With this pull request, another dockerhub target
nano-nightly
is introducednanocurrency/nano-nightly
will have all non release builds (DB
andRC
builds)nanocurrency/nano
will only have the official release builds.I did the following tests:
DB build (run on
develop
branch withrelease_build=='false'
)Resulting docker tag gr0vity/nano-nightly:V27.0DB11
This is the github runner log
RC build (run on
releases/v27
branch withrelease_build=='false'
)Resulting docker tag gr0vity/nano-nightly:V27.0RC1
This is the github runner log
Release build (run on
releases/v27
branch withrelease_build=='true'
)Resulting docker tag gr0vity/nano:V27.0
This is the github runner log