premissions for my jenkins user
by Ido Rosenzwig
Hi,
I wish to have trigger (and re-trigger) premissions on my jenkins user.
my user is : irosenzw
Best regards,
Ido Rosenzwig
8 years, 4 months
ovirt-engine_master_coverity-analysis is broken
by Barak Korren
Hi Sharon,
The $subject job started failing and Eyal told me you worked on it
recently. I'm not sure your changed made it fail because I saw changes
by both you and Sandro.
Anyway the problem with the jobs seems to be that the jenkins repo URL
was set to:
git:///jenkins.git
Instead of:
git://gerrit.ovirt.org/jenkins.git
I fixed this manually but it is still failing. Now it seems that it is
not getting the right thing from:
https://scan.coverity.com/download/linux-64
I can't find any docs about this when looking quickly at coverity`s
website, so I'm hoping you know more about this.
--
Barak Korren
bkorren(a)redhat.com
RHEV-CI Team
8 years, 4 months
oVirt 4.0.2 RC1 merge / branch / tag / bugzilla reminder
by Sandro Bonazzola
All stable branch maintainers, please make sure to
- merge all relevant open bugs until Wednesday morning 11:00 AM TLV time.
For each package that need to be built (i.e oVirt product) please make sure
every bug in MODIFIED has the right Target Release and Target Milestone.
A Target release should state the version of the package you're building
and should include the same version you used for the tag you just used for
this build. (e.g. for ovirt-engine, tag: ovirt-engine-4.0.2, tr: 4.0.2)
A list of bugs that require attention is here:
-
https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A4....
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
8 years, 4 months
RHEVM CI Jenkins daily report - 18
by jenkins＠jenkins.phx.ovirt.org
------=_Part_362_1346657207.1468882803657
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/18//artifact/exported-...
Cheers,
Jenkins
------=_Part_362_1346657207.1468882803657
Content-Type: application/octet-stream; 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 - 18/07/2016
</th></tr><tr><th colspan=2 class=sub>
<font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Jobs (Production)</a></font>
</th></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt-engine_3.6_check-merged-fc23-x86_64/">ovirt-engine_3.6_check-merged-fc23-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-engine_master_coverity-analysis/">ovirt-engine_master_coverity-analysis</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-node-ng_master_build-artifacts-fc24-x8...">ovirt-node-ng_master_build-artifacts-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-node-ng_ovirt-3.6_build-artifacts-fc23...">ovirt-node-ng_ovirt-3.6_build-artifacts-fc23-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-node-ng_ovirt-4.0_build-artifacts-fc22...">ovirt-node-ng_ovirt-4.0_build-artifacts-fc22-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-node-ng_ovirt-4.0_build-artifacts-fc23...">ovirt-node-ng_ovirt-4.0_build-artifacts-fc23-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-node-plugin-hosted-engine_ovirt-3.6_ch...">ovirt-node-plugin-hosted-engine_ovirt-3.6_check-merged-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/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/vdsm_master_check-merged-fc24-x86_64/">vdsm_master_check-merged-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>
------=_Part_362_1346657207.1468882803657--
8 years, 4 months
[Jenkins] Passing parameters to build-artifacts.sh
by Vojtech Szocs
Hi,
I'm just curious whether it's possible to do the following:
Let's say we have a project (ovirt-engine-dashboard) built by Jenkins,
which means there's a Jenkins job that runs build-artifacts.sh script
whenever a patch gets merged via gerrit.
Can we somehow pass custom parameters to build-artifacts.sh for such
(Jenkins CI) builds?
For example, putting something like this into commit message:
My-Param 123
would reflect into `My-Param` env. variable when running the script?
Motivation: for release builds (which shouldn't contain the "snapshot"
part [*] in RPM release string), pass parameter to build-artifacts.sh
that ensures the "snapshot" part is empty. This way, we don't need to
patch the project prior to release (remove "snapshot" in spec) & then
patch it again after the release (re-add "snapshot" in spec).
[*] {date}git{commit}
Thanks,
Vojtech
8 years, 4 months
Re: Forgotten Patches in project ovirt-engine
by Michal Skrivanek
can you please abandon this and any other Eldan’s patches which are still out there? They have been already addressed by other means
Thanks,
michal
> On 17 Jul 2016, at 03:56, noreply+patchwatcher(a)ovirt.org wrote:
>
> The following patches did not have any activity for over 90 days, please consider nudging for more attention.
> http://gerrit.ovirt.org/42867
>
>
8 years, 4 months
