- Infra - oVirt List Archives

[JIRA] (OVIRT-1313) Make OST manual job build history more useful
by Barak Korren (oVirt JIRA) 09 Apr '17

09 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1313?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1313: -------------------------------- Description: Looking at the OST manual job build history is pretty useless right now because seeing a failed build tells you nothing about what actually failed to run. We should use the groovy post-build plugin to add information such as the suite type that was run, the oVirt version that was tested and wither custom settings were used. We can also consider adding the name of the person that ran the job. was: Looking at the OST manual job build history is pretty useless right now because seeing a failed build tells you nothing about what actually failed to run. We should use the groovy post-build plugin to add information such as the suite type that was run, the oVirt version that was tested and wither custom settings were used. > Make OST manual job build history more useful > --------------------------------------------- > > Key: OVIRT-1313 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1313 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Priority: Low > Labels: ost > > Looking at the OST manual job build history is pretty useless right now because seeing a failed build tells you nothing about what actually failed to run. > We should use the groovy post-build plugin to add information such as the suite type that was run, the oVirt version that was tested and wither custom settings were used. > We can also consider adding the name of the person that ran the job. -- This message was sent by Atlassian JIRA (v1000.885.0#100040)

1 0

[JIRA] (OVIRT-1313) Make OST manual job build history more useful
by Barak Korren (oVirt JIRA) 09 Apr '17

09 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1313?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1313: -------------------------------- Summary: Make OST manual job build history more useful (was: Make OST manual job buiold history more useful) > Make OST manual job build history more useful > --------------------------------------------- > > Key: OVIRT-1313 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1313 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Priority: Low > Labels: ost > > Looking at the OST manual job build history is pretty useless right now because seeing a failed build tells you nothing about what actually failed to run. > We should use the groovy post-build plugin to add information such as the suite type that was run, the oVirt version that was tested and wither custom settings were used. -- This message was sent by Atlassian JIRA (v1000.885.0#100040)

1 0

[JIRA] (OVIRT-1313) Make OST manual job buiold history more useful
by Barak Korren (oVirt JIRA) 09 Apr '17

09 Apr '17

Barak Korren created OVIRT-1313: ----------------------------------- Summary: Make OST manual job buiold history more useful Key: OVIRT-1313 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1313 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Reporter: Barak Korren Assignee: infra Priority: Low Looking at the OST manual job build history is pretty useless right now because seeing a failed build tells you nothing about what actually failed to run. We should use the groovy post-build plugin to add information such as the suite type that was run, the oVirt version that was tested and wither custom settings were used. -- This message was sent by Atlassian JIRA (v1000.885.0#100040)

1 0

[JIRA] (OVIRT-1313) Make OST manual job buiold history more useful
by Barak Korren (oVirt JIRA) 09 Apr '17

09 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1313?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1313: -------------------------------- Epic Link: OVIRT-400 > Make OST manual job buiold history more useful > ---------------------------------------------- > > Key: OVIRT-1313 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1313 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Priority: Low > Labels: ost > > Looking at the OST manual job build history is pretty useless right now because seeing a failed build tells you nothing about what actually failed to run. > We should use the groovy post-build plugin to add information such as the suite type that was run, the oVirt version that was tested and wither custom settings were used. -- This message was sent by Atlassian JIRA (v1000.885.0#100040)

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-updates-fc25-x86_64 #148
by jenkins＠jenkins.phx.ovirt.org 09 Apr '17

09 Apr '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc25-x86_64…> Changes: [Eyal Edri] Final removal of master nightly snapshot copy jobs mech ------------------------------------------ Started by user Barak Korren [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc25-x86_64…> > 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 5a9a208da9ee4b684648cad19f26b5b8cdc4525d (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 5a9a208da9ee4b684648cad19f26b5b8cdc4525d > git rev-list c7f97c6100e0a53f679bd711bf05ca8f6a89a6a0 # timeout=10 [system-sync_mirrors-fedora-updates-fc25-x86_64] $ /bin/bash -xe /tmp/hudson1757423059663022307.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-updates-fc25 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync /tmp/hudson1757423059663022307.sh: line 3: 26457 Terminated jenkins/scripts/mirror_mgr.sh resync_yum_mirror 'fedora-updates-fc25' 'x86_64' jenkins/data/mirrors-reposync.conf Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information Build step 'Execute shell' marked build as failure

1 12

Build failed in Jenkins: system-sync_mirrors-fedora-updates-fc24-x86_64 #147
by jenkins＠jenkins.phx.ovirt.org 09 Apr '17

09 Apr '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc24-x86_64…> ------------------------------------------ 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-fedora-updates-fc24-x86_64…> > 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 bdca0b5702e3f2058805edcff168947ee95b1996 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f bdca0b5702e3f2058805edcff168947ee95b1996 > git rev-list bdca0b5702e3f2058805edcff168947ee95b1996 # timeout=10 [system-sync_mirrors-fedora-updates-fc24-x86_64] $ /bin/bash -xe /tmp/hudson2711638654874449445.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-updates-fc24 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Resyncing repo: fedora-updates-fc24 Syncing yum repo fedora-updates-fc24 for arch: x86_64 fedora-updates-fc24/presto 0% [ ] 0.0 B/s | 0 B --:-- ETA fedora-updates-fc24/presto 51% [======== ] 0.0 B/s | 834 kB --:-- ETA fedora-updates-fc24/prestodelta | 1.6 MB 00:00 : unbound-munin-1.6.0-6.fc24.noarch.rpm | 33 kB 00:00 Removing kernel-debug-devel-4.10.8-100.fc24.x86_64.rpm due to failed signature check. Build step 'Execute shell' marked build as failure

1 18

[oVirt Jenkins] ovirt_master_hc-system-tests - Build # 61 - Failure!
by jenkins＠jenkins.phx.ovirt.org 09 Apr '17

09 Apr '17

------=_Part_344_426053590.1491643776895 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/ Build: http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/61/ Build Number: 61 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #61 [ngoldin] reposync: add debug-info packages on master ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_344_426053590.1491643776895--

1 1

oVirt repositories 101; or everything you wanted to know about oVirt repositories and didn't ask
by Eyal Edri 09 Apr '17

09 Apr '17

Hi oVirt developers and users, Some of you might be familiar with the oVirt repositories and all their flavors, while some of you are just familiar with the official releases. The fact is, we have plenty of them and each has its own role and a right usage. Moreover, we did a significant overhaul on all the repositories in the past months, So hopefully now it will be easier to explain which repo to use when. I'll start with reviewing each oVirt repository and give a bit of background and the logic behind it, how to consume it and the relevant usage for it. For simplicity, I'll review the repositories on the 4.1 release, but it valid for all other oVirt releases ( except 'master' which doesn't have an official or pre-release repositories ). I will also upload this information to the oVirt.org site, but since this is important, I didn't want to wait with the sending this email. *oVirt repositories* *Official repositories* *Desc:* here you can find the official signed oVirt RPMs, immediately after an official release has been done. *Path:* http://resources.ovirt.org/pub/ovirt-4.1/rpm/$distro *Update frequency:* on every oVirt release, usually happens on a monthly cadence. *Release rpm: *http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm *Who should use it? * oVirt users, developers or anyone who wants a final and official release *Pre-release repositories* *Desc:* here you can find the pre-release bits of oVirt RC builds, just before they are released. *Path:* http://resources.ovirt.org/pub/ovirt-4.1-pre/rpm/$distro *Update frequency:* usually on a weekly or bi-weekly basis *Release rpm: *http://resources.ovirt.org/pub/yum-repo/ovirt- release41-pre.rpm *Who should use it? * oVirt users, developers or anyone who wants to try out oVirt new version before its out, Keeping in mind this isn't a fully verified release and might still have critical bugs which are not fixed yet. Packages in this repo are verified by automation and checked by humans for basic sanity before publishing. *Nightly snapshot (verified) repositories* *Desc:* here you can find the nightly snapshot of RPMs, which passed basic sanity by our 'oVirt System Tests' framework in the oVirt CI system. *Path:* http://resources.ovirt.org/pub/ovirt-4.1-snapshot/rpm/$distro *Update frequency:* Every night *Release rpm: *http://resources.ovirt.org/pub/yum-repo/ovirt- release41-snapshot.rpm *Who should use it? * oVirt users, developers or anyone who wants to try out oVirt latest bits right of the build oven! We trust our system tests, which already run more than 40 various tests such as 'add host', 'create VM', 'live migration' and more! *** Important note: the snapshot repositories are verified only in master currently, we might do the same for 4.1 soon, as we see no issues with master so far ** * *The above repos should suffice to most usres and developers, but if you feel its not enough and you still need a faster verified repo, look below! * *Advanced oVirt repositories* *Builds artifacts repo* *Desc:* This is a new feature from oVirt 'standard CI' project, where each 'build-artifacts' job is actually a yum repo as well. *Path:* http://jenkins.ovirt.org/job/ovirt-engine_4.1_ build-artifacts-on-demand-el7-x86_64/lastSuccessfulBuild/ artifact/exported-artifacts ( example ) *Update frequency:* after each commit or 'ci please build' comment *Release rpm: *N/A *Who should use it? * oVirt developers who need latest RPMs from another oVirt project and cannot or need not wait for that project`s packages to pass OST". oVirt developers running manual OST job and need to test an open Gerrit patch, using the 'ci please build' command. *Tested repositories* *Desc:* The tested repositories hold all the oVIrt packages which passed CI ( similar to snapshot repos ) and retain also version history for X versions back. *Path:* http://resources.ovirt.org/repos/ovirt/tested/4.1/rpm/$distro *Update frequency:* after each 'build artifacts' job is triggered by any oVirt project and if the packages passed sanity checks *Release rpm: *N/A *Who should use it? * If you want to have latest and greatest oVirt packages and can't wait for the nightly repo. If you are testing upgrades or need more than one version of a pacakge in your repo. *Experimental repositories * *Desc:* Internal CI repos which are a part of the 'experimental' flow which runs OST on each built package. *Path:* http://resources.ovirt.org/repos/ovirt/experimental/ 4.1/latest.tested/rpm/el7/$distro *Update frequency:* after each 'build artifacts' job is triggered by any oVirt project and if the packages passed sanity checks *Release rpm: *N/A *Who should use it? * *No one other than internal CI jobs.* These repos are constantly refreshed and RPMs are being removed from them, so they are very prone to errors, please don't use them. I hope this makes a bit of order in all the repos and how to use them. If you still have questions, please don't hesitate to contact the infra team at infra(a)ovirt.org or just reply to this thread. -- Eyal edri ASSOCIATE MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0

[JIRA] (OVIRT-1312) Make 'scan_for_artifacts.sh' publish repos separately
by Barak Korren (oVirt JIRA) 09 Apr '17

09 Apr '17

Barak Korren created OVIRT-1312: ----------------------------------- Summary: Make 'scan_for_artifacts.sh' publish repos separately Key: OVIRT-1312 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1312 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Repositories Mgmt Reporter: Barak Korren Assignee: infra The '{{scan_for_artifacts.sh}}' cron job runs on the resources server and syncs packages into the nightly snapshot repos. It tries to serially sync all repos for all oVirt versions. The issue is that if one of the repos fails to sync, the rest do not get synced either. We need to make the cron job sync each repo separately so failure mfor one repo will not affect the others. -- This message was sent by Atlassian JIRA (v1000.885.0#100040)

1 0

[JIRA] (OVIRT-1312) Make 'scan_for_artifacts.sh' publish repos separately
by Barak Korren (oVirt JIRA) 09 Apr '17

09 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1312?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1312: -------------------------------- Epic Link: OVIRT-403 > Make 'scan_for_artifacts.sh' publish repos separately > ----------------------------------------------------- > > Key: OVIRT-1312 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1312 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > > The '{{scan_for_artifacts.sh}}' cron job runs on the resources server and syncs packages into the nightly snapshot repos. It tries to serially sync all repos for all oVirt versions. > The issue is that if one of the repos fails to sync, the rest do not get synced either. > We need to make the cron job sync each repo separately so failure mfor one repo will not affect the others. -- This message was sent by Atlassian JIRA (v1000.885.0#100040)

1 0