Provide binary as releases about docker-machine-driver-hetzner HOT 9 CLOSED

https://docs.travis-ci.com/user/deployment/releases/ documents how to release to Github using Travis. I might give it a try in my fork.

from docker-machine-driver-hetzner.

Well, I cannot look into it till thursday, so if you could have a look, @monochromata, it'd be much appreciated

from docker-machine-driver-hetzner.

@monochromata maybe some tools / commands, which could help you:

• mkdir releases
• https://github.com/mitchellh/gox => gox -output="releases/{{.Dir}}_{{.OS}}_{{.Arch}}/{{.Dir}}" (creates the binary files of all architectures)
• find releases -maxdepth 1 -mindepth 1 -type d -exec tar -cvzf {}.tar.gz {} \; (creates tar.gz archives of the gox output binary folders and strips the first directory)
• add all releases/*tar.gz to the GitHub release

from docker-machine-driver-hetzner.

Ok, thanks to Max' help, I created a first release with binaries from Travis: https://github.com/monochromata/docker-machine-driver-hetzner/releases/tag/0.2.3 . The comments in .travis.yml explain how to modify the .travis.yml file to work in this repo when merged.

There are a number of open points left:

• Add version number (from tag) to tar.gz file names
• shorten the path in the tarball (currently: releases/docker-machine-driver-hetzner__/docker-machine-driver-hetzner)
• I didn't test the tarball yet
• The README needs to be adjusted

from docker-machine-driver-hetzner.

Hi,
That's super cool :)
I've created PRs for adding the version number to the tar archive and stripping the path away in the tarball. When you create a test release, I can test it with Rancher to check if it works fine.
Tomorrow I will also add some documentation to the readme.
Best regards
Max

from docker-machine-driver-hetzner.

Great: https://github.com/monochromata/docker-machine-driver-hetzner/releases/tag/0.2.4

• I now tried the linux/amd64 binary and was able to use it to create a new server :-)
• The tarball is fine except it now contains a directory called "." I didn't find a quick work-around for that.

from docker-machine-driver-hetzner.

Both should be done with the PRs in your repository. :)

from docker-machine-driver-hetzner.

Ok, it's done so far. The tar command is a bit ugly now (it outputs error messages because I added an extra docker-machine-driver-hetzner.exe which is missing for Unix builds, while docker-machine-driver-hetzner is missing for the Windows builds), but it works :-).

Thanks again, Max!

from docker-machine-driver-hetzner.

@monochromata Thanks to you too, it was a lot of fun. So should open source development be in 2018 👍

from docker-machine-driver-hetzner.