upload to bintray

[caarlos0]

maybe it is a cool feature to add...

[bpicode]

...it is IMO. Bintray has a very nice API and many cool features beyond plain binary storage [1, 2]. In order to unlock some these one may have to add opkg/deb/rpm packaging to GoReleaser.

[1] https://blog.bintray.com/2016/07/12/developing-for-openwrt-bintray-has-an-opkg-for-you/
[2] https://blog.bintray.com/2014/12/16/hosting-debian-packages-on-bintray-rocks/

[suntong]

I gave it a try and it is pretty straightforward -- the second blog entry listed by @bpicode, https://blog.bintray.com/2014/12/16/hosting-debian-packages-on-bintray-rocks/, is still good, despite that it is published in year 2014.

I.e., basically, for Uploading and Publishing Debian release pacakge, the following is all it need, provided that you have created the Debian repo and package already:

curl -X PUT -T libmypack_0.0.1_i386.deb -umyuser:<API_KEY> 'https://api.bintray.com/content/myorg/myrepo/mypack/0.0.1/pool/main/m/mypack/libmypack_0.0.1_i386.deb;deb_distribution=mydist;deb_component=main;deb_architecture=i386,amd64;publish=1'

To create the Debian package entry within the given repo, it is as simple as:

curl -v -H "Content-Type: application/json" -u$mybintrayid:$mybintraykey https://api.bintray.com/packages/$mybintrayid/$mybintrayrepo-d '{"name":"libterm-screencolor-perl","desc":"This package...","licenses":["MIT","GPL-3.0"],"vcs_url":"https://github.com/bintray/bintray-examples","public_download_numbers":false}'

To create a Debian repo is also as simple as above, all explained clearly in above blog. And check also the Bintray Debian Repository Creation and Upload file using API for the condensed and practical version.

But I think goreleaser should assume that the repo already exist, and the only jobs need to do is to create the Debian package and then upload it, as explained above.

To change the goreleaser code it seems straightforward as well.

• duplicate pipeline/fpm/fpm.go as ./pipeline/bintray/bintray.go, as all the package info can all be obtained from the fpm configuration.
• create a internal/client/bintray.go that does CreateRelease (to create the Debian package), and Upload, both by using the above curl CLI code.

It is the internal piping, code organization, context.Context, releaseID, content, body etc, etc that really confuses me. Moreover, the .goreleaser.yml file needs to have a new entry bintray that accept BintrayUserName as the (only) configurable parameter. That part I have no idea yet. The mybintraykey should be define the same way as the GITHUB_TOKEN is defined, and is recommended to be called BINTRAY_API_KEY.

So I can only describe in high level what should be done, but cannot do it myself.
But you can see that there isn't much to do on the bintray cli side actually, for the magic to happen.

Hope someone can get this done soon.

Thanks

[mattstratton]

@suntong have you gotten this working in travis by any chance? I've tried using the example you gave - I can get it working in my local terminal, but when I attempt it in Travis it has all sorts of problems (it claims it cannot open the .deb file, etc, even though I do an ls in travis and it sees the file in dist just fine).

If you have an example of a working travis setup that would be grand.

[suntong]

Oh yeah, I had build a simple example after this, which was aimed for people to easily follow -- wireframe:

• how to use Continuous-Integration travis-ci to build and release binary executables (of all OS platforms) every time you do a git commit
• how to package the final tool as debian package and upload to your PPA on bintray, so that people can easily install and get your updates

[jorinvo]

Just leaving this here for reference: https://github.com/laher/goxc/blob/master/tasks/bintray.go
Guess we can have a look at this since it's basically what we wanna do.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.