- Infra - oVirt List Archives

jsonrpc build failures
by Piotr Kliczewski 09 Jan '17

09 Jan '17

I pushed a patch and I can see that all the jobs failed for it: http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_master_check-patch-el7-x86_6… : FAILURE http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_master_check-patch-fc24-x86_… : FAILURE http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_4.1_check-patch-fc24-x86_64/… : FAILURE http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_4.1_check-patch-el7-x86_64/3/ : FAILURE Can someone please take a look? Thanks, Piotr

1 0

The feature everyone was asking for is finally here...
by Eyal Edri 09 Jan '17

09 Jan '17

FYI, After many requests from multiple developers and testers, the oVirt CI added a new simple job that lets you run the full fledged end-to-end oVirt system tests with a click of a button. You can read all the details and how-to in the new oVirt blog [1]. We wanted to allow running oVirt system tests on EVERY open patch from ANY oVirt project, without relaying on complex building code inside the job. Luckily we just added the 'build-on-demand' so together with it you can build any rpms you'd like and use them to run the manual job. So the 2 steps you'll need to do are: 1. Write 'ci please build' inside a comment on an open oVirt patch ( make sure the feature is enabled for that project first, its already available for ovirt-engine,vdsm,dashboard and vdsm-jsonrpc-java) 2. Run the manual OST job for the version you'd like to test with the URLs you got from #1 You'll get and email once the job is done and you can browse the results and check for logs from engine and the hosts. Please feel free to ask questions on infra(a)ovirt.org as usual. [1] https://www.ovirt.org/blog/2017/01/ovirt-system-tests-to-the-rescue/ -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 <+972%209-769-2018> irc: eedri (on #tlv #rhev-dev #rhev-integ)

4 3

[JIRA] (OVIRT-1010) Split the experimental pipeline job into stages
by Barak Korren (oVirt JIRA) 09 Jan '17

09 Jan '17

Barak Korren created OVIRT-1010: ----------------------------------- Summary: Split the experimental pipeline job into stages Key: OVIRT-1010 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1010 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Reporter: Barak Korren Assignee: infra Since the experimental flow is based on a pipeline job, we can make debugging it easier by splitting it into stages. -- This message was sent by Atlassian JIRA (v1000.670.2#100024)

1 0

[JIRA] (OVIRT-1010) Split the experimental pipeline job into stages
by Barak Korren (oVirt JIRA) 09 Jan '17

09 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1010?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1010: -------------------------------- Epic Link: OVIRT-400 > Split the experimental pipeline job into stages > ----------------------------------------------- > > Key: OVIRT-1010 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1010 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Since the experimental flow is based on a pipeline job, we can make debugging it easier by splitting it into stages. -- This message was sent by Atlassian JIRA (v1000.670.2#100024)

1 0

When trigged manually the check-merged job
by Yaniv Bronheim 09 Jan '17

09 Jan '17

When trigged manually the check-merged job for specific patch we don't see the link in the patch History - see in https://gerrit.ovirt.org/#/c/69802/3 it used to be different .. can we get the link back? Thanks. -- *Yaniv Bronhaim.*

3 2

[JIRA] (OVIRT-853) check out blue ocean jenkins project
by Barak Korren (oVirt JIRA) 09 Jan '17

09 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-853?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-853: ------------------------------------ I have it running in a test container... It required Jenkins 2.7 and up. It run side-by-side with the old Jenkins UI. Its quite good at showing results of pipelines. Some terms important for the analysis below: * *Pipeline stage:* Created with the '{{stage}}' block - collects build steps together and gives then a title. * *Pipeline build step:* Created with commands like '{{sh}}' and {{scm}}. Does actual work like running scripts. The older pipeline stage view (The table we see in the status screen of pipeline jobs) can already show pipeline stages and let you see the logs of separate build steps separately, but its not very good when the pipeline does things in parallel - it just shows the steps one after another. Blue Ocean knows how to show things that happened in parallel separately. Its important to note that both plugins assume that pipeline stages never happen in parallel. This means that debugging complex stuff that happens in parallel can be difficult, since it can be hard to tell separate build steps apart (Most of them are simply called 'Shell script') and we can't give then names by using stages. Both Blue Ocean and the old pipeline stage view do not show the names of the nodes things are running on, this can make some things harder to debug. When pipeline jobs run other jobs - both plugins are not good at showing that, they do not provide clear indication about what is going on or provide links to the invoked jobs. Blue ocean knows how to show the running time of a given piepline, but not of stages inside that pipeline. The pipeline view can show both, so its better for debugging slowness... Blue ocean also cannot show runtime trends. Blue Ocean is not good at showing results of freestyle (old) jobs: * The logs of all build steps are shown together - like in the console view * There is no results screen, so we can't use something like groovy to create better output display. * There is a big and fancy artifacts tab, but it only lets you download artifacts, not view them. Also we need to check how it behaves when we have many artifacts nested inside directories. *Conclusions:* # Blue Ocean requires Jenkins 2 # We should slowly move to pipeline jobs everywhere if we want to get any improved logging. # We should keep pipelines simple - not do complex stuff in parallel, instead split pipelines into serial stages and only do 1-3 steps on parallel within the stage boundaries. # Blue Ocean cannot completely replace the Jenkins UI. # I recommend we install Blue Ocean once we upgrade to Jenkins 2, so we can start gaining real world experience with it. # Over time I expect we will link to Blue Ocean from Gerrit instead of to the old UI. > check out blue ocean jenkins project > ------------------------------------ > > Key: OVIRT-853 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-853 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: infra > > https://jenkins.io/projects/blueocean/ -- This message was sent by Atlassian JIRA (v1000.670.2#100024)

1 0

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

08 Jan '17

------=_Part_174_926679668.1483916402346 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/194//artifact/exported-a… Cheers, Jenkins ------=_Part_174_926679668.1483916402346 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 - 08/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_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/ovirt_4.1_system-tests/">ovirt_4.1_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/repos_4.0_check-closure_fc23_merged/">repos_4.0_check-closure_fc23_merged</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/repos_4.1_check-closure_el7_merged/">repos_4.1_check-closure_el7_merged</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/repos_4.1_check-closure_fc24_merged/">repos_4.1_check-closure_fc24_merged</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/repos_master_check-closure_el7_merged/">repos_master_check-closure_el7_merged</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/repos_master_check-closure_fc24_merged/">repos_master_check-closure_fc24_merged</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_174_926679668.1483916402346--

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #151 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 08 Jan '17

08 Jan '17

------=_Part_168_1561606545.1483884140733 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/151/, Build Number: 151, Build Status: FAILURE ------=_Part_168_1561606545.1483884140733--

1 1

Future of the oVirt website
by Marc Dequènes (Duck) 08 Jan '17

08 Jan '17

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Mf2CRNBB5HrIBekLkGCVl7fFA28A9J5x4 Content-Type: multipart/mixed; boundary="KLQQcoDbkQBSA3JhvJxcIEH58dqc2asks"; protected-headers="v1" From: =?UTF-8?B?TWFyYyBEZXF1w6huZXMgKER1Y2sp?= <duck(a)redhat.com> To: oVirt Infra <infra(a)ovirt.org> Cc: Brian Proffitt <bproffit(a)redhat.com>, Garrett LeSage <garrett(a)redhat.com>, Michael Scherer <misc(a)redhat.com> Message-ID: <70270534-4d06-ef32-0a72-b457c96678fe(a)redhat.com> Subject: Future of the oVirt website --KLQQcoDbkQBSA3JhvJxcIEH58dqc2asks Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Quack, So I just discovered this thread: http://lists.ovirt.org/pipermail/devel/2017-January/029097.html First, it would be nice if the infra team was involved directly, because not everyone is also an oVirt developer (and on this list). Also there are already plans to improve the site system and build and this side-initiative feels like an unexpected and rude disruption of energy already invested. It seems people forget how things were in the past, which leads to going back and forth between a new solution and the previous one. People wish for an easy way to contribute, and this is a legitimate goal. After some time an easy solution make things complicated because it is such a mess and there is no review, so no quality checks, and people wish to have workflows. Then they find it to cumbersome and wish to go back to a marvelous past. And so on again and again. This said, this does not mean the current solution is perfect and we should not think about a better one, but we should recall why we abandoned a wiki to switch to the current solution, so we don't fall into the same traps. What I can say on the topic is that migrating is painful, so we should be cautious. OSAS is not here to force a solution upon you, but the infra team (and the OSAS folks too), have a limited workforce to dedicate to this project, so let's make something realistic. Also we just finish another pass of cleanup of the current site, with migration bugs from the previous Mediawiki solution, so keep in mind it would probably take _years_ to really get something clean. Who's gonna do this?= I also wanted to say I totally disagree on someone's remark (somewhere in the thread) about doc not being as important as code. A lot of content is obsolete or mistaken in the current site already, and this means giving a very bad image of the project, raising the number of silly questions people come to bother you with on ML or IRC, so I think doc should really be taken seriously. As a user it is often I have to dig in the code to find undocumented features, or why a documented one does not work as said, and that's fu^Wutterly boring. So this was to gather all related parties. \_o< --KLQQcoDbkQBSA3JhvJxcIEH58dqc2asks-- --Mf2CRNBB5HrIBekLkGCVl7fFA28A9J5x4 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEcpcqg+UmRT3yiF+BVen596wcRD8FAlhvJ5cACgkQVen596wc RD8Ecw//WfXl6FgFg+7R8u84dAhiDiciE/ybTPZDPWldnClTE/+L0toNSiNNBXNd 13HQGnpXpxeCH0JqdzYw0GbJB9DqRhfZBEgw55/BtPG9kPL14bTZrLlZNhvQa8p7 A+i+zAq9I6TbHeR1bY/lNf1cBZYGFRacxihlF6W62lq0jZthV2q3bRX4Fy18yWUD CmwKVKchaGrx4J0SOQ2NO4lh7enwaKpGOTzTsIlIjA+jSSKZAJt2jbKzel+bOfY/ SFDxfp2L539A4pXPDOJ4oRI4fMOZ+aVYpfGT2p+QmwMzaEu1KR4ZF0rXNDNr9SaI M//R3174Rr42oXfWpPJO1jAWeZpdGvJbVypxVFNNxFDFATrG7/JuAkoUJWbYQ28Q DKmHH8DXzyaB+NGA3rLpiAJSy59yNN5YZi/vK5I1fdF2L6uMw9dY3AND+RYSdzFp AXMx7Wg1n8MylxKc45GS6NgzCG1P43BeB0dSsLoxKZMkg7EDjwm7qug6PrebtbI8 Tvk0UEhdzHlXaGFTUrNVW6XrMJG6J9UhmoO2uS/KMUCnG2FsMJSwLPIdigxKqDSu bccFD6tQz4+VkG9KdiEw+/ofXtS5zF9ZiTPf3cETDbcMWQ8Vm47aq49sTOGF6LTt MLtPRRvu32oDg4UN6o1hGhUoiFcF8d2SEIPkDWsKahutOaL4vHw= =uxHW -----END PGP SIGNATURE----- --Mf2CRNBB5HrIBekLkGCVl7fFA28A9J5x4--

3 3

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #143 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 08 Jan '17

08 Jan '17

------=_Part_124_1594460510.1483641357074 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/143/, Build Number: 143, Build Status: FAILURE ------=_Part_124_1594460510.1483641357074--

1 4