[EnMasse] generated artifacts

[Rob Cernich]

> Here is a description of the enmasse CI:
> https://github.com/EnMasseProject/enmasse/tree/master/documentation/ci
> 
> It basically does build & test -> pushes to docker hub -> triggers
> systemtests which does a openshift deployment with enmasse + tests. I
> would prefer if we could keep the upstream community bits built and
> relased using travis + github.

Given that we're talking about doing builds for the artifacts going into the images, I think it would be fine to use jenkins to build the artifacts used within the images (e.g. the patched versions of qpid/proton).  This would create a clean separation between the images and the artifacts being installed in the images (which, btw, we'll need to do anyway once we get to productization).  The only issue I see with doing this in travis is that travis doesn't store build artifacts, and there's no real place to upload these artifacts.  So..hybrid approach, build the artifacts in jenkins; build the images in travis.  Also, I'm guessing you can use a webhook with travis so you can invoke a build upon completion of the jenkins job.

> 
> Setting up internal jenkins jobs to do these builds in addition would be
> nice. We have a messaging CI that we can use for that, but I'm currently
> awaiting some restructuring in the CI machines so that we can run
> systemtests against an internal openshift instance.
> 
>