- Infra - oVirt List Archives

[JIRA] (OVIRT-998) Re: Enable Github gh-pages for project ovirt-engine-api-model
by eyal edri [Administrator] (oVirt JIRA) 03 Jan '17

03 Jan '17

eyal edri [Administrator] created OVIRT-998: ----------------------------------------------- Summary: Re: Enable Github gh-pages for project ovirt-engine-api-model Key: OVIRT-998 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-998 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: eyal edri [Administrator] Assignee: infra Sending ticket to infra-support. Pavel - let me know if you need help, its just clicking on the gh-pages generate button on GitHub ( last time we did it for SDK ) On Mon, Jan 2, 2017 at 11:43 PM, Juan Hernández <jhernand(a)redhat.com> wrote: > Hello, > > In order to have a public and stable location for the documentation of > the API I would like to start using the Github gh-pages mechanism. I > have already created a 'gh-pages' branch in the 'ovirt-engine-api-model' > project, and merged to that branch the first version of the > documentation. The next step is to enable the use of that 'gh-pages' > branch as the source of the documentation in the settins of that > project. But that needs to be done by an administrator of the oVirt > organization. Would you be so kind to do that? > > Thanks in advance, > Juan Hernandez > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > > > -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

Enable Github gh-pages for project ovirt-engine-api-model
by Juan Hernández 03 Jan '17

03 Jan '17

Hello, In order to have a public and stable location for the documentation of the API I would like to start using the Github gh-pages mechanism. I have already created a 'gh-pages' branch in the 'ovirt-engine-api-model' project, and merged to that branch the first version of the documentation. The next step is to enable the use of that 'gh-pages' branch as the source of the documentation in the settins of that project. But that needs to be done by an administrator of the oVirt organization. Would you be so kind to do that? Thanks in advance, Juan Hernandez

2 1

oVirt infra daily report - unstable production jobs - 188
by jenkins＠jenkins.phx.ovirt.org 02 Jan '17

02 Jan '17

------=_Part_77_1317460797.1483398061112 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/188//artifact/exported-a… Cheers, Jenkins ------=_Part_77_1317460797.1483398061112 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 02/01/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental_3.6/">deploy-to-ovirt_experimental_3.6</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-master-experimental_build-…">ovirt-node-ng_ovirt-master-experimental_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-fc24-x86…">ovirt-system-tests_master_check-patch-fc24-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/">ovirt_3.6_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_3.6_image-ng-system-tests/">ovirt_3.6_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/system-backup_jenkins_old_ovirt_org/">system-backup_jenkins_old_ovirt_org</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_77_1317460797.1483398061112--

1 0

[JIRA] (OVIRT-973) nightly ovirt-engine build is missing Chrome permutation
by eyal edri [Administrator] (oVirt JIRA) 02 Jan '17

02 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-973?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-973: ------------------------------------------------- You can easily send a patch to build-artifacts with the permutations you want and then use the 'build-on-demand' job using 'ci please build' to build rpms using the new PARAMS. > nightly ovirt-engine build is missing Chrome permutation > -------------------------------------------------------- > > Key: OVIRT-973 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-973 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Greg Sheremeta > Assignee: infra > > mburman [reports|https://bugzilla.redhat.com/show_bug.cgi?id=1400010] that the nightly ovirt-engine build is missing the Chrome permutation. > From the [build|http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-…] > {noformat} > 21:13:24 [INFO] Compiling 1 permutation > 21:13:24 [INFO] Compiling permutation 0... > 21:16:54 [INFO] Compile of permutations succeeded > {noformat} > That should compile 2 if we want Firefox and Chrome, or 3 if we also want IE. > mburman reports this started on November 30. I'm not sure what changed. > Adding build flags will fix: > DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS="-Dgwt.userAgent=safari,gecko1_8" -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-973) nightly ovirt-engine build is missing Chrome permutation
by eyal edri [Administrator] (oVirt JIRA) 02 Jan '17

02 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-973?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-973: ------------------------------------------------- How much time it will add if we'll add chrome to the permutations? I wouldn't want to pay a constant time penalty just because a single manual test needed it. > nightly ovirt-engine build is missing Chrome permutation > -------------------------------------------------------- > > Key: OVIRT-973 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-973 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Greg Sheremeta > Assignee: infra > > mburman [reports|https://bugzilla.redhat.com/show_bug.cgi?id=1400010] that the nightly ovirt-engine build is missing the Chrome permutation. > From the [build|http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-…] > {noformat} > 21:13:24 [INFO] Compiling 1 permutation > 21:13:24 [INFO] Compiling permutation 0... > 21:16:54 [INFO] Compile of permutations succeeded > {noformat} > That should compile 2 if we want Firefox and Chrome, or 3 if we also want IE. > mburman reports this started on November 30. I'm not sure what changed. > Adding build flags will fix: > DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS="-Dgwt.userAgent=safari,gecko1_8" -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-997) master/latest.tested and 4.1/latest.tested are not populated with nightly builds of ovirt-provider-ovn
by Pavel Zhukov (oVirt JIRA) 02 Jan '17

02 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-997?page=com.atlassian.jira.p… ] Pavel Zhukov reassigned OVIRT-997: ---------------------------------- Assignee: eyal edri [Administrator] (was: infra) > master/latest.tested and 4.1/latest.tested are not populated with nightly builds of ovirt-provider-ovn > ------------------------------------------------------------------------------------------------------ > > Key: OVIRT-997 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-997 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: danken > Assignee: eyal edri [Administrator] > -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-997) master/latest.tested and 4.1/latest.tested are not populated with nightly builds of ovirt-provider-ovn
by Pavel Zhukov (oVirt JIRA) 02 Jan '17

02 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-997?page=com.atlassian.jira.p… ] Pavel Zhukov commented on OVIRT-997: ------------------------------------ [~danken(a)redhat.com] The explanation why it happens is here: {quote}The idea of repoman is to 1. Take all the sources. 2. Filter each of them. 3. Join the packages after filters together and form the repo. In this case we use several sources S(1), S(2), ... S(N) each with "only-missing" filter. When only-missing filter is used for each S(N+1) it checks if package with such name is already sourced from S(N) and it is there then it will skip the addition. No version comparison is done for "only-missing" and it is as expected as the idea of the filter is to append missing packages. I think you need to use "latest" filter instead of "only-missing", e.g. "latest=1" will keep only latest version of each package from the source. Then if several source have the same package it will take 1 latest version from each and it should be safe as yum/dnf will install the latest version from compose.{quote} https://gerrit.ovirt.org/#/c/68788/2 If several sources are used you have to use latest=1 parameter. Otherwise only first artifact will be used. > master/latest.tested and 4.1/latest.tested are not populated with nightly builds of ovirt-provider-ovn > ------------------------------------------------------------------------------------------------------ > > Key: OVIRT-997 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-997 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: danken > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-997) master/latest.tested and 4.1/latest.tested are not populated with nightly builds of ovirt-provider-ovn
by Pavel Zhukov (oVirt JIRA) 02 Jan '17

02 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-997?page=com.atlassian.jira.p… ] Pavel Zhukov commented on OVIRT-997: ------------------------------------ [~amarchuk] any ideas why it happens? Does repoman filter unsigned rpms? > master/latest.tested and 4.1/latest.tested are not populated with nightly builds of ovirt-provider-ovn > ------------------------------------------------------------------------------------------------------ > > Key: OVIRT-997 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-997 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: danken > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-997) master/latest.tested and 4.1/latest.tested are not populated with nightly builds of ovirt-provider-ovn
by Pavel Zhukov (oVirt JIRA) 02 Jan '17

02 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-997?page=com.atlassian.jira.p… ] Pavel Zhukov commented on OVIRT-997: ------------------------------------ Seems like they're filtered out by repoman: 5179:2017-01-02 13:01:44,542::INFO::repoman.common.stores.RPM.add_rpm:248::Adding package /srv/resources/repos/ovirt/experimental/master/latest.tested/rpm/fc24/noarch/ovirt-provider-ovn-1.0-1.20161229142547.git17e7bc0.fc24.noarch.rpm to repo Non persistent RPMStore 5196:2017-01-02 13:01:44,553::INFO::repoman.common.stores.RPM.add_rpm:248::Adding package /srv/resources/repos/ovirt/experimental/master/latest.tested/rpm/fc24/noarch/ovirt-provider-ovn-driver-1.0-1.20161229142547.git17e7bc0.fc24.noarch.rpm to repo Non persistent RPMStore 5484:2017-01-02 13:01:44,889::INFO::repoman.common.stores.RPM.add_rpm:248::Adding package /srv/resources/repos/ovirt/experimental/master/latest.tested/rpm/el7/noarch/ovirt-provider-ovn-driver-1.0-1.el7.centos.noarch.rpm to repo Non persistent RPMStore 5493:2017-01-02 13:01:44,895::INFO::repoman.common.stores.RPM.add_rpm:248::Adding package /srv/resources/repos/ovirt/experimental/master/latest.tested/rpm/el7/noarch/ovirt-provider-ovn-1.0-1.el7.centos.noarch.rpm to repo Non persistent RPMStore 5905:2017-01-02 13:01:51,296::INFO::repoman.common.stores.RPM.add_rpm:248::Adding package /srv/resources/repos/ovirt/experimental/master/latest/rpm/fc24/noarch/ovirt-provider-ovn-1.0-1.20161229142547.git17e7bc0.fc24.noarch.rpm to repo Non persistent RPMStore 5922:2017-01-02 13:01:51,314::INFO::repoman.common.stores.RPM.add_rpm:248::Adding package /srv/resources/repos/ovirt/experimental/master/latest/rpm/fc24/noarch/ovirt-provider-ovn-driver-1.0-1.20161229142547.git17e7bc0.fc24.noarch.rpm to repo Non persistent RPMStore 6211:2017-01-02 13:01:51,727::INFO::repoman.common.stores.RPM.add_rpm:248::Adding package /srv/resources/repos/ovirt/experimental/master/latest/rpm/el7/noarch/ovirt-provider-ovn-driver-1.0-1.el7.centos.noarch.rpm to repo Non persistent RPMStore 6220:2017-01-02 13:01:51,738::INFO::repoman.common.stores.RPM.add_rpm:248::Adding package /srv/resources/repos/ovirt/experimental/master/latest/rpm/el7/noarch/ovirt-provider-ovn-1.0-1.el7.centos.noarch.rpm to repo Non persistent RPMStore 10902:2017-01-02 13:02:03,952::DEBUG::repoman.common.artifact.get_artifacts:351::ArtifactList::Iterating ArtifactName {'1.0-1.20161229142547.git17e7bc0': {17041649: [rpm(ovirt-provider-ovn.fc24.noarch 1.0 1.20161229142547.git17e7bc0.fc24 noarch bin unsigned), rpm(ovirt-provider-ovn.fc24.noarch 1.0 1.20161229142547.git17e7bc0.fc24 noarch bin unsigned)]}} 10908:2017-01-02 13:02:03,953::DEBUG::repoman.common.artifact.get_artifacts:205::ArtifactVersion::Iterating ArtifactInode [rpm(ovirt-provider-ovn.fc24.noarch 1.0 1.20161229142547.git17e7bc0.fc24 noarch bin unsigned), rpm(ovirt-provider-ovn.fc24.noarch 1.0 1.20161229142547.git17e7bc0.fc24 noarch bin unsigned)] 10909:2017-01-02 13:02:03,953::DEBUG::repoman.common.artifact.get_artifacts:164::ArtifactInode::[rpm(ovirt-provider-ovn.fc24.noarch 1.0 1.20161229142547.git17e7bc0.fc24 noarch bin unsigned), rpm(ovirt-provider-ovn.fc24.noarch 1.0 1.20161229142547.git17e7bc0.fc24 noarch bin unsigned)] 10910:2017-01-02 13:02:03,953::DEBUG::repoman.common.artifact.get_artifacts:166::ArtifactInode::arts=[rpm(ovirt-provider-ovn.fc24.noarch 1.0 1.20161229142547.git17e7bc0.fc24 noarch bin unsigned), rpm(ovirt-provider-ovn.fc24.noarch 1.0 1.20161229142547.git17e7bc0.fc24 noarch bin unsigned)] 10913:2017-01-02 13:02:03,953::DEBUG::repoman.common.artifact.get_artifacts:175::ArtifactInode::after filter arts=[rpm(ovirt-provider-ovn.fc24.noarch 1.0 1.20161229142547.git17e7bc0.fc24 noarch bin unsigned), rpm(ovirt-provider-ovn.fc24.noarch 1.0 1.20161229142547.git17e7bc0.fc24 noarch bin unsigned)] > master/latest.tested and 4.1/latest.tested are not populated with nightly builds of ovirt-provider-ovn > ------------------------------------------------------------------------------------------------------ > > Key: OVIRT-997 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-997 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: danken > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-997) master/latest.tested and 4.1/latest.tested are not populated with nightly builds of ovirt-provider-ovn
by danken (oVirt JIRA) 02 Jan '17

02 Jan '17

danken created OVIRT-997: ---------------------------- Summary: master/latest.tested and 4.1/latest.tested are not populated with nightly builds of ovirt-provider-ovn Key: OVIRT-997 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-997 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: danken Assignee: infra -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0