[ https://issues.apache.org/jira/browse/CASSANDRA-12622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Shuler updated CASSANDRA-12622: --------------------------------------- Fix Version/s: (was: 3.10) 3.x > Snap package of Cassandra > ------------------------- > > Key: CASSANDRA-12622 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12622 > Project: Cassandra > Issue Type: New Feature > Components: Packaging > Reporter: Evan > Priority: Minor > Fix For: 3.x > > > Picking up the conversation from [1], I'd like to propose that Cassandra > publish snap packages (http://snapcraft.io). > I've put together a patch: > https://github.com/apache/cassandra/compare/trunk...evandandrea:snap > This could be used to build and publish a snap on every commit to trunk [2, > 3], or as a quicker way for developers to one-off build something more > lightweight than a container for testing. > Alternatively, you could keep snap publication to released versions of > Cassandra. Dependencies are bundled, so you would get to decide Oracle vs > OpenJDK and the exact version. For the end user it would mean confidence that > Cassandra with this bundled set of dependencies had been tested by the > project. Uploads would instantly reach all of Ubuntu and a fair few other > distributions without any changes [4], hopefully simplifying install > instructions. > I couldn't find where the machinery for driving the Cassandra release process > lives, but if someone can point me in the right direction I'd be happy to > submit a patch for that. > 1: https://www.mail-archive.com/dev@cassandra.apache.org/msg09216.html > 2: Builds of trunk would be best published to the edge channel: > http://snapcraft.io/#snapcraft_home_using-snaps_channels > 3: What automatic building and publishing could look like using Travis: > https://travis-ci.org/evandandrea/cassandra-snap/builds/158449135#L3937 > 4: http://snapcraft.io/docs/core/install -- This message was sent by Atlassian JIRA (v6.3.4#6332)