[JIRA] (OVIRT-1739) Unified code owners mechanism between Gerrit and GitHub
by Barak Korren (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1509956867-24534-179
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Barak Korren created OVIRT-1739:
-----------------------------------
Summary: Unified code owners mechanism between Gerrit and GitHub
Key: OVIRT-1739
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1739
Project: oVirt - virtualization made easy
Issue Type: New Feature
Components: Gerrit/git, GitHub, oVirt CI
Reporter: Barak Korren
Assignee: infra
"Code owners" is the mechanism that automatically assigns reviewers to new code patches.
In Gerrit we use the "reviewers" plugin to automatically set reviewers (See OVIRT-1165).
GitHub has its own mechanism: https://github.com/blog/2392-introducing-code-owners
We would like to have a unified way for oVirt devs to do this regardless of the code hosting platform.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100070)
------------=_1509956867-24534-179
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<h3>Barak Korren created OVIRT-1739:</h3>
<pre> Summary: Unified code owners mechanism between Gerrit and GitHub
Key: OVIRT-1739
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1739
Project: oVirt - virtualization made easy
Issue Type: New Feature
Components: Gerrit/git, GitHub, oVirt CI
Reporter: Barak Korren
Assignee: infra</pre>
<p>“Code owners” is the mechanism that automatically assigns reviewers to new code patches.</p>
<p>In Gerrit we use the “reviewers” plugin to automatically set reviewers (See OVIRT-1165).</p>
<p>GitHub has its own mechanism: <a href="https://github.com/blog/2392-introducing-code-owners">https://github.com/blog/2392-introducing-code-owners</a></p>
<p>We would like to have a unified way for oVirt devs to do this regardless of the code hosting platform.</p>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYL..." alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>
------------=_1509956867-24534-179--
7 years
[JIRA] (OVIRT-1732) Make 'poll-upstream-chages' job abandon old changes it made
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1732?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1732:
--------------------------------
Priority: High (was: Medium)
> Make 'poll-upstream-chages' job abandon old changes it made
> -----------------------------------------------------------
>
> Key: OVIRT-1732
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1732
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Components: oVirt CI
> Reporter: Barak Korren
> Assignee: infra
> Priority: High
> Labels: poll-upstream-sources, standard-ci
>
> The poll-upstream-changes job creates patches when it runs. Not all these patches need or should be merged. When maintainers get around to looking at them, they typically can just merge the latest patch and throw away the rest.
> The issue is that over time, the patches created by the job can accumulate, and it can be cumbersome for maintainers to remove un-needed ones manually.
> We should make the poll job remove un-needed patches it made. It needs to look at the last SHA in the upstream-sources.yaml file, and remove all that patches that include an older SHA automatically.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100070)
7 years
oVirt infra daily report - unstable production jobs - 496
by jenkins＠jenkins.phx.ovirt.org
------=_Part_54_544170131.1509922802665
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/496//artifact/exported...
Cheers,
Jenkins
------=_Part_54_544170131.1509922802665
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 - 05/11/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-system-tests_ansible-suite-master/">ovirt-system-tests_ansible-suite-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;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/system-sync_mirrors-centos-extras-el7-x86_64/">system-sync_mirrors-centos-extras-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;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
------=_Part_54_544170131.1509922802665--
7 years
[JIRA] (OVIRT-1702) Jenkins STD-CI are running in dirty mock chroots
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1702?page=com.atlassian.jir... ]
Barak Korren commented on OVIRT-1702:
-------------------------------------
{quote}
I'm pretty sure in the past it was completely removed from the slave.
{quote}
I'm pretty sure it was not, since code handling this has not been significantly changed since David first wrote it.
The workspace including the source checkout does get completely remove when a *different job* starts running on the node. But as long as its the same job, the workspace stays as-is.
{quote}
Is there any good reason for not cleaning the slave after job completion?
{quote}
Yes. Re-cloning the whole git repo every time we run something will significantly slow things down.
Also we do not clean the slave up *after* the execution, we clean it *before the next one*. This has the benefit of allowing us to debug failed runs and also prevent the next run from failing if the post-run code was not reached for some reason. But a side-affect of this is that the more cleanup steps we have the longer the latency our users experience between submitting patchs and having their check-patch code run, so we try to keep it to a minimum.
> Jenkins STD-CI are running in dirty mock chroots
> ------------------------------------------------
>
> Key: OVIRT-1702
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1702
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: sbonazzo
> Assignee: infra
>
> Example:
> http://jenkins.ovirt.org/job/ovirt-wgt_master_check-patch-fc26-x86_64/11/...
> *09:44:06* + ./automation/build-artifacts.sh*09:44:06* + [[ -d
> exported-artifacts ]]*09:44:06* + mkdir -p
> exported-artifacts*09:44:06* + [[ -d tmp.repos/SOURCES ]]*09:44:06* +
> mkdir -p tmp.repos/SOURCES*09:44:06* + git clone
> git://anongit.freedesktop.org/spice/spice-nsis*09:44:06* fatal:
> destination path 'spice-nsis' already exists and is not an empty
> directory.
> jobs should run in clean chroots.
> --
> SANDRO BONAZZOLA
> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
> Red Hat EMEA <https://www.redhat.com/>
> <https://red.ht/sig>
> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
> <http://www.teraplan.it/redhat-osd-2017/>
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100070)
7 years
[JIRA] (OVIRT-1655) Groovy script failed
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1655?page=com.atlassian.jir... ]
Barak Korren commented on OVIRT-1655:
-------------------------------------
[~sbonazzo(a)redhat.com] Maybe I did not explain things clearly. The exception you see in the groovy code is the result of the execution slave not being available any more by the time the Groovy code runs. It seem that something that the job was doing caused the slave to lose network connectivity with Jenkins. That is the kind of exception we cannot really anticipate of handle properly.
The groovy exception is not the reason behind longs not being available, the slave not being available to pull logs from is...
In any case the failing run was not kept, so we cannot debug further. Next time please mark it to be kept forever and set the description to clearly link to the relevant Jira ticket.
Closing this ticket with CANNOT-REPRODUCE. Please re-open if the issue re-occurs.
> Groovy script failed
> --------------------
>
> Key: OVIRT-1655
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1655
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: sbonazzo
> Assignee: infra
>
> Hi, I had an ovirt-node-ng build failure and didn't get logs about what
> happened due to:
> *Groovy script failed:*
> java.lang.NullPointerException: Cannot invoke method child() on null object
> Failed job is
> http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1_build-artifacts-el7-...
> CAn you please check what happened?
> --
> SANDRO BONAZZOLA
> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
> Red Hat EMEA <https://www.redhat.com/>
> <https://red.ht/sig>
> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100070)
7 years
Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #882
by jenkins＠jenkins.phx.ovirt.org
See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/882/disp...>
------------------------------------------
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/ws/>
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10
Cleaning workspace
> git rev-parse --verify HEAD # timeout=10
Resetting working tree
> git reset --hard # timeout=10
> git clean -fdx # timeout=10
Pruning obsolete local branches
Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git
> git --version # timeout=10
> git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune
> git rev-parse origin/master^{commit} # timeout=10
Checking out Revision 2d0aecce46cfa1b3a1770ab846c983bf95f82328 (origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 2d0aecce46cfa1b3a1770ab846c983bf95f82328
Commit message: "Make mirror_mgr.sh drop yum MD cache before sync"
> git rev-list 2d0aecce46cfa1b3a1770ab846c983bf95f82328 # timeout=10
[system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins1210161513228216876.sh
+ jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf
Checking if mirror needs a resync
Traceback (most recent call last):
File "/usr/bin/reposync", line 343, in <module>
main()
File "/usr/bin/reposync", line 175, in main
my.doRepoSetup()
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup
return self._getRepos(thisrepo, True)
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos
self._repos.doSetup(thisrepo)
File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup
self.retrieveAllMD()
File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD
dl = repo._async and repo._commonLoadRepoXML(repo)
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1456, in _commonLoadRepoXML
local = self.cachedir + '/repomd.xml'
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 772, in <lambda>
cachedir = property(lambda self: self._dirGetAttr('cachedir'))
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 755, in _dirGetAttr
self.dirSetup()
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 734, in dirSetup
self._dirSetupMkdir_p(dir)
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 711, in _dirSetupMkdir_p
raise Errors.RepoError, msg
yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7'
Build step 'Execute shell' marked build as failure
7 years
