- Infra - oVirt List Archives

[JIRA] (OVIRT-776) Re: Build failed in Jenkins: ovirt_4.0_he-system-tests #402
by Evgheni Dereveanchin (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-776?page=com.atlassian.jira.p… ] Evgheni Dereveanchin reassigned OVIRT-776: ------------------------------------------ Assignee: Evgheni Dereveanchin (was: infra) > Re: Build failed in Jenkins: ovirt_4.0_he-system-tests #402 > ----------------------------------------------------------- > > Key: OVIRT-776 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-776 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Evgheni Dereveanchin > > Looks like a network issue, scp fails with a timeout on a socket. > Can you please have a look? > On Mon, Oct 17, 2016 at 10:22 PM, <jenkins(a)jenkins.phx.ovirt.org> wrote: > > See <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/402/changes> > > > > Changes: > > > > [Gal Ben Haim] Fix check-patch to collect logs on failure > > > > ------------------------------------------ > > [...truncated 1897 lines...] > > ## took 2809 seconds > > ## rc = 1 > > ########################################################## > > ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv > > ##! Last 20 log enties: logs/mocker-fedora-23-x86_64. > > fc23.he_basic_suite_4.0.sh/he_basic_suite_4.0.sh.log > > ##! > > + true > > + env_cleanup > > + echo '#########################' > > ######################### > > + local res=0 > > + local uuid > > + echo '======== Cleaning up' > > ======== Cleaning up > > + [[ -e <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ > > ovirt-system-tests/deployment-he_basic_suite_4.0> ]] > > + echo '----------- Cleaning with lago' > > ----------- Cleaning with lago > > + lago --workdir <http://jenkins.ovirt.org/job/ > > ovirt_4.0_he-system-tests/ws/ovirt-system-tests/deployment- > > he_basic_suite_4.0> destroy --yes --all-prefixes > > + echo '----------- Cleaning with lago done' > > ----------- Cleaning with lago done > > + [[ 0 != \0 ]] > > + echo '======== Cleanup done' > > ======== Cleanup done > > + exit 0 > > Took 2642 seconds > > =================================== > > ##! > > ##! ERROR ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > ##!######################################################## > > ########################################################## > > Build step 'Execute shell' marked build as failure > > Performing Post build task... > > Match found for :.* : True > > Logical operation result is TRUE > > Running script : #!/bin/bash -xe > > echo 'shell_scripts/system_tests.collect_logs.sh' > > > > # > > # Required jjb vars: > > # version > > # > > VERSION=4.0 > > SUITE_TYPE= > > > > WORKSPACE="$PWD" > > OVIRT_SUITE="$SUITE_TYPE_suite_$VERSION" > > TESTS_LOGS="$WORKSPACE/ovirt-system-tests/exported-artifacts" > > > > rm -rf "$WORKSPACE/exported-artifacts" > > mkdir -p "$WORKSPACE/exported-artifacts" > > > > if [[ -d "$TESTS_LOGS" ]]; then > > mv "$TESTS_LOGS/"* "$WORKSPACE/exported-artifacts/" > > fi > > > > [ovirt_4.0_he-system-tests] $ /bin/bash -xe /tmp/ > > hudson4967817357021364058.sh > > + echo shell_scripts/system_tests.collect_logs.sh > > shell_scripts/system_tests.collect_logs.sh > > + VERSION=4.0 > > + SUITE_TYPE= > > + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/> > > + OVIRT_SUITE=4.0 > > + TESTS_LOGS=<http://jenkins.ovirt.org/job/ovirt_4.0_he- > > system-tests/ws/ovirt-system-tests/exported-artifacts> > > + rm -rf <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/402/ > > artifact/exported-artifacts> > > + mkdir -p <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/402/ > > artifact/exported-artifacts> > > + [[ -d <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ > > ovirt-system-tests/exported-artifacts> ]] > > + mv <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ > > ovirt-system-tests/exported-artifacts/lago_logs> < > > http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ > > ovirt-system-tests/exported-artifacts/nosetests-002_bootstrap.py.xml> < > > http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ > > ovirt-system-tests/exported-artifacts/nosetests-004_basic_sanity.py.xml> < > > http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ > > ovirt-system-tests/exported-artifacts/test_logs> < > > http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/402/ > > artifact/exported-artifacts/> > > POST BUILD TASK : SUCCESS > > END OF POST BUILD TASK : 0 > > Match found for :.* : True > > Logical operation result is TRUE > > Running script : #!/bin/bash -xe > > echo "shell-scripts/mock_cleanup.sh" > > > > shopt -s nullglob > > > > > > WORKSPACE="$PWD" > > > > # Make clear this is the cleanup, helps reading the jenkins logs > > cat <<EOC > > _______________________________________________________________________ > > ####################################################################### > > # # > > # CLEANUP # > > # # > > ####################################################################### > > EOC > > > > > > # Archive the logs, we want them anyway > > logs=( > > ./*log > > ./*/logs > > ) > > if [[ "$logs" ]]; then > > tar cvzf exported-artifacts/logs.tgz "${logs[@]}" > > rm -rf "${logs[@]}" > > fi > > > > # stop any processes running inside the chroot > > failed=false > > mock_confs=("$WORKSPACE"/*/mocker*) > > # Clean current jobs mockroot if any > > for mock_conf_file in "${mock_confs[@]}"; do > > [[ "$mock_conf_file" ]] || continue > > echo "Cleaning up mock $mock_conf" > > mock_root="${mock_conf_file##*/}" > > mock_root="${mock_root%.*}" > > my_mock="/usr/bin/mock" > > my_mock+=" --configdir=${mock_conf_file%/*}" > > my_mock+=" --root=${mock_root}" > > my_mock+=" --resultdir=$WORKSPACE" > > > > #TODO: investigate why mock --clean fails to umount certain dirs > > sometimes, > > #so we can use it instead of manually doing all this. > > echo "Killing all mock orphan processes, if any." > > $my_mock \ > > --orphanskill \ > > || { > > echo "ERROR: Failed to kill orphans on $chroot." > > failed=true > > } > > > > mock_root="$(\ > > grep \ > > -Po "(?<=config_opts\['root'\] = ')[^']*" \ > > "$mock_conf_file" \ > > )" || : > > [[ "$mock_root" ]] || continue > > mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || : > > if [[ "$mounts" ]]; then > > echo "Found mounted dirs inside the chroot $chroot. Trying to > > umount." > > fi > > for mount in "${mounts[@]}"; do > > sudo umount --lazy "$mount" \ > > || { > > echo "ERROR: Failed to umount $mount." > > failed=true > > } > > done > > done > > > > # Clean any leftover chroot from other jobs > > for mock_root in /var/lib/mock/*; do > > this_chroot_failed=false > > mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || : > > if [[ "$mounts" ]]; then > > echo "Found mounted dirs inside the chroot $mock_root." \ > > "Trying to umount." > > fi > > for mount in "${mounts[@]}"; do > > sudo umount --lazy "$mount" \ > > || { > > echo "ERROR: Failed to umount $mount." > > failed=true > > this_chroot_failed=true > > } > > done > > if ! $this_chroot_failed; then > > sudo rm -rf "$mock_root" > > fi > > done > > > > if $failed; then > > echo "Aborting." > > exit 1 > > fi > > > > # remove mock system cache, we will setup proxies to do the caching and > > this > > # takes lots of space between runs > > shopt -u nullglob > > sudo rm -Rf /var/cache/mock/* > > > > # restore the permissions in the working dir, as sometimes it leaves files > > # owned by root and then the 'cleanup workspace' from jenkins job fails to > > # clean and breaks the jobs > > sudo chown -R "$USER" "$WORKSPACE" > > > > [ovirt_4.0_he-system-tests] $ /bin/bash -xe /tmp/ > > hudson2195449912416509862.sh > > + echo shell-scripts/mock_cleanup.sh > > shell-scripts/mock_cleanup.sh > > + shopt -s nullglob > > + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/> > > + cat > > _______________________________________________________________________ > > ####################################################################### > > # # > > # CLEANUP # > > # # > > ####################################################################### > > + logs=(./*log ./*/logs) > > + [[ -n ./ovirt-system-tests/logs ]] > > + tar cvzf exported-artifacts/logs.tgz ./ovirt-system-tests/logs > > ./ovirt-system-tests/logs/ > > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.he_ > > basic_suite_4.0.sh/ > > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23. > > he_basic_suite_4.0.sh/he_basic_suite_4.0.sh.log > > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/ > > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23. > > install_packages/state.log > > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23. > > install_packages/build.log > > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23. > > install_packages/stdout_stderr.log > > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23. > > install_packages/root.log > > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/ > > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/state.log > > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/build.log > > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23. > > init/stdout_stderr.log > > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/root.log > > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.clean_rpmdb/ > > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23. > > clean_rpmdb/stdout_stderr.log > > + rm -rf ./ovirt-system-tests/logs > > + failed=false > > + mock_confs=("$WORKSPACE"/*/mocker*) > > + for mock_conf_file in '"${mock_confs[@]}"' > > + [[ -n <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ > > ovirt-system-tests/mocker-fedora-23-x86_64.fc23.cfg> ]] > > + echo 'Cleaning up mock ' > > Cleaning up mock > > + mock_root=mocker-fedora-23-x86_64.fc23.cfg > > + mock_root=mocker-fedora-23-x86_64.fc23 > > + my_mock=/usr/bin/mock > > + my_mock+=' --configdir=<http://jenkins.ovirt.org/job/ovirt_4.0_he- > > system-tests/ws/ovirt-system-tests'> > > + my_mock+=' --root=mocker-fedora-23-x86_64.fc23' > > + my_mock+=' --resultdir=<http://jenkins.ovirt.org/job/ovirt_4.0_he- > > system-tests/ws/'> > > + echo 'Killing all mock orphan processes, if any.' > > Killing all mock orphan processes, if any. > > + /usr/bin/mock --configdir=<http://jenkins.ovirt.org/job/ovirt_4.0_he- > > system-tests/ws/ovirt-system-tests> --root=mocker-fedora-23-x86_64.fc23 > > --resultdir=<http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/> > > --orphanskill > > WARNING: Could not find required logging config file: < > > http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ > > ovirt-system-tests/logging.ini.> Using default... > > INFO: mock.py version 1.2.18 starting (python version = 3.4.3)... > > Start: init plugins > > INFO: selinux enabled > > Finish: init plugins > > Start: run > > Finish: run > > ++ grep -Po '(?<=config_opts\['\''root'\''\] = '\'')[^'\'']*' < > > http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ > > ovirt-system-tests/mocker-fedora-23-x86_64.fc23.cfg> > > + mock_root=fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad > > + [[ -n fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad ]] > > + mounts=($(mount | awk '{print $3}' | grep "$mock_root")) > > ++ mount > > ++ awk '{print $3}' > > ++ grep fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad > > + : > > + [[ -n '' ]] > > + false > > + shopt -u nullglob > > + sudo rm -Rf /var/cache/mock/fedora-23-x86_64- > > 0c362156a2fa4a935ea8b988eb73b2ad > > + sudo chown -R jenkins <http://jenkins.ovirt.org/job/ > > ovirt_4.0_he-system-tests/ws/> > > POST BUILD TASK : SUCCESS > > END OF POST BUILD TASK : 1 > > Recording test results > > Archiving artifacts > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016> -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-757) [VDSM] Add Travis CI to vdsm github project
by danken (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-757?page=com.atlassian.jira.p… ] 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)

1 0

[JIRA] (OVIRT-757) [VDSM] Add Travis CI to vdsm github project
by Barak Korren (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-757?page=com.atlassian.jira.p… ] 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)

2 1

SSL Server Test: www.ovirt.org (Powered by Qualys SSL Labs)
by Yaniv Kaul 31 Oct '16

31 Oct '16

Someone tweeted about our incomplete certificate chain - see https://www.ssllabs.com/ssltest/analyze.html?d=www.ovirt.org

3 2

[JIRA] (OVIRT-761) Re: Do we or can we have Mac OS slaves in Jenkins?
by Juan Hernández (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-761?page=com.atlassian.jira.p… ] Juan Hernández commented on OVIRT-761: -------------------------------------- CC [~omachace(a)redhat.com] Travis CI integration for the Python SDK is now enabled. For future releases it would be good to make sure that the build in Mac OS X works before actually releasing the new version. > Re: Do we or can we have Mac OS slaves in Jenkins? > -------------------------------------------------- > > Key: OVIRT-761 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-761 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Barak Korren > > Opening a ticket. > On Mon, Oct 10, 2016 at 11:44 AM, Juan Hernández <jhernand(a)redhat.com> > wrote: > > Hello, > > > > Part of the Ruby SDK uses native code that needs to be compiled during > > installation of the gem. The Ruby SDK is a requirement of ManageIQ, and > > many ManageIQ developers/users use Mac OS. In the past I had some issues > > with this environment, as the C compiler there behaves in an slightly > > different way than GCC. Those issues were discovered only when the SDK > > was already released. To avoid that I would like to have Jenkins jobs > > building/testing the SDK for Mac OS. Is that possible? Do we have Mac OS > > slaves? If not, can we have them? > > > > Regards, > > Juan Hernandez > > > > -- > > Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta > > 3ºD, 28016 Madrid, Spain > > Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L. > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016> -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-798) outgoing mail failure - SPF fail
by eyal edri [Administrator] (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-798?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-798: ------------------------------------------------- We already got a few reports on this, [~duck][~sbendavi(a)redhat.com] can you have a look? > outgoing mail failure - SPF fail > -------------------------------- > > Key: OVIRT-798 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-798 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Hi, > When adding a reviewer to a patch on gerrit, I get an email: > The original message was received at Mon, 31 Oct 2016 05:07:32 -0400 > from gerrit.ovirt.org [127.0.0.1] > ----- The following addresses had permanent fatal errors ----- > <sbonazzo(a)redhat.com> > (reason: 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], > 'redhat.com'; REJECT) > ----- Transcript of session follows ----- > ... while talking to mx1.redhat.com.: > >>> DATA > <<< 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT > 550 5.1.1 <sbonazzo(a)redhat.com>... User unknown > <<< 554 5.5.1 Error: no valid recipients > Final-Recipient: RFC822; sbonazzo(a)redhat.com > Action: failed > Status: 5.7.1 > Remote-MTA: DNS; mx1.redhat.com > Diagnostic-Code: SMTP; 551 5.7.1 SPF fail: > 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT > Last-Attempt-Date: Mon, 31 Oct 2016 05:07:33 -0400 > Please check/handle. Thanks. > -- > Didi -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-798) outgoing mail failure - SPF fail
by Yedidyah Bar David (oVirt JIRA) 31 Oct '16

31 Oct '16

Yedidyah Bar David created OVIRT-798: ---------------------------------------- Summary: outgoing mail failure - SPF fail Key: OVIRT-798 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-798 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra Hi, When adding a reviewer to a patch on gerrit, I get an email: The original message was received at Mon, 31 Oct 2016 05:07:32 -0400 from gerrit.ovirt.org [127.0.0.1] ----- The following addresses had permanent fatal errors ----- <sbonazzo(a)redhat.com> (reason: 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT) ----- Transcript of session follows ----- ... while talking to mx1.redhat.com.: >>> DATA <<< 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT 550 5.1.1 <sbonazzo(a)redhat.com>... User unknown <<< 554 5.5.1 Error: no valid recipients Final-Recipient: RFC822; sbonazzo(a)redhat.com Action: failed Status: 5.7.1 Remote-MTA: DNS; mx1.redhat.com Diagnostic-Code: SMTP; 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT Last-Attempt-Date: Mon, 31 Oct 2016 05:07:33 -0400 Please check/handle. Thanks. -- Didi -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-757) [VDSM] Add Travis CI to vdsm github project
by Barak Korren (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-757?page=com.atlassian.jira.p… ] 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)

1 0

[JIRA] (OVIRT-757) [VDSM] Add Travis CI to vdsm github project
by Barak Korren (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-757?page=com.atlassian.jira.p… ] 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)

1 0

[JIRA] (OVIRT-790) 732846953375 infra-support
by eyal edri [Administrator] (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-790?page=com.atlassian.jira.p… ] eyal edri [Administrator] deleted OVIRT-790: -------------------------------------------- > 732846953375 infra-support > -------------------------- > > Key: OVIRT-790 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-790 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: m.kos(a)lycos.com > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0