### Logwatch 7.3.6 (05/19/07)
Processing Initiated: Sun Sep 29 03:13:25 2013
Date Range Processed: yesterday
( 2013-Sep-28 )
Period is day.
Detail Level of Output: 0
- Original Message -
> From: "Dan Kenigsberg"
> To: "Ohad Basan"
> Cc: "infra"
> Sent: Wednesday, September 25, 2013 1:29:01 PM
> Subject: Re: full sudo access to centos64 jenkins slave
>
> On Wed, Sep 25, 2013 at 05:36:46AM -0400, Ohad Basan wrote:
> > Hello
> >
> > i'd like to run t
Hey,
I recall wiki page that explains the usage of vdsmfake
(http://www.ovirt.org/VDSM_Fake)
Can you share it in the README file and locate it in the root folder of the
repository ?
or even add short instructions summary in a README of how to run and work with
the utility?
might be helpful
Tha
All,
Is there static analysis tool used for oVirt code base?
There is interesting tool called Sonar: http://www.sonarqube.org/. It
integrates with Jenkins and provides you neat dashboard that will let you
understand code quality. This tool supports many languages including Java
and Python.
Thank
Hi Piotr,
Currently, we employ several static analysis tools in the various oVirt
projects.
In oVirt-Engine:
1. We use checkstyle at build time with several standard checks, and a couple
implemented by project members
2. FindBugs is run by a Jenkins job:
http://jenkins.ovirt.org/view/All/j
Allon,
Sonar is similar to findbugs but it gives you code duplication, complexity,
coverage and help you understand how metrics change over the time.
There is a bit "noise" with default configuration but it can be nicely
tuned: http://www.sonarqube.org/screencasts/configuring-coding-rules/
you can
Project: http://jenkins.ovirt.org/job/ovirt-engine-cli_create_rpms/
Build: http://jenkins.ovirt.org/job/ovirt-engine-cli_create_rpms/189/
Build Number: 189
Build Status: Still Failing
Triggered By: Started by user eyal edri
-
Changes Since Last Success:
--
Project:
http://jenkins.ovirt.org/job/ovirt-engine-cli_create_rpms/./label=centos64/
Build:
http://jenkins.ovirt.org/job/ovirt-engine-cli_create_rpms/./label=centos64/189/
Build Number: 189
Build Status: Still Failing
Triggered By: Started by upstream project "ovirt-engine-cli_create_rpms" buil
fyi,
new maven repository is up and running at
http://artifactory.ovirt.org:8081/artifactory.
next step is to use it as proxy for running jenkins jobs. (after testing)
maven2 repo proxy is located at:
http://artifactory.ovirt.org:8081/artifactory/repo1
options are:
1. adding new profile in po
- Original Message -
> From: "Eyal Edri"
> To: "infra"
> Sent: Sunday, September 29, 2013 10:36:53 PM
> Subject: [ANN] new artifcatory.ovirt.org server is up and running
>
> fyi,
>
> new maven repository is up and running at
> http://artifactory.ovirt.org:8081/artifactory.
> next step
- Original Message -
> From: "Alon Bar-Lev"
> To: "Eyal Edri"
> Cc: "infra"
> Sent: Sunday, September 29, 2013 10:40:17 PM
> Subject: Re: [ANN] new artifcatory.ovirt.org server is up and running
>
>
>
> - Original Message -
> > From: "Eyal Edri"
> > To: "infra"
> > Sent: S
- Original Message -
> From: "Eyal Edri"
> To: "Alon Bar-Lev"
> Cc: "infra"
> Sent: Sunday, September 29, 2013 10:48:48 PM
> Subject: Re: [ANN] new artifcatory.ovirt.org server is up and running
>
>
>
> - Original Message -
> > From: "Alon Bar-Lev"
> > To: "Eyal Edri"
> >
Project: ${PROJECT_URL}
Build: ${BUILD_URL}
Build Number: ${BUILD_NUMBER}
Build Status: ${BUILD_STATUS}
Triggered By: ${CAUSE}
-
Changes Since Last Success:
-
${CHANGES_SINCE_LAST_SUCCESS}
-
Failed Tests:
--
Project: http://jenkins.ovirt.org/job/check_gerrit_ovirt_org/
Build: http://jenkins.ovirt.org/job/check_gerrit_ovirt_org/79335/
Build Number: 79335
Build Status: Fixed
Triggered By: Started by timer
-
Changes Since Last Success:
---
Project: http://jenkins.ovirt.org/job/check_gerrit_ovirt_org/
Build: http://jenkins.ovirt.org/job/check_gerrit_ovirt_org/79333/
Build Number: 79333
Build Status: Failure
Triggered By: Started by timer
-
Changes Since Last Success:
-
Project: http://jenkins.ovirt.org/job/ovirt-engine-cli_create_rpms/
Build: http://jenkins.ovirt.org/job/ovirt-engine-cli_create_rpms/191/
Build Number: 191
Build Status: Failure
Triggered By: Started by an SCM change
-
Changes Since Last Success:
-
Hi,
Fedora 20 Alpha has been released and can be downloaded from
http://fedoraproject.org/get-prerelease.
I think it's time to start running our tests and build nightly also on Fedora
20 in order to discover
possible compatibility issues.
Can infra provide a Fedora 20 VM for jenkins use?
Thanks,
17 matches
Mail list logo
