Hi
Thanks I have updated the slave and remoting to 2.53.3 and jenkins to 1.652
, the error is gone
but now i am facing issue another issue , when i am trying to launch slave
node from slave machine it throws me below exception
I am login as admin on slave machine , I am able to access dashbo
Jenkins is on 1.624 ...
On Tuesday, March 8, 2016 at 8:03:03 PM UTC, Daniel Beck wrote:
>
>
> On 08.03.2016, at 19:21, Prashant Sawant >
> wrote:
>
> > I am facing same issue ... my slave,jar and remoting.jar are both on
> 2.52 , still it's giving me security issue
>
> Time to update Jenkins.
On 08.03.2016, at 19:21, Prashant Sawant wrote:
> I am facing same issue ... my slave,jar and remoting.jar are both on 2.52 ,
> still it's giving me security issue
Time to update Jenkins. Even the no longer supported 1.625.x LTS release line
is on 2.53.2.
--
You received this message becaus
Jenkins master is hosted on Windows server 2012 and I am trying installing
slave on separate Windows Server 2012
On Tuesday, March 8, 2016 at 6:21:26 PM UTC, Prashant Sawant wrote:
>
> Hi There ,
> I am facing same issue ... my slave,jar and remoting.jar are both on 2.52
> , still it's giving m
Hi There ,
I am facing same issue ... my slave,jar and remoting.jar are both on 2.52 ,
still it's giving me security issue
can you please advice
Thanks
Prashant
On Wednesday, July 22, 2015 at 7:33:06 PM UTC+1, Kohsuke Kawaguchi wrote:
>
> Yes, my code signing certificate expired.
>
> Up until
, 2015 1:33 PM
To: Jenkins Users
Subject: Re: Jenkins Remoting Agent - Expired Certificate
Yes, my code signing certificate expired.
Up until about 2 years ago, I was signing these bits without including the
timestamp. That has the unfortunate side effect of invalidating the signature
when my
Yes, my code signing certificate expired.
Up until about 2 years ago, I was signing these bits without including the
timestamp. That has the unfortunate side effect of invalidating the
signature when my certificate expires, which happens sooner or later.
Since then I have modified the signing p
Has anyone else encountered this?
We're running Jenkins LTS 1.554.3 and Java Server SDK 7u72 on a Windows 2008
Server, and Java 7u72 on the slave workstations. When we restarted our server
yesterday none of our slaves connected via DCOM. They never made it past the
first (Connecting to ...) or
