Publish binaries for releases

[metalmatze]

Hey!
I really enjoy packr and use it on over 10+ projects now. During my CI/CD I sometimes need to go get packr, which is rather annoying because it takes a minute. It would be super dope, if you could provide some pre-build binaries (linux-amd64 for me). That way I could just curl them in my CI/CD and that's it.
Thanks!

[markbates]

That would be great. A PR would be awesome.

[metalmatze]

How would I do a PR so you can upload the binaries? Are you talking about Travis? 🤔

[markbates]

Yeah, I’m not quite sure how to go about it. My guess would be that we would use travis to build binaries and then push those to GitHub somehow.

…

----------- Mark Bates

On Dec 6, 2017, 1:19 PM -0600, Matthias Loibl ***@***.***>, wrote: How would I do a PR so you can upload the binaries? Are you talking about Travis? 🤔 — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[metalmatze]

Yep. I do that with drone a lot. I'll just have to take a look on how to do it with Travis when tagging. 😎

[markbates]

You are awesome!

[markbates]

The command "GOARCH=amd64 GOOS=darwin go build -v -o packr_darwin_amd64 ./packr" exited with 0.
Skipping a deployment with the releases provider because a custom condition was not met

[metalmatze]

Yes. The condition is, that it is only run iff a release was tagged with git tag

[markbates]

Not working. :(

https://travis-ci.org/gobuffalo/packr/jobs/312706654

I tagged that on using git tag v1.9.3 and then did git push origin --tags. Travis picked it up, built them, but didn't deploy them. Thoughts?

[metalmatze]

It might be this line which prevents the build from running that step.
But we need that due to the matrix of running the builds with different Go versions. We only want to push the binaries built with Go 1.9.

packr/.travis.yml

Line 29 in 782425e

condition: $TRAVIS_GO_VERSION =~ ^1\.9\.[0-9]+$