[JIRA] (OVIRT-1026) mock_genconfig fails on fc25 due to missing requests library
by Evgheni Dereveanchin (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1026?page=com.atlassian.jir... ]
Evgheni Dereveanchin reassigned OVIRT-1026:
-------------------------------------------
Assignee: Evgheni Dereveanchin (was: infra)
> mock_genconfig fails on fc25 due to missing requests library
> ------------------------------------------------------------
>
> Key: OVIRT-1026
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1026
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Reporter: Evgheni Dereveanchin
> Assignee: Evgheni Dereveanchin
> Priority: High
>
> Some jobs are failing on Fedora 25 slaves due to missing requests library:
> http://jenkins.ovirt.org/user/sbonazzo/my-views/view/Failing%20by%20relea...
> 16:39:15 + ./mock_genconfig --name=fedora-24-x86_64-custom --base=fedora-24-x86_64.cfg --option=basedir=/home/jenkins/workspace/vcredist-x86_4.1_create-rpms-fc24-x86_64_created/mock/ --try-proxy
> 16:39:16 Traceback (most recent call last):
> 16:39:16 File "./mock_genconfig", line 8, in <module>
> 16:39:16 import requests
> 16:39:16 ImportError: No module named requests
> 16:39:16 Build step 'Execute shell' marked build as failure
> In puppet code there seems to be a workaround to install requests but only on Fedora 24 - we need to check if this is needed for Fedora 25 as well
--
This message was sent by Atlassian JIRA
(v1000.695.1#100025)
7 years, 8 months
[JIRA] (OVIRT-1026) mock_genconfig fails on fc25 due to missing requests library
by Evgheni Dereveanchin (oVirt JIRA)
Evgheni Dereveanchin created OVIRT-1026:
-------------------------------------------
Summary: mock_genconfig fails on fc25 due to missing requests library
Key: OVIRT-1026
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1026
Project: oVirt - virtualization made easy
Issue Type: Bug
Reporter: Evgheni Dereveanchin
Assignee: infra
Priority: High
Some jobs are failing on Fedora 25 slaves due to missing requests library:
http://jenkins.ovirt.org/user/sbonazzo/my-views/view/Failing%20by%20relea...
16:39:15 + ./mock_genconfig --name=fedora-24-x86_64-custom --base=fedora-24-x86_64.cfg --option=basedir=/home/jenkins/workspace/vcredist-x86_4.1_create-rpms-fc24-x86_64_created/mock/ --try-proxy
16:39:16 Traceback (most recent call last):
16:39:16 File "./mock_genconfig", line 8, in <module>
16:39:16 import requests
16:39:16 ImportError: No module named requests
16:39:16 Build step 'Execute shell' marked build as failure
In puppet code there seems to be a workaround to install requests but only on Fedora 24 - we need to check if this is needed for Fedora 25 as well
--
This message was sent by Atlassian JIRA
(v1000.695.1#100025)
7 years, 8 months
Mass rebase 3 days before RC
by Sandro Bonazzola
Hi,
this Friday we have 1400 jobs in queue in jenkins while we never had more
than 100 jobs for the past 2 months. I initially thought it was ani nfra
issue but I double checked, there are 130 slaves working, the jobs are all
triggered by patches.
I hope that the eventual mass rebase is only for 4.2/master, I haven't
checked yet.
If the mass rebase is related to 4.1, I understand that having the release
candidate coming NEXT Monday many developers wants to ensure their patch
are included but really, you shouldn't wait the last second to push them.
If we want to build 4.1 RC on Monday please avoid to mush mass rebase over
the weekend until 4.1 is out or we won't have enough resources to build it.
Sorry for the rant.
Thanks,
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
7 years, 8 months
[JIRA] (OVIRT-1025) [URGENT] Jenkins queue up to 600 jobs with lots of unused slaves
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1025?page=com.atlassian.jir... ]
Barak Korren commented on OVIRT-1025:
-------------------------------------
Load seem to be due to ~20 engine patches sent at once, each running multiple upgrade jobs... probably not neccessary so maybe we should just abort the upgrade jobs if important tasks are starved atm.
> [URGENT] Jenkins queue up to 600 jobs with lots of unused slaves
> ----------------------------------------------------------------
>
> Key: OVIRT-1025
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1025
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: sbonazzo
> Assignee: infra
>
> Hi, this morning there are 639 jobs in queue and just 1 running build.
> This is critical with the upcoming 4.1 rc release coming.
> Please fix urgently!
> --
> 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.695.1#100025)
7 years, 8 months
[JIRA] (OVIRT-1025) [URGENT] Jenkins queue up to 600 jobs with lots of unused slaves
by sbonazzo (oVirt JIRA)
sbonazzo created OVIRT-1025:
-------------------------------
Summary: [URGENT] Jenkins queue up to 600 jobs with lots of unused slaves
Key: OVIRT-1025
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1025
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: sbonazzo
Assignee: infra
Hi, this morning there are 639 jobs in queue and just 1 running build.
This is critical with the upcoming 4.1 rc release coming.
Please fix urgently!
--
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.695.1#100025)
7 years, 8 months
oVirt infra daily report - unstable production jobs - 198
by jenkins＠jenkins.phx.ovirt.org
------=_Part_63_1964850859.1484262003830
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/198//artifact/exported...
Cheers,
Jenkins
------=_Part_63_1964850859.1484262003830
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 - 12/01/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-node-ng_ovirt-master-experimental_buil...">ovirt-node-ng_ovirt-master-experimental_build-artifacts-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>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-fc24-x...">ovirt-system-tests_master_check-patch-fc24-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>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/">ovirt_3.6_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;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt_3.6_image-ng-system-tests/">ovirt_3.6_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;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt_3.6_publish-rpms_nightly/">ovirt_3.6_publish-rpms_nightly</a>
</td><td>
Collects RPMs from all oVirt projects (3.6 branches) and publish them to resources.ovirt.org yum repository.<br> 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/ovirt_3.6_system-tests/">ovirt_3.6_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;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/">ovirt_4.0_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;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt_4.1_system-tests/">ovirt_4.1_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;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt_master_system-tests_manual/">ovirt_master_system-tests_manual</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/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;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/repos_master_check-closure_fc24_merged/">repos_master_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;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/system-backup_jenkins_old_ovirt_org/">system-backup_jenkins_old_ovirt_org</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/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;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/">test-repo_ovirt_experimental_4.0</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_63_1964850859.1484262003830--
7 years, 8 months
[JIRA] (OVIRT-1021) Trigger a job on a github repo change
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1021?page=com.atlassian.jir... ]
Barak Korren commented on OVIRT-1021:
-------------------------------------
[~fdeutsch] The problem with freeform jobs is that they get unmaintained fast. But we do accept patches to the 'jenkins' repo, so you can make any job you like as long as you write it in JJB YAML.
I don't think Standard-CI and Travis are fully interchangable, for example, Travis lets you ask for a Docker image to run your tests on, in Standard-CI you specify environment in terms of OS, repos and packages you want. Travis also gives you pre-baked steps for interacting with various systems, in standard CI we just let you run a script which can be limiting or liberating depending on how you look at it (We do support interacting with certain systems on your behalf, depending on the artifacts you leave behind).
Given the simplicity of Standard-CI, I think it would be possible to write a .travis.yaml file that implements it, but probably not the other way around. Then again, if you already have your CI defined in "Standard-CI" terms, you might as well let the oVirt Jenkins run it...
But before we go any further I would like to hear a more detailed description of what you are looking to do, to better understand if it fits into the standard CI framework, or if its more of an OST type of thing.
> Trigger a job on a github repo change
> -------------------------------------
>
> Key: OVIRT-1021
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1021
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Reporter: Fabian Deutsch
> Assignee: infra
>
> Hey,
> we are pushing some changes to this github repository:
> https://github.com/kubevirt/demo
> The test autpmation requires nesting, thus it would be nice if this repo could be run on jenkins.
> Could our jenkins instance get a plugin to be able to hook it up to github i.e.
> https://wiki.jenkins-ci.org/display/JENKINS/GitHub+plugin
> The other thing would be how to store the job specification in the repo.
> Here it would be nice if we could dump a travis-ci-like file into the repo and let the job inerprete this.
--
This message was sent by Atlassian JIRA
(v1000.692.0#100025)
7 years, 8 months
