Add RPMs and DEBs to releases

[JonZeolla]

We should be able to automatically include artifacts such as RPMs and DEBs to our releases, using tags from the versions specified in the package.

This would provide an install method independent of zkg.

[JonZeolla]

Depends on #10

[ottobackwards]

I've done RPM installs of plugins, and we do zkg now. I don't know how I would mix the two. I wonder if there are any other folks who do?

[JonZeolla]

My thought is to appeal to environments that prefer to host packages and install using builtin tools. We could also add a zkg bundle to the releases?

[JonZeolla]

I know that there have been projects (one example here) which used metron-bro-plugin-kafka which made their own RPMs/DEBs.

[ottobackwards]

I know how to do it, but not in a zkg environment. IE> what would be the best practice? just deploy it? try running zkg after unpacking it? we should as on #development

[JonZeolla]

My plan was that the rpms and debs would provide an install method independent of zkg

[ottobackwards]

Ok, can you put that explicitly in the issue description?

[JonZeolla]

Done

[ottobackwards]

Maybe we should add "install" images for supported systems to our set. So that we can run quick tests to be sure the debs install in ubuntu? and centos?

[JonZeolla]

I agree that should be a part of this work. Since there aren't really hierarchies with GitHub issues what do you feel if we just make a list of issues and indicate which are blocked with a label, and be specific about the prereq issues in the first comment?

[ottobackwards]

sure

[ottobackwards]

that or a feature branch

[JonZeolla]

For a project this small I have a hard time with using longer lived feature branches, but if the scenario arises I'm fine with that too