Generate .deb-packages as a part of release on travis

binarin commented 8 years ago

Plugins are installed to /usr/lib/rabbitmq/plugins/ - it will work transparently only with some future versions of rabbitmq (with https://github.com/rabbitmq/rabbitmq-server/pull/1016)

Open questions:

Is the package signing needed? On a plus side the same GPG keys can be used to provide a signature as requested in #107. Mechanisms are already in place, but it'll require some effort from you for generating a GPG key and converting it to the travis-accepted form
Should debian changelog be automatically generated, e.g. from a log of git commits? Or is it worth making its hand-crafted version, e.g. with the same descriptions that go into GitHub releases?

codecov-io commented 8 years ago

Current coverage is 41.71% (diff: 100%)

Merging #108 into master will not change coverage

@@             master       #108   diff @@
==========================================
  Files            13         13          
  Lines           513        513          
  Methods           0          0          
  Messages          0          0          
  Branches          0          0          
==========================================
  Hits            214        214          
  Misses          299        299          
  Partials          0          0

Powered by Codecov. Last update 9ed8213...75e6d3b

binarin commented 7 years ago

I've added automatic changelog generation, and fixed building of unsigned packages. Open questions can be resolved separately, but even in this form it already provides useful release artifacts.

aweber / rabbitmq-autocluster

Generate .deb-packages as a part of release on travis #108

Current coverage is 41.71% (diff: 100%)