I see the problem on Windows and Linux slaves
On Jul 9, 2014 8:07 AM, "Steve K" wrote:
> Mark,
>
> To be clear, are you saying you see it with both Windows and Linux *servers
> *(vs. slaves)?
>
> Thanks for the link to the reported issue. There is some comfort in
> knowing you're not alone and th
Mark,
To be clear, are you saying you see it with both Windows and Linux *servers
*(vs. slaves)?
Thanks for the link to the reported issue. There is some comfort in knowing
you're not alone and that, maybe, someone is looking into the problem.
Regards,
Steve K.
--
You received this message
I see the problem on both Windows and Linux.
Mark Waite
On Wed, Jul 9, 2014 at 7:47 AM, Steve K
wrote:
> Thanks Mark,
>
> Just curious. Are you on a Windows server? We recently moved from a Linux
> to a Windows server. We never saw the problem when we were on the Linux
> server.
>
> Regards,
Thanks Mark,
Just curious. Are you on a Windows server? We recently moved from a Linux
to a Windows server. We never saw the problem when we were on the Linux
server.
Regards,
Steve K.
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
I've seen the same problem, and Thomas Carsuzan has seen the same problem.
https://issues.jenkins-ci.org/browse/JENKINS-16737 is being used to track
the issue.
The usual work around is to build again, or to wipe the workspace and build
again. It is still not clear what is causing the problem, si
Hello,
Have any other 'Git' users seen this problem?
We are at Jenkins v1.554.3 with Git Plugin v 2.2.2, Git Parameter Plugin v
0.3.2, and Git Client Plugin v 1.9.1
The problem occurs at the very end of the job, when it is attempting to
send job success notices to the developers who committed c
