- Infra - oVirt List Archives

[JIRA] (OVIRT-1315) post-merge build-artifacts jobs for the same commit have a race condition between different platforms
by sbonazzo (oVirt JIRA) 12 Apr '17

12 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1315?page=com.atlassian.jira.… ] sbonazzo commented on OVIRT-1315: --------------------------------- [~bkorren(a)redhat.com] can we change stdci to have a single build job that trigger all the different distro/arch builds, wait until they finishes and then finish with success if all succeeded and trigger the deploy job? This is valid for all projects, not only vdsm. It doesn't make sense to have different versions/builds available for different arches/distro. > post-merge build-artifacts jobs for the same commit have a race condition between different platforms > ----------------------------------------------------------------------------------------------------- > > Key: OVIRT-1315 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1315 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Priority: High > > When a change is merged the build artifacts jobs for all platforms are invoked in parallel by the Gerrit trigger. These jobs in turn invoej the 'deploy-to-experimental' job to move the artifacts into the 'experimental' repos for OST testing. > Various issues arise because of this: > # A Fedora build can trigger an OST run befire the equivalent EL7 build finishes. This wastes resources on needless OST runs. > # A PPC64 build can place 'noarch' artifacts in experimental before the equivalent x86_64 builds are ready. This can cause OST failures. > Because of the PPC64 issue, we have actually disabled publishing into experimental from the PPC64 jobs. Since we now want to move to fully automated production publishing via the experimental flow, we need to fix this. -- This message was sent by Atlassian JIRA (v1000.892.1#100040)

1 0

[JIRA] (OVIRT-1315) post-merge build-artifacts jobs for the same commit have a race condition between different platforms
by Barak Korren (oVirt JIRA) 11 Apr '17

11 Apr '17

Barak Korren created OVIRT-1315: ----------------------------------- Summary: post-merge build-artifacts jobs for the same commit have a race condition between different platforms Key: OVIRT-1315 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1315 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Reporter: Barak Korren Assignee: infra Priority: High When a change is merged the build artifacts jobs for all platforms are invoked in parallel by the Gerrit trigger. These jobs in turn invoej the 'deploy-to-experimental' job to move the artifacts into the 'experimental' repos for OST testing. Various issues arise because of this: # A Fedora build can trigger an OST run befire the equivalent EL7 build finishes. This wastes resources on needless OST runs. # A PPC64 build can place 'noarch' artifacts in experimental before the equivalent x86_64 builds are ready. This can cause OST failures. Because of the PPC64 issue, we have actually disabled publishing into experimental from the PPC64 jobs. Since we now want to move to fully automated production publishing via the experimental flow, we need to fix this. -- This message was sent by Atlassian JIRA (v1000.892.1#100040)

1 0

[JIRA] (OVIRT-1315) post-merge build-artifacts jobs for the same commit have a race condition between different platforms
by Barak Korren (oVirt JIRA) 11 Apr '17

11 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1315?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1315: -------------------------------- Epic Link: OVIRT-400 > post-merge build-artifacts jobs for the same commit have a race condition between different platforms > ----------------------------------------------------------------------------------------------------- > > Key: OVIRT-1315 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1315 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Priority: High > > When a change is merged the build artifacts jobs for all platforms are invoked in parallel by the Gerrit trigger. These jobs in turn invoej the 'deploy-to-experimental' job to move the artifacts into the 'experimental' repos for OST testing. > Various issues arise because of this: > # A Fedora build can trigger an OST run befire the equivalent EL7 build finishes. This wastes resources on needless OST runs. > # A PPC64 build can place 'noarch' artifacts in experimental before the equivalent x86_64 builds are ready. This can cause OST failures. > Because of the PPC64 issue, we have actually disabled publishing into experimental from the PPC64 jobs. Since we now want to move to fully automated production publishing via the experimental flow, we need to fix this. -- This message was sent by Atlassian JIRA (v1000.892.1#100040)

1 0

oVirt infra daily report - unstable production jobs - 288
by jenkins＠jenkins.phx.ovirt.org 11 Apr '17

11 Apr '17

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/288//artifact/exported-a… Cheers, Jenkins

1 1

oVirt infra daily report - unstable production jobs - 288
by jenkins＠jenkins.phx.ovirt.org 11 Apr '17

11 Apr '17

------=_Part_6_2123170173.1491951601794 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/288//artifact/exported-a… Cheers, Jenkins ------=_Part_6_2123170173.1491951601794 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 - 10/04/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/ovirt_4.1_image-ng-system-tests/">ovirt_4.1_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_master-ansible-system-tests/">ovirt_master-ansible-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_master_image-ng-system-tests/">ovirt_master_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-sync_mirrors-centos-updates-el7-x86_64/">system-sync_mirrors-centos-updates-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/test-repo_ovirt_experimental_master/">test-repo_ovirt_experimental_master</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/test-repo_ovirt_experimental_master-dry_run/">test-repo_ovirt_experimental_master-dry_run</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_6_2123170173.1491951601794--

1 0

planned Jenkins restart
by Evgheni Dereveanchin 11 Apr '17

11 Apr '17

Hi everyone, I'll be performing a planned Jenkins restart within the next hour. No new builds will be scheduled during this maintenance period. I will inform you once it is over. Regards, Evgheni Dereveanchin

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #6257 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 11 Apr '17

11 Apr '17

------=_Part_357_2059036738.1491675826893 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6257/, Build Number: 6257, Build Status: FAILURE ------=_Part_357_2059036738.1491675826893--

1 54

[JIRA] (OVIRT-1271) GH plugin tries to consume gerrit's projects
by Evgheni Dereveanchin (oVirt JIRA) 11 Apr '17

11 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1271?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-1271: --------------------------------------------- These warning messages are still present on both production and staging Jenkins instances. The GitHub plugin tries to [match a string|https://github.com/jenkinsci/github-plugin/blob/93d40692ff3866705175…] like <protocol>://<server>/<project>/<repo> and this fails since our Gerrit URL uses a different format: <protocol>://<server>/<repo> The unclear thing is why GitHub plugin is invoked at all on jobs that are only using Gerrit. The staging instance only has a single GitHub job and that one does not have any mentions of gerrit as a repo URL. Same for other jobs - they consume Gerrit directly and have all GitHub settings unset. It may be related to hook setup or something similar. Will try to troubleshoot more on the staging instance. > GH plugin tries to consume gerrit's projects > -------------------------------------------- > > Key: OVIRT-1271 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1271 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Pavel Zhukov > Assignee: infra > Priority: Low > > Jenkins logs are flooded with: > Mar 23, 2017 10:40:05 AM com.cloudbees.jenkins.GitHubRepositoryName create > WARNING: Could not match URL http://gerrit.ovirt.org/jenkins.git > Mar 23, 2017 10:40:05 AM com.cloudbees.jenkins.GitHubRepositoryName create > WARNING: Could not match URL http://gerrit.ovirt.org/jenkins-whitelist.git > Mar 23, 2017 10:40:05 AM com.cloudbees.jenkins.GitHubRepositoryName create > WARNING: Could not match URL git://gerrit.ovirt.org/vdsm.git > Mar 23, 2017 10:40:05 AM com.cloudbees.jenkins.GitHubRepositoryName create > WARNING: Could not match URL http://gerrit.ovirt.org/jenkins.git > While the messages itself are harmless they floods the logs and consume jenkins master's resources. > See https://issues.jenkins-ci.org/browse/JENKINS-24422 for more details. -- This message was sent by Atlassian JIRA (v1000.892.1#100040)

1 0

Change in barak-test[master]: jenkins integ test
by review＠gerrit-staging.phx.ovirt.org 11 Apr '17

11 Apr '17

>From Evgheni Dereveanchin <ederevea(a)redhat.com>: Evgheni Dereveanchin has posted comments on this change. Change subject: jenkins integ test ...................................................................... Patch Set 1: test -- To view, visit https://gerrit-staging.phx.ovirt.org/17 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I50acc69c8c5b6b3e03f3ced23d72c883ac4db2c2 Gerrit-PatchSet: 1 Gerrit-Project: barak-test Gerrit-Branch: master Gerrit-Owner: Evgheni Dereveanchin <ederevea(a)redhat.com> Gerrit-Reviewer: Evgheni Dereveanchin <ederevea(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-HasComments: No

1 0

[JIRA] (OVIRT-1314) update Jenkins plugins listed in 2017-04-10 advisory
by Evgheni Dereveanchin (oVirt JIRA) 11 Apr '17

11 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1314?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1314: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > update Jenkins plugins listed in 2017-04-10 advisory > ---------------------------------------------------- > > Key: OVIRT-1314 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1314 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > Priority: High > > A security advisory is out for a bunch of plugins: > https://jenkins.io/security/advisory/2017-04-10/ > Opening this ticket to track the process of updating affected ones. -- This message was sent by Atlassian JIRA (v1000.892.1#100040)

1 0