Implement CI-based distribution

[ronaldtse]

We'd like to cross-compile the Riffol binary on different systems. Rust standard library depends on libc, which can be different on different Linux distros (Debian vs CentOS).

This task is to create a Jenkinsfile that can distribute standalone binaries that target different platforms.

Links:

• https://grahamenos.com/rust-osx-linux-musl.html
• https://os.phil-opp.com/freestanding-rust-binary/
• https://www.reddit.com/r/rust/comments/2geibf/how_to_distribute_programs_written_in_rust_as/

The resulting binaries should be distributed in the Releases section in this repo.

[drystone]

@ronaldtse I'm nearly there having spent a gruesome couple of days grappling with Jenkins and underpowered cloud hosts! It uses Jenkins and platform specific Docker agents.

The binaries are currently tested over each platform but not retained. Hopefully, once www.riffol.com is set up we can somehow post them over as part of this CI.

I've been using a private Jenkins instance for testing but would prefer to integrate into your Jenkins. Would you be able to do this?

Please close this issue if you're satisfied. Thanks :)

[ronaldtse]

@drystone for testing, we could use Travis and its matrices.

My intention for Jenkins was for the distribution of releases, especially on our own yum repo at https://github.com/riboseinc/yum

[drystone]

@ronaldtse, I guess we are going to need both in that case. Matrices would indeed be useful for testing and they appear broken in Jenkins - at least with a declarative Jenkinsfile.

Jenkins is a bit pointless at the moment as all it does is test. I suggest we leave it in as a basis for building packages and binary distribution - perhaps not add the GitHub hooks for the time being.

We could, however, hook both this and the Nereond repo to Travis so we can do the cross platform testing. I'll push some .travis.yml in the meantime.

[ronaldtse]

@drystone you're absolutely right. Let's use Travis to test. I think it's easy to package Riffol / Nereond in RPMs using Jenkins as long as the build flow allows it.