This was just for debugging actually, but I believe it might help in the future.
input parameters to the build.sh script
This allows for using the script also from other repos. I'd like to keep trying things without having to ask you for checking in Drone.io...
This is probably related to #5, because if we introcude the nightly tag, the current check might fail.
This introduces:
* an explicit check for the existence of the latest version tag
* This way, we don't need to bother to have `nightly` or `dev` tags in place. The new check works by `curl` failing, if the target tag does not exist. Source: https://stackoverflow.com/questions/32113330/check-if-imagetag-combination-already-exists-on-docker-hub
* more verbose output
* This was just for debugging actually, but I believe it might help in the future.
* input parameters to the `build.sh` script
* This allows for using the script also from other repos. I'd like to keep trying things without having to ask you for checking in Drone.io...
This is probably related to #5, because if we introcude the `nightly` tag, the current check might fail.
This introduces:
* an explicit check for the existence of the latest version tag
* This way, we don't need to bother to have `nightly` or `dev` tags in place. The new check works by `curl` failing, if the target tag does not exist.
* more verbose output
* This was just for debugging actually, but I believe it might help in the future.
* input parameters to the `build.sh` script
* This allows for using the script also from other repos. I'd like to keep trying things without having to ask you for checking in Drone.io...
This introduces:
nightlyordevtags in place. The new check works bycurlfailing, if the target tag does not exist. Source: https://stackoverflow.com/questions/32113330/check-if-imagetag-combination-already-exists-on-docker-hubbuild.shscriptThis is probably related to #5, because if we introcude the
nightlytag, the current check might fail.