7 Jun
2016
7 Jun
'16
7:24 a.m.
On 6 June 2016 at 18:11, Eyal Edri <eedri@redhat.com> wrote:
OK, i took it offline for now, let me know if you see the issue again.
On Mon, Jun 6, 2016 at 2:09 PM, Tal Nisan <tnisan@redhat.com> wrote:
Regardless, note that this specific Jenkins slave probably has an older JDK since it cannot work with 1.8
There is no such thing. All slaves have JDK 1.6, 1.7 and 1.8 as available on the OS (This had been Puppet-enforced for a long time). The job itself was not configured to require JDK 1.8 (Nor was it restricted to EL7 and up as it should be for engine >= 4). I've re-enabled the slave and configured the job accordingly. -- Barak Korren bkorren@redhat.com RHEV-CI Team