July 2017 - Infra - oVirt List Archives

[JIRA] (OVIRT-1548) Better STD-CI for GitHub
by Barak Korren (oVirt JIRA) 23 Jul '17

23 Jul '17

Barak Korren created OVIRT-1548: ----------------------------------- Summary: Better STD-CI for GitHub Key: OVIRT-1548 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1548 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra Priority: High We currently have some support for crating STD-CI jobs for projects running on GitHub. There are however, several issues with it: * The job templates you use for GitHub are different then the ones you use for Gerrit: ** Job names need to contain '\-github-' ** In Gerrit you need a separate 'project' entry for the 'build-artifacts' jobs, in GitHub you need a separate one for 'check-patch'. ** SCM checkout details are specified in the 'project' entry as opposed to a separate SCM file (We might want to adopt this for Gerrit). * The 'check-patch' jobs do not have full STC-CI. They don't run the post-build steps. * The triggering scheme is strange: ** All jobs trigger when certain messages are posted in the PR comments. ** Nothing is triggered automatically (As opposed to Gerrit where CI runs as soon as a patchset is submitted) ** Nothing triggers when a PR is merged (As opposed to with Gerrit where 'check-merged' and 'build-artifacts' are triggered on merge). * The white-listing scheme is different: ** The 'jenkins-whiltelist' file does not effect theses jobs at all. ** GitHub project/organisation membership determines white-listing ** white-listing is determined by who added the comment to run CI, not who authored the patch. Some of these issues and differences had already been tracked in other tickets. This ticket is for concentrating all related work. Other related tickets will be linked to it as blockers. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[JIRA] (OVIRT-1548) Better STD-CI for GitHub
by Barak Korren (oVirt JIRA) 23 Jul '17

23 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1548?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1548: -------------------------------- Epic Link: OVIRT-400 > Better STD-CI for GitHub > ------------------------ > > Key: OVIRT-1548 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1548 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: github, standard-ci > > We currently have some support for crating STD-CI jobs for projects running on GitHub. There are however, several issues with it: > * The job templates you use for GitHub are different then the ones you use for Gerrit: > ** Job names need to contain '\-github-' > ** In Gerrit you need a separate 'project' entry for the 'build-artifacts' jobs, in GitHub you need a separate one for 'check-patch'. > ** SCM checkout details are specified in the 'project' entry as opposed to a separate SCM file (We might want to adopt this for Gerrit). > * The 'check-patch' jobs do not have full STC-CI. They don't run the post-build steps. > * The triggering scheme is strange: > ** All jobs trigger when certain messages are posted in the PR comments. > ** Nothing is triggered automatically (As opposed to Gerrit where CI runs as soon as a patchset is submitted) > ** Nothing triggers when a PR is merged (As opposed to with Gerrit where 'check-merged' and 'build-artifacts' are triggered on merge). > * The white-listing scheme is different: > ** The 'jenkins-whiltelist' file does not effect theses jobs at all. > ** GitHub project/organisation membership determines white-listing > ** white-listing is determined by who added the comment to run CI, not who authored the patch. > Some of these issues and differences had already been tracked in other tickets. This ticket is for concentrating all related work. Other related tickets will be linked to it as blockers. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[JIRA] (OVIRT-1547) limit the amount of warnings the whitelist bots sends to GitHub
by Barak Korren (oVirt JIRA) 23 Jul '17

23 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1547?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1547: ------------------------------------- There is no bot here. This seems to be the logic on the GitHub pull-request trigger plugin when if is configured to filter by project/organisation membership. I suspect the amount of alerts matches the amount of jobs we have triggering on pull request events exactly. We probably need a staging environment for further testing and coming up with solutions, so adding OVIRT-1533 as a blocker > limit the amount of warnings the whitelist bots sends to GitHub > --------------------------------------------------------------- > > Key: OVIRT-1547 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1547 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri > Assignee: infra > > I'm not sure how the logic of the whitelist bot is done, but it looks like its sending too many messages back to GitHub: > https://github.com/oVirt/ovirt-ansible/pull/23 - on 1 commits there were 13 alerts. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[JIRA] (OVIRT-1547) limit the amount of warnings the whitelist bots sends to GitHub
by Barak Korren (oVirt JIRA) 23 Jul '17

23 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1547?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1547: -------------------------------- Issue Type: Bug (was: Task) > limit the amount of warnings the whitelist bots sends to GitHub > --------------------------------------------------------------- > > Key: OVIRT-1547 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1547 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri > Assignee: infra > > I'm not sure how the logic of the whitelist bot is done, but it looks like its sending too many messages back to GitHub: > https://github.com/oVirt/ovirt-ansible/pull/23 - on 1 commits there were 13 alerts. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[JIRA] (OVIRT-1547) limit the amount of warnings the whitelist bots sends to GitHub
by eyal edri (oVirt JIRA) 23 Jul '17

23 Jul '17

eyal edri created OVIRT-1547: -------------------------------- Summary: limit the amount of warnings the whitelist bots sends to GitHub Key: OVIRT-1547 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1547 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri Assignee: infra I'm not sure how the logic of the whitelist bot is done, but it looks like its sending too many messages back to GitHub: https://github.com/oVirt/ovirt-ansible/pull/23 - on 1 commits there were 13 alerts. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[JIRA] (OVIRT-1547) limit the amount of warnings the whitelist bots sends to GitHub
by eyal edri (oVirt JIRA) 23 Jul '17

23 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1547?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1547: ----------------------------- Epic Link: OVIRT-400 > limit the amount of warnings the whitelist bots sends to GitHub > --------------------------------------------------------------- > > Key: OVIRT-1547 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1547 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri > Assignee: infra > > I'm not sure how the logic of the whitelist bot is done, but it looks like its sending too many messages back to GitHub: > https://github.com/oVirt/ovirt-ansible/pull/23 - on 1 commits there were 13 alerts. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[oVirt Jenkins] ovirt-node-ng_ovirt-4.1-snapshot_build-artifacts-el7-x86_64 - Build # 200 - Failure!
by jenkins＠jenkins.phx.ovirt.org 23 Jul '17

23 Jul '17

------=_Part_243_976463564.1500696005282 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-snapshot_build-artifac… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-snapshot_build-artifac… Build Number: 200 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #200 ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_243_976463564.1500696005282--

1 1

[oVirt Jenkins] ovirt-node-ng_ovirt-4.1_build-artifacts-el7-x86_64 - Build # 200 - Failure!
by jenkins＠jenkins.phx.ovirt.org 23 Jul '17

23 Jul '17

------=_Part_241_608899719.1500696005012 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1_build-artifacts-el7-x8… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1_build-artifacts-el7-x8… Build Number: 200 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_241_608899719.1500696005012--

1 1

[oVirt Jenkins] ovirt-node-ng_master_build-artifacts-el7-x86_64 - Build # 483 - Failure!
by jenkins＠jenkins.phx.ovirt.org 23 Jul '17

23 Jul '17

------=_Part_247_1010026508.1500696265975 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… Build Number: 483 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #483 ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_247_1010026508.1500696265975--

1 1

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #551
by jenkins＠jenkins.phx.ovirt.org 23 Jul '17

23 Jul '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/551/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/changes/13/75913/5:patch --prune > git rev-parse origin/patch^{commit} # timeout=10 > git rev-parse patch^{commit} # timeout=10 Checking out Revision 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f (patch) Commit message: "Exclude big packages from mirrors" > git config core.sparsecheckout # timeout=10 > git checkout -f 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f > git rev-list 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins5437237118876510709.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 1465, in _commonLoadRepoXML if self._latestRepoXML(local): File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1443, in _latestRepoXML repomd = self.metalink_data.repomd File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 916, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 904, in _getMetalink shutil.move(result, self.metalink_filename) File "/usr/lib64/python2.7/shutil.py", line 301, in move copy2(src, real_dst) File "/usr/lib64/python2.7/shutil.py", line 130, in copy2 copyfile(src, dst) File "/usr/lib64/python2.7/shutil.py", line 82, in copyfile with open(src, 'rb') as fsrc: IOError: [Errno 2] No such file or directory: '/home/jenkins/mirrors_cache/fedora-updates-fc26/metalink.xml.tmp' Build step 'Execute shell' marked build as failure

1 1