run install tests and CI on all packaging changes

[jodh-intel]

To avoid the situation where a set of packages cannot be installed / upgraded to (#98), we need to find a way to test every packaging change.

Adding a CI test for Ubuntu + Fedora to install the latest OBS testing packages would give us a level of confidence that what is about to become stable is installable.

[jodh-intel]

I think we need to find a solution to this so that our process becomes:

• Create a release by tagging all the appropriate component repos.

  The code at tag $release is known to be good as we know that master builds for each component.

• Create the packages for the release in the OBS staging area.

• Ideally, run a full CI on every distro version we package for (Centos 7.x, Fedora 27, Ubuntu 16.04, etc) under Jenkins.

• Decide if the release should be promoted from staging -> master in OBS.

  Essentially, the questions is which of the following do we want:

  • Require the CI to pass for a particular distro version before that distro versions packages are promoted from staging -> master.
  • Require all the CI results to pass before any distro version is promoted from staging -> master.

  The second option is clearly stricter but also is a lot clearer from a users perspective as it guarantees that each release is always going to be available for all distro versions we package for.

---

The above will also require that we change the scripts in:

• https://github.com/clearcontainers/tests/tree/master/.ci/

... so that we install all components from the OBS staging repo using apt / dnf / etc. Maybe setting a variable in the Jenkins environment like CC_PACKAGING_TEST=true or something so that the scripts can change behaviour based on that value.

wdyt @erick0z, @chavafg, @jcvenegas, @grahamwhaley, @sameo?