- Infra - oVirt List Archives

[JIRA] (OVIRT-1237) Move repclosure jobs to OST
by eyal edri [Administrator] (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1237?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1237: --------------------------------------------- Resolution: Duplicate Status: Done (was: To Do) OVIRT-911 > Move repclosure jobs to OST > --------------------------- > > Key: OVIRT-1237 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1237 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > (14:08:22) sbonazzo: bkorren: I'm thinking about moving check-closure jobs > to standard CI. Do I need a new git repo for it? > (14:08:47) sbonazzo: bkorren: or now standard CI supports subdirectories? > (14:14:55) bkorren: sbonazzo, I think the best place for it is OST > (14:15:29) bkorren: sbonazzo, because then it can run against the > experimental repo, as well as the pre-release and stable ones > (14:16:57) sbonazzo: bkorren: OST has a learning curve I can't afford :-) > if that's the best place, I'll open a bz to track it and will plan for it > (14:17:49) bkorren: sbonazzo, okok, but its as easy as adding one > repoclosure command to run against the repo it already composes on its own > (14:18:26) bkorren: sbonazzo, please open a Jira as well, we might find a > good time to add it at some point <- eedri|afk > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #4581 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 20 Mar '17

20 Mar '17

------=_Part_82_1776490534.1489546652415 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/4581/, Build Number: 4581, Build Status: FAILURE ------=_Part_82_1776490534.1489546652415--

1 8

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5915 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 20 Mar '17

20 Mar '17

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

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5909 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 20 Mar '17

20 Mar '17

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

1 1

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #170
by jenkins＠jenkins.phx.ovirt.org 20 Mar '17

20 Mar '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/170/displa…> ------------------------------------------ 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 a5038d6893e1ea9d19c2253e18ff28b6e8c7311f (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f a5038d6893e1ea9d19c2253e18ff28b6e8c7311f > git rev-list a5038d6893e1ea9d19c2253e18ff28b6e8c7311f # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/hudson1434698995110565518.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 687, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 727, 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 1451, in _commonLoadRepoXML if self._latestRepoXML(local): File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1420, in _latestRepoXML oxml = self._saveOldRepoXML(local) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1278, in _saveOldRepoXML shutil.copy2(local, old_local) File "/usr/lib64/python2.7/shutil.py", line 131, in copy2 copystat(src, dst) File "/usr/lib64/python2.7/shutil.py", line 98, in copystat os.utime(dst, (st.st_atime, st.st_mtime)) OSError: [Errno 2] No such file or directory: '/home/jenkins/mirrors_cache/fedora-base-fc24/repomd.xml.old.tmp' Build step 'Execute shell' marked build as failure

1 1

[oVirt Jenkins] ovirt_4.1_he-system-tests - Build # 47 - Still Failing!
by jenkins＠jenkins.phx.ovirt.org 20 Mar '17

20 Mar '17

------=_Part_154_1962669375.1489977573997 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/ Build: http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/47/ Build Number: 47 Build Status: Still Failing Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #44 [Lev Veyde] Configure NFSv3 to use static ports Changes for Build #45 [Lev Veyde] Configure NFSv3 to use static ports [Sandro Bonazzola] ovirt-engine-cli: drop fc24 on master [Sandro Bonazzola] ovirt-engine-yarn: drop fc24 on master [Sandro Bonazzola] ovirt-imageio: drop fc24 on master [Sandro Bonazzola] ovirt-vmconsole: drop fc24 on master Changes for Build #46 [Lev Veyde] Configure NFSv3 to use static ports Changes for Build #47 [Ondra Machacek] Fix Ansible modules tests [Daniel Belenky] ost publisher: replaced 'email' with 'email-ext' [Gil Shinar] New builder that includes a few more std steps ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_154_1962669375.1489977573997--

1 2

[JIRA] (OVIRT-1264) Move individual job definitions from 'jobs/confs/yaml' to 'jobs/confs/projects'
by Barak Korren (oVirt JIRA) 19 Mar '17

19 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1264?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1264: -------------------------------- Epic Link: OVIRT-400 > Move individual job definitions from 'jobs/confs/yaml' to 'jobs/confs/projects' > ------------------------------------------------------------------------------- > > Key: OVIRT-1264 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1264 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > We've been doing some work recently to enable using the 'jenkins' repo to create different jobs for different Jenkins instances. I had been working on enabling its use to configure the staging server, while Gil had been working on using it downstream. > This work is based on the assumption that the '{{jobs/confs/yaml}}' directory only contains job templates and not individual job definitions. This is certainly true for all standard-CI jobs. > I have found, however, a few jobs that are defined inside the YAML directory. These include: > - ovirt-engine_master_coverity-analysis > - scan_security_and_license_ovirt-engine_master > - system_gerrit-alert-old-patches > - system_jenkins-report > Some of these jobs seem quite old. Can we remove them? Alternatively we could move the definitions to the '{{projects}}' directory, or, ideally, re-factor them into separate 'job-template' and 'project' definitions that reside in the right places. -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-1264) Move individual job definitions from 'jobs/confs/yaml' to 'jobs/confs/projects'
by Barak Korren (oVirt JIRA) 19 Mar '17

19 Mar '17

Barak Korren created OVIRT-1264: ----------------------------------- Summary: Move individual job definitions from 'jobs/confs/yaml' to 'jobs/confs/projects' Key: OVIRT-1264 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1264 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Reporter: Barak Korren Assignee: infra We've been doing some work recently to enable using the 'jenkins' repo to create different jobs for different Jenkins instances. I had been working on enabling its use to configure the staging server, while Gil had been working on using it downstream. This work is based on the assumption that the '{{jobs/confs/yaml}}' directory only contains job templates and not individual job definitions. This is certainly true for all standard-CI jobs. I have found, however, a few jobs that are defined inside the YAML directory. These include: - ovirt-engine_master_coverity-analysis - scan_security_and_license_ovirt-engine_master - system_gerrit-alert-old-patches - system_jenkins-report Some of these jobs seem quite old. Can we remove them? Alternatively we could move the definitions to the '{{projects}}' directory, or, ideally, re-factor them into separate 'job-template' and 'project' definitions that reside in the right places. -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

oVirt infra daily report - unstable production jobs - 263
by jenkins＠jenkins.phx.ovirt.org 19 Mar '17

19 Mar '17

------=_Part_148_975747284.1489964418248 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/263//artifact/exported-a… Cheers, Jenkins ------=_Part_148_975747284.1489964418248 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 - 19/03/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_master_check-patch-el7-x86_…">ovirt-system-tests_master_check-patch-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_4.0_image-ng-system-tests/">ovirt_4.0_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_hc-system-tests/">ovirt_4.1_hc-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.  NOT STABLE YET </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/">ovirt_4.1_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_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_hc-system-tests/">ovirt_master_hc-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/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_fc25_merged/">repos_master_check-closure_fc25_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/test-repo_ovirt_experimental_3.6/">test-repo_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> ------=_Part_148_975747284.1489964418248--

1 0

Job definitions in the 'yaml' directory
by Barak Korren 19 Mar '17

19 Mar '17

Hi guys, We've been doing some work recently to enable using the 'jenkins' repo to create different jobs for different Jenkins instances. I had be working on enabling its use to configure the staging server, while Gil had been working on using it downstream. This work is based on the assumption that the 'jobs/confs/yaml' directory only contains job templates and not individual job definitions. This is certainly true for all standard-CI jobs. I have found, however, a few jobs that are defined inside the YAML directory. These include: - ovirt-engine_master_coverity-analysis - scan_security_and_license_ovirt-engine_master - system_gerrit-alert-old-patches - system_jenkins-report Some of these jobs seem quite old. Can we remove them? Alternatively we could move the definitions to the 'projects' directory, or, ideally, re-factor them into separate 'job-template' and 'project' definitions that reside in the right places. -- Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/

2 2