[ https://ovirt-jira.atlassian.net/browse/OVIRT-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22122#comment-22122 ] danken commented on OVIRT-757: ------------------------------ It would be Vdsm's unit tests, which are also run by check-patch. vdsm source tree already has .travis.yml which github uses to trigger Travis runs We love jenkins CI and we don't want to replace it, only augment, with very little cost to the ovirt project. Travis has a nice look-and-feel; but more importantly, it keeps the outcome of jobs indefinitely. We'd like to see TravisCI for for the very same reason we have a github mirror to our gerrit: github provides a widely-used platform, that might be more approachable to the general public, even though I personally like it less.

[VDSM] Add Travis CI to vdsm github project -------------------------------------------

Key: OVIRT-757 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-757 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra

Hi all, Vdsm includes now a travis configuration running vdsm tests on both Fedora 24 and Centos 7. You can see example build shere: https://travis-ci.org/nirs/vdsm/builds/166263228 These builds are currently configured in my private vdsm fork on github. We want to enable Travis CI service on vdsm github project, so each time a patch is merged (sync from gerrit) or each time a pull request is submitted, a build is started. Developers can use these builds in 2 ways: - fork vdsm and enable travis on their fork - submit pull requests to get them tested When a build fails, travis sends email to the author about the failure, this works fine for developers forks without any additional configuration. You can configure github for us, or give Dan and/or me the permissions to configure the github project. Cheers, Nir

-- This message was sent by Atlassian JIRA (v1000.482.3#100017)