Hi everyone, this week updates:
* Jenkins slaves stabilized
After last week's upgrade, some of the slaves got wrongly configured,
during this week all the slaves have been checked and fixed any issues
found.
* Artifactory migration
We are migrating to an artifactory server on
On Mon, Nov 30, 2015 at 2:11 PM, Dan Kenigsberg wrote:
> On Mon, Nov 30, 2015 at 01:11:25PM +0100, Sandro Bonazzola wrote:
> > On Thu, Nov 12, 2015 at 9:34 AM, Sandro Bonazzola
> > wrote:
> >
> > > Hi,
> > > can we drop FC22 testing in jenkins now that
Hi team,
Back in the day, somewhere between the discovery of fire and the wheel,
Java 5 introduced generics. This was a great step forwards, but also
created some of the most horrible boiler-plated code you could imagine:
Map = new HashMap();
Java 7
The oVirt Project is pleased to announce the availability
of the oVirt 3.5.6 Final Release as of December 1st, 2015.
This release is available now for
Red Hat Enterprise Linux 6.7, CentOS Linux 6.7 (or similar) and
Red Hat Enterprise Linux 7.1, CentOS Linux 7.1 (or similar).
This release
On 12/01/2015 09:28 AM, Yevgeny Zaspitsky wrote:
On Dec 1, 2015 3:47 PM, "Ravi Nori" > wrote:
>
> Hi,
>
> Some of you have faced issues setting up engine after SSO patches
were merged.
>
> Below are the issues and the proposed solutions on how to
On Tue, Dec 1, 2015 at 2:47 PM, Ravi Nori wrote:
> Hi,
>
> Some of you have faced issues setting up engine after SSO patches were
> merged.
>
> Below are the issues and the proposed solutions on how to proceed.
>
> * Issue #1: Host name resolution.
>
> During setup make sure
Hi,
due to the release of recent 3.6.0 major release of the oVirt project,
and upcoming release of its first maintenance release 3.6.1,
the last 3.5 release is 3.5.6 we released today.
We recommend anyone hitting issued existing in 3.5
to upgrade to 3.6 to get the fixes since 3.5 won't receive
Hi,
Some of you have faced issues setting up engine after SSO patches were
merged.
Below are the issues and the proposed solutions on how to proceed.
* Issue #1: Host name resolution.
During setup make sure the engine FQDN that you provide can be resolved.
If it cannot be resolved
On Dec 1, 2015 3:47 PM, "Ravi Nori" wrote:
>
> Hi,
>
> Some of you have faced issues setting up engine after SSO patches were
merged.
>
> Below are the issues and the proposed solutions on how to proceed.
>
> * Issue #1: Host name resolution.
>
> During setup make sure the