[JIRA] (OVIRT-757) [VDSM] Add Travis CI to vdsm github project
[ https://ovirt-jira.atlassian.net/browse/OVIRT-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] closed OVIRT-757. --- Resolution: Fixed working according to user, please reopen if needed. > [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: Barak Korren > > 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.6#100017) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-757) [VDSM] Add Travis CI to vdsm github project
[ https://ovirt-jira.atlassian.net/browse/OVIRT-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=22137#comment-22137 ] danken commented on OVIRT-757: -- Thanks. https://travis-ci.org/oVirt/vdsm/jobs/171955938 was triggered automatically right after I've merged a patch to vdsm's gerrit. > [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: Barak Korren > > 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) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: [JIRA] (OVIRT-757) [VDSM] Add Travis CI to vdsm github project
On Mon, Oct 31, 2016 at 11:36:04AM +0200, Barak Korren (oVirt JIRA) wrote: > > [ > https://ovirt-jira.atlassian.net/browse/OVIRT-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=22135#comment-22135 > ] > > Barak Korren commented on OVIRT-757: > > > Enabled travis on vds repo: > https://travis-ci.org/oVirt/vdsm > > Please check if it works for you Thanks. https://travis-ci.org/oVirt/vdsm/jobs/171955938 was triggered automatically right after I've merged a patch to vdsm's gerrit. ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-757) [VDSM] Add Travis CI to vdsm github project
[ https://ovirt-jira.atlassian.net/browse/OVIRT-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=22135#comment-22135 ] Barak Korren commented on OVIRT-757: Enabled travis on vds repo: https://travis-ci.org/oVirt/vdsm Please check if it works for you > [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: Barak Korren > > 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) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-757) [VDSM] Add Travis CI to vdsm github project
[ https://ovirt-jira.atlassian.net/browse/OVIRT-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-757: --- Status: In Progress (was: To Do) > [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: Barak Korren > > 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) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-757) [VDSM] Add Travis CI to vdsm github project
[ https://ovirt-jira.atlassian.net/browse/OVIRT-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren reassigned OVIRT-757: -- Assignee: Barak Korren (was: infra) > [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: Barak Korren > > 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) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-757) [VDSM] Add Travis CI to vdsm github project
[ https://ovirt-jira.atlassian.net/browse/OVIRT-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: [JIRA] (OVIRT-757) [VDSM] Add Travis CI to vdsm github project
On Sun, Oct 30, 2016 at 05:12:03PM +0200, eyal edri [Administrator] (oVirt JIRA) wrote: > > [ > https://ovirt-jira.atlassian.net/browse/OVIRT-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=22109#comment-22109 > ] > > eyal edri [Administrator] commented on OVIRT-757: > - > > Few questions: > > 1. Which tests will run there? same as check-patch/check-merged? It would be Vdsm's unit tests, which are also run by check-patch. > 2. How will the travis configuration be managed/configured vdsm source tree already has .travis.yml which github uses to trigger Travis runs > 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? 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. ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-757) [VDSM] Add Travis CI to vdsm github project
[ https://ovirt-jira.atlassian.net/browse/OVIRT-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=22109#comment-22109 ] eyal edri [Administrator] commented on OVIRT-757: - 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? > [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) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-757) [VDSM] Add Travis CI to vdsm github project
Nir Soffer created OVIRT-757: Summary: [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.383.2#100014) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
