[ofiwg] Travis CI testing of libfabric and fabtests

[Jeff Squyres (jsquyres)]

On Oct 8, 2015, at 11:12 PM, Sean Hefty <sean.hefty at intel.com> wrote:
> 
> I've also enabled branch protection to the upstream trees.  Now that Travis CI is working, I'd like to propose that we require status checks to pass before pull requests can be merged.  The only drawback that I see to this is that there will be a small delay (~5-10 minutes) before simple pull requests can be merged.

Can you publish your Travis CI setup so that others can use it?

Optimally, it would be great if there could be CI testing for every provider.

We have a similar setup with Jenkins inside Cisco, but have not found the cycles to finish the setup.  The complication is that our Jenkins is behind the Cisco lab environment firewall.  This created two problems:

- Github can't ping our Jenkins when a new PR comes in; our Jenkins has to poll Github for changes
- The results of a Jenkins test are available via a local web server, which is obviously not available from the greater internet.  We half-finished a solution of publishing our results to gists (e.g., so that when a test fails, someone outside of Cisco can see the full stdout/stderr from the test to know *what* failed -- e.g., see https://gist.github.com/cisco-usnic-bot/2291186ea50354528bef)

At some point, we need to free up a little time to finish our Jenkins integration and start publishing the results of the tests back to the pull requests, etc.

-- 
Jeff Squyres
jsquyres at cisco.com
For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/