Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

[VDSM] Add Travis CI to vdsm github project

Description

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

Activity

Show:

Eyal Edri November 3, 2016 at 1:05 PM

working according to user, please reopen if needed.

danken October 31, 2016 at 11:24 AM

Thanks.

https://travis-ci.org/oVirt/vdsm/jobs/171955938 was triggered
automatically right after I've merged a patch to vdsm's gerrit.

Barak Korren October 31, 2016 at 9:35 AM

Enabled travis on vds repo:
https://travis-ci.org/oVirt/vdsm

Please check if it works for you

danken October 31, 2016 at 7:11 AM

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.

Eyal Edri October 30, 2016 at 3:11 PM

Few questions:

1. Which tests will run there? same as check-patch/check-merged?
2. How will the travis configuration be managed/configured
3. Why use another CI system when we can run it on jenkins.ovirt.org? is there any limitation to existing jenkins server that Travis doesn't have? can you elaborate?

Fixed

Details

Assignee

Reporter

Priority

Created October 9, 2016 at 8:14 PM
Updated November 29, 2016 at 12:18 PM
Resolved November 3, 2016 at 1:05 PM