subject:"Windows slave"

On Mon, Aug 5, 2019 at 9:33 AM Shubham Bansal  wrote:

>
> https://pastebin.com/yzL2vE9g
> Did you see these logs?
>
>
Yes. Did you see my quote from those logs in my reply 5 August 2019
18:17:05 UTC+5:30?

I don't have anything else to offer.  There are thousands of installations
successfully running Jenkins masters and Jenkins agents on different
machines using the same connection technique you're using.  I've made my
guesses about what might be different in your environment compared to those
other installations.

Mark Waite


>
> On Monday, 5 August 2019 21:01:46 UTC+5:30, Mark Waite wrote:
>>
>>
>>
>> On Mon, Aug 5, 2019 at 6:54 AM Shubham Bansal  wrote:
>>
>>> The protocol is chosen as "Inbound TCP Agent Protocol/4 (TLS
>>> encryption)" with fixed port "5378".
>>>
>>
>> That's a reasonable configuration.  That is listed as an unassigned port
>> in at least one of the ports databases
>> <https://www.speedguide.net/port.php?port=5378>, so it should be
>> reasonable to use that port number.
>>
>>
>>> What can possibly be an issue here?
>>>
>>
>> Something on the agent could be killing the agent process.
>> Something on the network between the agent and the master could be
>> breaking or damaging the communication.
>> Something on the master could be breaking or damaging the communication
>> between the agent and the master.
>>
>>
>>> And you have mentioned that something is changing the configuration, is
>>> there a way to figure that out what is the cause?
>>>
>>
>> Unless you see protocol 4 listed as disabled, then it is unlikely that
>> anything has changed the configuration.  I was speculating that something
>> might be changing the configuration, but if something is changing the
>> configuration, then you should see the protocol listed as 'disabled'
>> instead of 'enabled'.
>>
>> Mark Waite
>>
>>
>>>
>>> On Monday, 5 August 2019 18:17:05 UTC+5:30, Mark Waite wrote:
>>>>
>>>> When the master log says:
>>>>
>>>>
>>>>1. Aug 05, 2019 8:54:51 AM hudson.remoting.jnlp.Main$CuiListener
>>>>error
>>>>2. SEVERE: The server rejected the connection: None of the
>>>>protocols were accepted
>>>>3. java.lang.Exception: The server rejected the connection: None of
>>>>the protocols were accepted
>>>>4. at
>>>>hudson.remoting.Engine.onConnectionRejected(Engine.java:682)
>>>>5. at hudson.remoting.Engine.innerRun(Engine.java:639)
>>>>6. at hudson.remoting.Engine.run(Engine.java:474)
>>>>
>>>>
>>>> that might hint that either something is damaging the communication
>>>> between the agent or something is changing the configuration of the master
>>>> to reject agent protocols that were previously accepted.  The protocols
>>>> which are accepted can be modified from a "Configure Global Security" page
>>>> of "Manage Jenkins".  The "Agents" section of that page includes a link to
>>>> enable and disable specific protocols.
>>>>
>>>> On Mon, Aug 5, 2019 at 6:29 AM Shubham Bansal 
>>>> wrote:
>>>>
>>>>> https://pastebin.com/ib0PK5af
>>>>>
>>>>> Can you tell me more from these logs of the slave windows machine?
>>>>>
>>>>>
>>>>> On Monday, 5 August 2019 17:42:23 UTC+5:30, Mark Waite wrote:
>>>>>>
>>>>>> Connecting the agent to the master *is* a robust way to connect.
>>>>>> Many users around the world use that method to connect agents to masters,
>>>>>> including Windows masters, Linux masters, and other platforms.
>>>>>>
>>>>>> If the agent is being disconnected after some time, there may be
>>>>>> something on the agent computer which kills the client process that runs 
>>>>>> on
>>>>>> the agent (for example, some program that won't allow Java programs to 
>>>>>> run
>>>>>> for an extended period).  If the agent process dies or is killed on the
>>>>>> agent computer, the agent will be disconnected.  If you're running the
>>>>>> agent process from the command line, then you may find hints to the cause
>>>>>> of the command line failure in the command prompt window that launched 
>>>

Re: Azure windows slave keeps disconnecting


https://pastebin.com/yzL2vE9g
Did you see these logs?


On Monday, 5 August 2019 21:01:46 UTC+5:30, Mark Waite wrote:
>
>
>
> On Mon, Aug 5, 2019 at 6:54 AM Shubham Bansal  > wrote:
>
>> The protocol is chosen as "Inbound TCP Agent Protocol/4 (TLS 
>> encryption)" with fixed port "5378". 
>>
>
> That's a reasonable configuration.  That is listed as an unassigned port 
> in at least one of the ports databases 
> <https://www.speedguide.net/port.php?port=5378>, so it should be 
> reasonable to use that port number.
>  
>
>> What can possibly be an issue here?
>>
>
> Something on the agent could be killing the agent process.
> Something on the network between the agent and the master could be 
> breaking or damaging the communication.
> Something on the master could be breaking or damaging the communication 
> between the agent and the master.
>  
>
>> And you have mentioned that something is changing the configuration, is 
>> there a way to figure that out what is the cause?
>>
>
> Unless you see protocol 4 listed as disabled, then it is unlikely that 
> anything has changed the configuration.  I was speculating that something 
> might be changing the configuration, but if something is changing the 
> configuration, then you should see the protocol listed as 'disabled' 
> instead of 'enabled'.
>
> Mark Waite
>  
>
>>
>> On Monday, 5 August 2019 18:17:05 UTC+5:30, Mark Waite wrote:
>>>
>>> When the master log says:
>>>
>>>
>>>1. Aug 05, 2019 8:54:51 AM hudson.remoting.jnlp.Main$CuiListener 
>>>error
>>>2. SEVERE: The server rejected the connection: None of the protocols 
>>>were accepted
>>>3. java.lang.Exception: The server rejected the connection: None of 
>>>the protocols were accepted
>>>4. at 
>>>hudson.remoting.Engine.onConnectionRejected(Engine.java:682)
>>>5. at hudson.remoting.Engine.innerRun(Engine.java:639)
>>>6. at hudson.remoting.Engine.run(Engine.java:474)
>>>
>>>
>>> that might hint that either something is damaging the communication 
>>> between the agent or something is changing the configuration of the master 
>>> to reject agent protocols that were previously accepted.  The protocols 
>>> which are accepted can be modified from a "Configure Global Security" page 
>>> of "Manage Jenkins".  The "Agents" section of that page includes a link to 
>>> enable and disable specific protocols.
>>>
>>> On Mon, Aug 5, 2019 at 6:29 AM Shubham Bansal  
>>> wrote:
>>>
>>>> https://pastebin.com/ib0PK5af
>>>>
>>>> Can you tell me more from these logs of the slave windows machine?
>>>>
>>>>
>>>> On Monday, 5 August 2019 17:42:23 UTC+5:30, Mark Waite wrote:
>>>>>
>>>>> Connecting the agent to the master *is* a robust way to connect.  
>>>>> Many users around the world use that method to connect agents to masters, 
>>>>> including Windows masters, Linux masters, and other platforms.
>>>>>
>>>>> If the agent is being disconnected after some time, there may be 
>>>>> something on the agent computer which kills the client process that runs 
>>>>> on 
>>>>> the agent (for example, some program that won't allow Java programs to 
>>>>> run 
>>>>> for an extended period).  If the agent process dies or is killed on the 
>>>>> agent computer, the agent will be disconnected.  If you're running the 
>>>>> agent process from the command line, then you may find hints to the cause 
>>>>> of the command line failure in the command prompt window that launched 
>>>>> the 
>>>>> agent.  If you're running the agent process by clicking the "Launch" 
>>>>> button 
>>>>> to launch the agent from the browser, you may want to try running the 
>>>>> agent 
>>>>> from the command line instead, just in case some diagnostic messages 
>>>>> might 
>>>>> help you.
>>>>>
>>>>> There may be something in the networking definition between the master 
>>>>> and the agents which is causing the agent process to die.  Usually, when 
>>>>> the network connection is interrupted between a master and  agent 
>>>>> launched 
>>>>> to connect to the master.  Th

Re: Azure windows slave keeps disconnecting

On Mon, Aug 5, 2019 at 6:54 AM Shubham Bansal  wrote:

> The protocol is chosen as "Inbound TCP Agent Protocol/4 (TLS encryption)"
> with fixed port "5378".
>

That's a reasonable configuration.  That is listed as an unassigned port in
at least one of the ports databases
<https://www.speedguide.net/port.php?port=5378>, so it should be reasonable
to use that port number.


> What can possibly be an issue here?
>

Something on the agent could be killing the agent process.
Something on the network between the agent and the master could be breaking
or damaging the communication.
Something on the master could be breaking or damaging the communication
between the agent and the master.


> And you have mentioned that something is changing the configuration, is
> there a way to figure that out what is the cause?
>

Unless you see protocol 4 listed as disabled, then it is unlikely that
anything has changed the configuration.  I was speculating that something
might be changing the configuration, but if something is changing the
configuration, then you should see the protocol listed as 'disabled'
instead of 'enabled'.

Mark Waite


>
> On Monday, 5 August 2019 18:17:05 UTC+5:30, Mark Waite wrote:
>>
>> When the master log says:
>>
>>
>>1. Aug 05, 2019 8:54:51 AM hudson.remoting.jnlp.Main$CuiListener error
>>2. SEVERE: The server rejected the connection: None of the protocols
>>were accepted
>>3. java.lang.Exception: The server rejected the connection: None of
>>the protocols were accepted
>>4. at hudson.remoting.Engine.onConnectionRejected(Engine.java:682)
>>5. at hudson.remoting.Engine.innerRun(Engine.java:639)
>>6. at hudson.remoting.Engine.run(Engine.java:474)
>>
>>
>> that might hint that either something is damaging the communication
>> between the agent or something is changing the configuration of the master
>> to reject agent protocols that were previously accepted.  The protocols
>> which are accepted can be modified from a "Configure Global Security" page
>> of "Manage Jenkins".  The "Agents" section of that page includes a link to
>> enable and disable specific protocols.
>>
>> On Mon, Aug 5, 2019 at 6:29 AM Shubham Bansal  wrote:
>>
>>> https://pastebin.com/ib0PK5af
>>>
>>> Can you tell me more from these logs of the slave windows machine?
>>>
>>>
>>> On Monday, 5 August 2019 17:42:23 UTC+5:30, Mark Waite wrote:
>>>>
>>>> Connecting the agent to the master *is* a robust way to connect.  Many
>>>> users around the world use that method to connect agents to masters,
>>>> including Windows masters, Linux masters, and other platforms.
>>>>
>>>> If the agent is being disconnected after some time, there may be
>>>> something on the agent computer which kills the client process that runs on
>>>> the agent (for example, some program that won't allow Java programs to run
>>>> for an extended period).  If the agent process dies or is killed on the
>>>> agent computer, the agent will be disconnected.  If you're running the
>>>> agent process from the command line, then you may find hints to the cause
>>>> of the command line failure in the command prompt window that launched the
>>>> agent.  If you're running the agent process by clicking the "Launch" button
>>>> to launch the agent from the browser, you may want to try running the agent
>>>> from the command line instead, just in case some diagnostic messages might
>>>> help you.
>>>>
>>>> There may be something in the networking definition between the master
>>>> and the agents which is causing the agent process to die.  Usually, when
>>>> the network connection is interrupted between a master and  agent launched
>>>> to connect to the master.  This seems less likely to be the problem, since
>>>> you mentioned that the when running as a restart, the service restarted
>>>> frequently.
>>>>
>>>> On Mon, Aug 5, 2019 at 5:46 AM Shubham Bansal 
>>>> wrote:
>>>>
>>>>> I have a Linux Azure machine as master and it connects to the windows
>>>>> slave machine using the option "Launch Agent by connecting it to master"
>>>>>
>>>>> This connects the agent fine but gets disconnected after some time
>>>>> (around 20-30 minutes). I tried running the agent as windows service but
>>>>> the service keeps restarting freque

Re: Azure windows slave keeps disconnecting

https://pastebin.com/yzL2vE9g

On Monday, 5 August 2019 18:17:05 UTC+5:30, Mark Waite wrote:
>
> When the master log says:
>
>
>1. Aug 05, 2019 8:54:51 AM hudson.remoting.jnlp.Main$CuiListener error
>2. SEVERE: The server rejected the connection: None of the protocols 
>were accepted
>3. java.lang.Exception: The server rejected the connection: None of 
>the protocols were accepted
>4. at hudson.remoting.Engine.onConnectionRejected(Engine.java:682)
>5. at hudson.remoting.Engine.innerRun(Engine.java:639)
>6. at hudson.remoting.Engine.run(Engine.java:474)
>
>
> that might hint that either something is damaging the communication 
> between the agent or something is changing the configuration of the master 
> to reject agent protocols that were previously accepted.  The protocols 
> which are accepted can be modified from a "Configure Global Security" page 
> of "Manage Jenkins".  The "Agents" section of that page includes a link to 
> enable and disable specific protocols.
>
> On Mon, Aug 5, 2019 at 6:29 AM Shubham Bansal  > wrote:
>
>> https://pastebin.com/ib0PK5af
>>
>> Can you tell me more from these logs of the slave windows machine?
>>
>>
>> On Monday, 5 August 2019 17:42:23 UTC+5:30, Mark Waite wrote:
>>>
>>> Connecting the agent to the master *is* a robust way to connect.  Many 
>>> users around the world use that method to connect agents to masters, 
>>> including Windows masters, Linux masters, and other platforms.
>>>
>>> If the agent is being disconnected after some time, there may be 
>>> something on the agent computer which kills the client process that runs on 
>>> the agent (for example, some program that won't allow Java programs to run 
>>> for an extended period).  If the agent process dies or is killed on the 
>>> agent computer, the agent will be disconnected.  If you're running the 
>>> agent process from the command line, then you may find hints to the cause 
>>> of the command line failure in the command prompt window that launched the 
>>> agent.  If you're running the agent process by clicking the "Launch" button 
>>> to launch the agent from the browser, you may want to try running the agent 
>>> from the command line instead, just in case some diagnostic messages might 
>>> help you.
>>>
>>> There may be something in the networking definition between the master 
>>> and the agents which is causing the agent process to die.  Usually, when 
>>> the network connection is interrupted between a master and  agent launched 
>>> to connect to the master.  This seems less likely to be the problem, since 
>>> you mentioned that the when running as a restart, the service restarted 
>>> frequently.
>>>
>>> On Mon, Aug 5, 2019 at 5:46 AM Shubham Bansal  
>>> wrote:
>>>
>>>> I have a Linux Azure machine as master and it connects to the windows 
>>>> slave machine using the option "Launch Agent by connecting it to master"
>>>>
>>>> This connects the agent fine but gets disconnected after some time 
>>>> (around 20-30 minutes). I tried running the agent as windows service but 
>>>> the service keeps restarting frequently causing the build to fail of it is 
>>>> triggered at this time of restart process. 
>>>>
>>>> Can someone here suggest a more robust way to connect?
>>>>
>>>>
>>>> -- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "Jenkins Users" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to jenkins...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/jenkinsci-users/245d1ca6-c04a-469d-a3c3-5ee1e96ba966%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/jenkinsci-users/245d1ca6-c04a-469d-a3c3-5ee1e96ba966%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>>
>>>
>>> -- 
>>> Thanks!
>>> Mark Waite
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkins...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/a1bcedbd-1fa4-4bf2-866e-7652d4d6c98e%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/a1bcedbd-1fa4-4bf2-866e-7652d4d6c98e%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>
>
> -- 
> Thanks!
> Mark Waite
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a84ee633-920b-462c-9243-cd5e56542bd0%40googlegroups.com.

Re: Azure windows slave keeps disconnecting

The protocol is chosen as "Inbound TCP Agent Protocol/4 (TLS encryption)" 
with fixed port "5378". 
What can possibly be an issue here?
And you have mentioned that something is changing the configuration, is 
there a way to figure that out what is the cause?

On Monday, 5 August 2019 18:17:05 UTC+5:30, Mark Waite wrote:
>
> When the master log says:
>
>
>1. Aug 05, 2019 8:54:51 AM hudson.remoting.jnlp.Main$CuiListener error
>2. SEVERE: The server rejected the connection: None of the protocols 
>were accepted
>3. java.lang.Exception: The server rejected the connection: None of 
>the protocols were accepted
>4. at hudson.remoting.Engine.onConnectionRejected(Engine.java:682)
>5. at hudson.remoting.Engine.innerRun(Engine.java:639)
>6. at hudson.remoting.Engine.run(Engine.java:474)
>
>
> that might hint that either something is damaging the communication 
> between the agent or something is changing the configuration of the master 
> to reject agent protocols that were previously accepted.  The protocols 
> which are accepted can be modified from a "Configure Global Security" page 
> of "Manage Jenkins".  The "Agents" section of that page includes a link to 
> enable and disable specific protocols.
>
> On Mon, Aug 5, 2019 at 6:29 AM Shubham Bansal  > wrote:
>
>> https://pastebin.com/ib0PK5af
>>
>> Can you tell me more from these logs of the slave windows machine?
>>
>>
>> On Monday, 5 August 2019 17:42:23 UTC+5:30, Mark Waite wrote:
>>>
>>> Connecting the agent to the master *is* a robust way to connect.  Many 
>>> users around the world use that method to connect agents to masters, 
>>> including Windows masters, Linux masters, and other platforms.
>>>
>>> If the agent is being disconnected after some time, there may be 
>>> something on the agent computer which kills the client process that runs on 
>>> the agent (for example, some program that won't allow Java programs to run 
>>> for an extended period).  If the agent process dies or is killed on the 
>>> agent computer, the agent will be disconnected.  If you're running the 
>>> agent process from the command line, then you may find hints to the cause 
>>> of the command line failure in the command prompt window that launched the 
>>> agent.  If you're running the agent process by clicking the "Launch" button 
>>> to launch the agent from the browser, you may want to try running the agent 
>>> from the command line instead, just in case some diagnostic messages might 
>>> help you.
>>>
>>> There may be something in the networking definition between the master 
>>> and the agents which is causing the agent process to die.  Usually, when 
>>> the network connection is interrupted between a master and  agent launched 
>>> to connect to the master.  This seems less likely to be the problem, since 
>>> you mentioned that the when running as a restart, the service restarted 
>>> frequently.
>>>
>>> On Mon, Aug 5, 2019 at 5:46 AM Shubham Bansal  
>>> wrote:
>>>
>>>> I have a Linux Azure machine as master and it connects to the windows 
>>>> slave machine using the option "Launch Agent by connecting it to master"
>>>>
>>>> This connects the agent fine but gets disconnected after some time 
>>>> (around 20-30 minutes). I tried running the agent as windows service but 
>>>> the service keeps restarting frequently causing the build to fail of it is 
>>>> triggered at this time of restart process. 
>>>>
>>>> Can someone here suggest a more robust way to connect?
>>>>
>>>>
>>>> -- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "Jenkins Users" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to jenkins...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/jenkinsci-users/245d1ca6-c04a-469d-a3c3-5ee1e96ba966%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/jenkinsci-users/245d1ca6-c04a-469d-a3c3-5ee1e96ba966%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>>
>>>
>>> -- 
>>> Thanks!
>>> Mark Waite
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>

Re: Azure windows slave keeps disconnecting

When the master log says:


   1. Aug 05, 2019 8:54:51 AM hudson.remoting.jnlp.Main$CuiListener error
   2. SEVERE: The server rejected the connection: None of the protocols
   were accepted
   3. java.lang.Exception: The server rejected the connection: None of the
   protocols were accepted
   4. at hudson.remoting.Engine.onConnectionRejected(Engine.java:682)
   5. at hudson.remoting.Engine.innerRun(Engine.java:639)
   6. at hudson.remoting.Engine.run(Engine.java:474)


that might hint that either something is damaging the communication between
the agent or something is changing the configuration of the master to
reject agent protocols that were previously accepted.  The protocols which
are accepted can be modified from a "Configure Global Security" page of
"Manage Jenkins".  The "Agents" section of that page includes a link to
enable and disable specific protocols.

On Mon, Aug 5, 2019 at 6:29 AM Shubham Bansal  wrote:

> https://pastebin.com/ib0PK5af
>
> Can you tell me more from these logs of the slave windows machine?
>
>
> On Monday, 5 August 2019 17:42:23 UTC+5:30, Mark Waite wrote:
>>
>> Connecting the agent to the master *is* a robust way to connect.  Many
>> users around the world use that method to connect agents to masters,
>> including Windows masters, Linux masters, and other platforms.
>>
>> If the agent is being disconnected after some time, there may be
>> something on the agent computer which kills the client process that runs on
>> the agent (for example, some program that won't allow Java programs to run
>> for an extended period).  If the agent process dies or is killed on the
>> agent computer, the agent will be disconnected.  If you're running the
>> agent process from the command line, then you may find hints to the cause
>> of the command line failure in the command prompt window that launched the
>> agent.  If you're running the agent process by clicking the "Launch" button
>> to launch the agent from the browser, you may want to try running the agent
>> from the command line instead, just in case some diagnostic messages might
>> help you.
>>
>> There may be something in the networking definition between the master
>> and the agents which is causing the agent process to die.  Usually, when
>> the network connection is interrupted between a master and  agent launched
>> to connect to the master.  This seems less likely to be the problem, since
>> you mentioned that the when running as a restart, the service restarted
>> frequently.
>>
>> On Mon, Aug 5, 2019 at 5:46 AM Shubham Bansal  wrote:
>>
>>> I have a Linux Azure machine as master and it connects to the windows
>>> slave machine using the option "Launch Agent by connecting it to master"
>>>
>>> This connects the agent fine but gets disconnected after some time
>>> (around 20-30 minutes). I tried running the agent as windows service but
>>> the service keeps restarting frequently causing the build to fail of it is
>>> triggered at this time of restart process.
>>>
>>> Can someone here suggest a more robust way to connect?
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkins...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/245d1ca6-c04a-469d-a3c3-5ee1e96ba966%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/245d1ca6-c04a-469d-a3c3-5ee1e96ba966%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>
>>
>> --
>> Thanks!
>> Mark Waite
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/a1bcedbd-1fa4-4bf2-866e-7652d4d6c98e%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/a1bcedbd-1fa4-4bf2-866e-7652d4d6c98e%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
Thanks!
Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEKRT8eYNUkoRTmMf%2B4sjKtbyCuBHp6TkVm%2B06JJFjSaA%40mail.gmail.com.

Re: Azure windows slave keeps disconnecting

https://pastebin.com/ib0PK5af

Can you tell me more from these logs of the slave windows machine?


On Monday, 5 August 2019 17:42:23 UTC+5:30, Mark Waite wrote:
>
> Connecting the agent to the master *is* a robust way to connect.  Many 
> users around the world use that method to connect agents to masters, 
> including Windows masters, Linux masters, and other platforms.
>
> If the agent is being disconnected after some time, there may be something 
> on the agent computer which kills the client process that runs on the agent 
> (for example, some program that won't allow Java programs to run for an 
> extended period).  If the agent process dies or is killed on the agent 
> computer, the agent will be disconnected.  If you're running the agent 
> process from the command line, then you may find hints to the cause of the 
> command line failure in the command prompt window that launched the agent.  
> If you're running the agent process by clicking the "Launch" button to 
> launch the agent from the browser, you may want to try running the agent 
> from the command line instead, just in case some diagnostic messages might 
> help you.
>
> There may be something in the networking definition between the master and 
> the agents which is causing the agent process to die.  Usually, when the 
> network connection is interrupted between a master and  agent launched to 
> connect to the master.  This seems less likely to be the problem, since you 
> mentioned that the when running as a restart, the service restarted 
> frequently.
>
> On Mon, Aug 5, 2019 at 5:46 AM Shubham Bansal  > wrote:
>
>> I have a Linux Azure machine as master and it connects to the windows 
>> slave machine using the option "Launch Agent by connecting it to master"
>>
>> This connects the agent fine but gets disconnected after some time 
>> (around 20-30 minutes). I tried running the agent as windows service but 
>> the service keeps restarting frequently causing the build to fail of it is 
>> triggered at this time of restart process. 
>>
>> Can someone here suggest a more robust way to connect?
>>
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkins...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/245d1ca6-c04a-469d-a3c3-5ee1e96ba966%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/245d1ca6-c04a-469d-a3c3-5ee1e96ba966%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>
>
> -- 
> Thanks!
> Mark Waite
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a1bcedbd-1fa4-4bf2-866e-7652d4d6c98e%40googlegroups.com.

Re: Azure windows slave keeps disconnecting

Connecting the agent to the master *is* a robust way to connect.  Many
users around the world use that method to connect agents to masters,
including Windows masters, Linux masters, and other platforms.

If the agent is being disconnected after some time, there may be something
on the agent computer which kills the client process that runs on the agent
(for example, some program that won't allow Java programs to run for an
extended period).  If the agent process dies or is killed on the agent
computer, the agent will be disconnected.  If you're running the agent
process from the command line, then you may find hints to the cause of the
command line failure in the command prompt window that launched the agent.
If you're running the agent process by clicking the "Launch" button to
launch the agent from the browser, you may want to try running the agent
from the command line instead, just in case some diagnostic messages might
help you.

There may be something in the networking definition between the master and
the agents which is causing the agent process to die.  Usually, when the
network connection is interrupted between a master and  agent launched to
connect to the master.  This seems less likely to be the problem, since you
mentioned that the when running as a restart, the service restarted
frequently.

On Mon, Aug 5, 2019 at 5:46 AM Shubham Bansal  wrote:

> I have a Linux Azure machine as master and it connects to the windows
> slave machine using the option "Launch Agent by connecting it to master"
>
> This connects the agent fine but gets disconnected after some time (around
> 20-30 minutes). I tried running the agent as windows service but the
> service keeps restarting frequently causing the build to fail of it is
> triggered at this time of restart process.
>
> Can someone here suggest a more robust way to connect?
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/245d1ca6-c04a-469d-a3c3-5ee1e96ba966%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/245d1ca6-c04a-469d-a3c3-5ee1e96ba966%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
Thanks!
Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGOi2C1UjaNb-9w%2B7Tk4OCeNenTDSQjDcac-i8KuDRi%2Bg%40mail.gmail.com.

Jenkins agent keeps disconnecting on windows slave

I have a Jenkins master on Azure linux machine and have an Azure Windows VM 
as a slave. The slave connects using the option ""Launch agent by 
connecting it to the master". 
When the launch command is run on the Windows machine, the agent does 
connect but it disconnects after some time (around 20-30 minutes).  I tried 
running the agent as a windows service but the service keeps restarting 
very frequently and if the master makes any request to this slave during 
this restart time, the build fails. 

Can someone here give me a more robust solution to this issue?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/b1cbe7c0-c88e-42d5-95a4-da7a53761e03%40googlegroups.com.

Azure windows slave keeps disconnecting

I have a Linux Azure machine as master and it connects to the windows slave 
machine using the option "Launch Agent by connecting it to master"

This connects the agent fine but gets disconnected after some time (around 
20-30 minutes). I tried running the agent as windows service but the 
service keeps restarting frequently causing the build to fail of it is 
triggered at this time of restart process. 

Can someone here suggest a more robust way to connect?


-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/245d1ca6-c04a-469d-a3c3-5ee1e96ba966%40googlegroups.com.

Re: Unable to add a windows slave into Jenkins 2.177

2019-06-17 Thread Mark Waite

The "Unsupported major/minor version" message means that you are attempting
to run Java code that requires a Java 8 virtual machine on a Java version
that is less than Java 8.  It could be a configuration error in your PATH.
It could be an installation error on the computer.  It could be that the
default Java installed on the computer is older than Java 8.

Refer to
https://stackoverflow.com/questions/22489398/unsupported-major-minor-version-52-0

On Mon, Jun 17, 2019 at 5:41 AM ANKUSH CHANDEL 
wrote:

> Hello All,
>
> Please help me out with adding a Windows slave into Jenkins.
> I am using Launch Method as "Launch agent by connecting it to the master".
>
> Which provides me three options to connect the slave machine.
>
> Connect agent to Jenkins one of these ways:
>
>-
>
>[image: launch agent]
>
> <https://phlox-dv.itn.intraorange:4443/computer/WIN_10_Ankush/slave-agent.jnlp>
>  Launch
>agent from browser
>-
>
>Run from agent command line:
>
>javaws http://Location:Port/computer/WIN_10_X/slave-agent.jnlp
>
>-
>
>Or if the agent is headless:
>
>java -jar agent.jar 
> <https://phlox-dv.itn.intraorange:4443/jnlpJars/agent.jar> -jnlpUrl 
> http://Location:Port/computer/WIN_10_X/slave-agent.jnlp -workDir 
> "C:\Jenkins\
>
>
> I have tired these steps but it saying unable to launch the application.
>
> C:\Jenkins>java -jar agent.jar -jnlpUrl 
> http://Location:Port/computer/WIN_10_X/slave-agent.jnlp
> -workDir "C:\Jenkins"
> Exception in thread "main" java.lang.UnsupportedClassVersionError:
> hudson/remoting/Launcher : Unsupported major.minor version 52.0
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(Unknown Source)
> at java.security.SecureClassLoader.defineClass(Unknown Source)
> at java.net.URLClassLoader.defineClass(Unknown Source)
> at java.net.URLClassLoader.access$100(Unknown Source)
> at java.net.URLClassLoader$1.run(Unknown Source)
> at java.net.URLClassLoader$1.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(Unknown Source)
> at java.lang.ClassLoader.loadClass(Unknown Source)
> at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
> at java.lang.ClassLoader.loadClass(Unknown Source)
> at sun.launcher.LauncherHelper.checkAndLoadMain(Unknown Source)
>
> C:\Jenkins>javaws http://Location:Port
> /computer/WIN_10_X/slave-agent.jnlp
>
> C:\Jenkins>java -jar agent.jar -jnlpUrl 
> http://Location:Port/computer/WIN_10_X/slave-agent.jnlp
> -workDir "C:\Jenkins"
> Error: Registry key 'Software\JavaSoft\Java Runtime
> Environment'\CurrentVersion'
> has value '1.8', but '1.7' is required.
> Error: could not find java.dll
> Error: Could not find Java SE Runtime Environment.
>
>
> Please help me out with this.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/35fd8d79-455b-4f35-8f27-ee5135b71893%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/35fd8d79-455b-4f35-8f27-ee5135b71893%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEGKoKeed47FezwLQsTWaRqqUsR1PKDqfSVqsiVy8zTZA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Unable to add a windows slave into Jenkins 2.177

2019-06-17 Thread ANKUSH CHANDEL

Hello All,

Please help me out with adding a Windows slave into Jenkins.
I am using Launch Method as "Launch agent by connecting it to the master".

Which provides me three options to connect the slave machine.

Connect agent to Jenkins one of these ways:

   - 
   
   [image: launch agent] 
   
<https://phlox-dv.itn.intraorange:4443/computer/WIN_10_Ankush/slave-agent.jnlp> 
Launch 
   agent from browser
   - 
   
   Run from agent command line:
   
   javaws http://Location:Port/computer/WIN_10_X/slave-agent.jnlp
   
   - 
   
   Or if the agent is headless:
   
   java -jar agent.jar 
<https://phlox-dv.itn.intraorange:4443/jnlpJars/agent.jar> -jnlpUrl 
http://Location:Port/computer/WIN_10_X/slave-agent.jnlp -workDir 
"C:\Jenkins\
   
   
I have tired these steps but it saying unable to launch the application.

C:\Jenkins>java -jar agent.jar -jnlpUrl 
http://Location:Port/computer/WIN_10_X/slave-agent.jnlp -workDir 
"C:\Jenkins"
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
hudson/remoting/Launcher : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(Unknown Source)
at java.security.SecureClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.access$100(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.launcher.LauncherHelper.checkAndLoadMain(Unknown Source)

C:\Jenkins>javaws 
http://Location:Port/computer/WIN_10_X/slave-agent.jnlp

C:\Jenkins>java -jar agent.jar -jnlpUrl 
http://Location:Port/computer/WIN_10_X/slave-agent.jnlp -workDir 
"C:\Jenkins"
Error: Registry key 'Software\JavaSoft\Java Runtime 
Environment'\CurrentVersion'
has value '1.8', but '1.7' is required.
Error: could not find java.dll
Error: Could not find Java SE Runtime Environment.


Please help me out with this.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/35fd8d79-455b-4f35-8f27-ee5135b71893%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problem when trying to connect to GitHub from a Windows slave

2019-05-27 Thread Sébastien Hinderer

Hello David,

Many thanks for your response!

eyal david (2019/05/27 18:37 +0300):
> Hi
> Try to recreate new keys from the windows slave using the git bash ...

What do you mean by git bash ?

> than create credentails id in jenkins master based on the your private key
> created on the windows slave

And hten of course the public key needs to be added on GitHub. Well
since the manual clone worked I'm a bit reluctant to do all this, I have
to say.

Sébastien.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/20190527204254.GA2102%40prajna.paris.inria.fr.
For more options, visit https://groups.google.com/d/optout.

Re: Problem when trying to connect to GitHub from a Windows slave

2019-05-27 Thread Sébastien Hinderer

Hi,

Many thanks for your response.

Geoffroy J (2019/05/27 09:18 -0700):
> Hello
> 
> Have you tried cloning manually using the ssh key on windows?

Yes, and it worked.
Sorry I forgot to mention this.

> Also, what username have you configured for your git credential on
> Jenkins?

The GitHub user name. But the 'git@' part in the URL of the repository.
Additionnally, as I mentionned, this setting works perfectly well for
the Unix machines.

> I faced ssh issues on windows because of change in SSH/GIT and it was 
> necessary to set credential username to 'git' instead of the real github 
> username. See https://issues.jenkins-ci.org/browse/JENKINS-50573

Thanks! Actually, my GitHub plugin is up-to-date so I'd expect this to
be fixed, right?

Also my error message is different from the one reported in the bug,
mine explicitly mentions an "invalid format" in the keyfile.

But many thanks for helping out, I really appreciate and hope we willl
find the problem!

Sébastien.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/20190527203246.GB1939%40prajna.paris.inria.fr.
For more options, visit https://groups.google.com/d/optout.

Re: Problem when trying to connect to GitHub from a Windows slave

2019-05-27 Thread Geoffroy J

Hello

Have you tried cloning manually using the ssh key on windows?

Also, what username have you configured for your git credential on Jenkins?
I faced ssh issues on windows because of change in SSH/GIT and it was 
necessary to set credential username to 'git' instead of the real github 
username. See https://issues.jenkins-ci.org/browse/JENKINS-50573

BR

On Monday, 27 May 2019 16:50:59 UTC+2, Sébastien Hinderer wrote:
>
> Dear all, 
>
> Recently, I wanted my slaves to fetch our GitHub repository through 
> authenticated ssh coneections rather than through HTTPS unauthenticated 
> connections. 
>
> I created the appropriate Jenkins credential with ssh keys, replaced the 
> HTTPS URL of the repo by an ssh-based one and requested the use of the 
> newly created credential. 
>
> On our Unix machines everything works like a charm. 
>
> On our Windows machines, though, I get an "invalid format" message while 
> trying to read a .key file. 
>
> In case it's useful, our Windows hosts are running git 2.17.0 and 
> OpenSSH 7.8p1. 
>
> Many thanks in advance for any hint! 
>
> Sébastien. 
>

>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ddb9de8e-9a6d-4c3a-892d-4a08c9501322%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Problem when trying to connect to GitHub from a Windows slave

2019-05-27 Thread Sébastien Hinderer

Dear all,

Recently, I wanted my slaves to fetch our GitHub repository through
authenticated ssh coneections rather than through HTTPS unauthenticated
connections.

I created the appropriate Jenkins credential with ssh keys, replaced the
HTTPS URL of the repo by an ssh-based one and requested the use of the
newly created credential.

On our Unix machines everything works like a charm.

On our Windows machines, though, I get an "invalid format" message while
trying to read a .key file.

In case it's useful, our Windows hosts are running git 2.17.0 and
OpenSSH 7.8p1.

Many thanks in advance for any hint!

Sébastien.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/20190527135323.GA32420%40prajna.paris.inria.fr.
For more options, visit https://groups.google.com/d/optout.

Re: SSH vs java web start for windows slave and Linux master in jenkins

2019-05-02 Thread rausalinas

ssh lets you only use resources while you need that node.  (unless you 
chose "Use this node as much as possible")

If I remember correctly, an agent can use around 80 MB of RAM. If your 
machine is quite resource-constrained, such as a Raspberry Pi that you use 
only sometimes for building for that platform, you may well want to save 
resources in case you use that machine for other purposes.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0c941b23-b884-4a72-9900-b4cb4ffb2116%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Windows Slave GIT_SSH Invalid format

2019-04-10 Thread Venkatapathi Jaligama

created ssh keys using ssh-keygen from git bash on windows, it works, Thank
you very much Mark

Regards,
Venkat

On Wed, Apr 10, 2019 at 1:54 PM Mark Waite 
wrote:

> I'd create the keys on Windows using the ssh-keygen command on Windows.
> OpenSSH on Windows will be consuming the keys.
>
> On Wed, Apr 10, 2019 at 11:43 AM Venkatapathi Jaligama <
> jvenkat...@gmail.com> wrote:
>
>> Hello Mark,
>>
>> First time i created key on linux, second-time I created on windows slave
>> from putty gen and convert to openssh format and then use the keys, even
>> these keys work for linux slaves but not for windows slave, gives invalid
>> format
>>
>> On Wed, Apr 10, 2019 at 1:38 PM Mark Waite 
>> wrote:
>>
>>> I've seen problems in the past where I needed to generate the private
>>> key / public key pair on the machine that would be using the key.  When you
>>> created the private key, did you run ssh-keygen on the Windows computer
>>> that is using the key?  If not, you might try that.
>>>
>>> On Wed, Apr 10, 2019 at 11:23 AM Venkatapathi Jaligama <
>>> jvenkat...@gmail.com> wrote:
>>>
>>>> Hello Mark,
>>>> Thank you for you prompt response, I have already tested this scenario
>>>> also removed all the jeys from windows slave and only use the jenkins
>>>> credentials still does not work, I generated new keys and added the private
>>>> key in the jenkins credentials and public key in Gitlab still same issue.
>>>> Could you think of anything else.
>>>>
>>>> Thanks,
>>>> Venkat
>>>>
>>>> On Wed, Apr 10, 2019 at 11:43 AM Mark Waite 
>>>> wrote:
>>>>
>>>>> Compare the contents of the private key definition in the Jenkins
>>>>> credentials UI with the private key that is being used on the Windows
>>>>> agent.  If the key is incorrectly defined in the Jenkins credentials, that
>>>>> might cause the problem you're seeing.
>>>>>
>>>>> Move (or hide) all other private keys on the Windows agent to be sure
>>>>> that your successful interactive test was not using a different private 
>>>>> key
>>>>> than the private key used in the Jenkins credential.
>>>>>
>>>>> On Wed, Apr 10, 2019 at 3:47 AM  wrote:
>>>>>
>>>>>> Hello Users,
>>>>>>
>>>>>> I have Jenkins with master slave configuration, I have linux slaves
>>>>>> and windows slaves
>>>>>> I am unable to use the Gitlab  SSH credentials on Windows Slave
>>>>>> Fails on scm checkout, The scm checkout works fine for the linux
>>>>>> slaves
>>>>>> To test the id_rsa key, I put the id_rsa in .ssh of home directory
>>>>>> and do git clone, it works fine, but somehow from git credentials it seem
>>>>>> to have a problem
>>>>>> Is there a workaround for this issue any help is very much appreciated
>>>>>>
>>>>>> using credential 2090ffbd-ddc3-45a9-adfb-e9c0e5ca4c75
>>>>>> Wiping out workspace first.
>>>>>> Cloning the remote Git repository
>>>>>> Cloning repository ssh://g...@gitlab-.com/xx.git
>>>>>>  > git init 
>>>>>> E:\workspace\Main_Build_master-HAJ7MPMVYIUEWROZ6RHLXJYVT3JUCE7ZDT7PHAOWUKJQYMDSW5KQ
>>>>>>  # timeout=10
>>>>>> Fetching upstream changes from ssh://g...@gitlab-.com/xx.git
>>>>>>  > git --version # timeout=10
>>>>>> using GIT_SSH to set credentials Jenkins private ssh key
>>>>>>  > git fetch --tags --progress ssh://g...@gitlab-.com/xx.git 
>>>>>> +refs/heads/*:refs/remotes/origin/* # timeout=7
>>>>>> ERROR: Error cloning remote repo 'origin'
>>>>>> hudson.plugins.git.GitException: Command "git fetch --tags --progress 
>>>>>> ssh://g...@gitlab-.com/xx.git +refs/heads/*:refs/remotes/origin/*" 
>>>>>> returned status code 128:
>>>>>> stdout:
>>>>>> stderr: Load key 
>>>>>> "E:\\workspace\\Main_Build_master-HAJ7MPMVYIUEWROZ6RHLXJYVT3JUCE7ZDT7PHAOWUKJQYMDSW5KQ@tmp\\ssh8872120221702825356.key":
>>>>>>  invalid format
>>>>>> Permission denied, please try again.
>>>>>> Permission denied, please try again@gitlab-.com/xx.gi

Re: Jenkins Windows Slave GIT_SSH Invalid format

2019-04-10 Thread Mark Waite

I'd create the keys on Windows using the ssh-keygen command on Windows.
OpenSSH on Windows will be consuming the keys.

On Wed, Apr 10, 2019 at 11:43 AM Venkatapathi Jaligama 
wrote:

> Hello Mark,
>
> First time i created key on linux, second-time I created on windows slave
> from putty gen and convert to openssh format and then use the keys, even
> these keys work for linux slaves but not for windows slave, gives invalid
> format
>
> On Wed, Apr 10, 2019 at 1:38 PM Mark Waite 
> wrote:
>
>> I've seen problems in the past where I needed to generate the private key
>> / public key pair on the machine that would be using the key.  When you
>> created the private key, did you run ssh-keygen on the Windows computer
>> that is using the key?  If not, you might try that.
>>
>> On Wed, Apr 10, 2019 at 11:23 AM Venkatapathi Jaligama <
>> jvenkat...@gmail.com> wrote:
>>
>>> Hello Mark,
>>> Thank you for you prompt response, I have already tested this scenario
>>> also removed all the jeys from windows slave and only use the jenkins
>>> credentials still does not work, I generated new keys and added the private
>>> key in the jenkins credentials and public key in Gitlab still same issue.
>>> Could you think of anything else.
>>>
>>> Thanks,
>>> Venkat
>>>
>>> On Wed, Apr 10, 2019 at 11:43 AM Mark Waite 
>>> wrote:
>>>
>>>> Compare the contents of the private key definition in the Jenkins
>>>> credentials UI with the private key that is being used on the Windows
>>>> agent.  If the key is incorrectly defined in the Jenkins credentials, that
>>>> might cause the problem you're seeing.
>>>>
>>>> Move (or hide) all other private keys on the Windows agent to be sure
>>>> that your successful interactive test was not using a different private key
>>>> than the private key used in the Jenkins credential.
>>>>
>>>> On Wed, Apr 10, 2019 at 3:47 AM  wrote:
>>>>
>>>>> Hello Users,
>>>>>
>>>>> I have Jenkins with master slave configuration, I have linux slaves
>>>>> and windows slaves
>>>>> I am unable to use the Gitlab  SSH credentials on Windows Slave
>>>>> Fails on scm checkout, The scm checkout works fine for the linux
>>>>> slaves
>>>>> To test the id_rsa key, I put the id_rsa in .ssh of home directory
>>>>> and do git clone, it works fine, but somehow from git credentials it seem
>>>>> to have a problem
>>>>> Is there a workaround for this issue any help is very much appreciated
>>>>>
>>>>> using credential 2090ffbd-ddc3-45a9-adfb-e9c0e5ca4c75
>>>>> Wiping out workspace first.
>>>>> Cloning the remote Git repository
>>>>> Cloning repository ssh://g...@gitlab-.com/xx.git
>>>>>  > git init 
>>>>> E:\workspace\Main_Build_master-HAJ7MPMVYIUEWROZ6RHLXJYVT3JUCE7ZDT7PHAOWUKJQYMDSW5KQ
>>>>>  # timeout=10
>>>>> Fetching upstream changes from ssh://g...@gitlab-.com/xx.git
>>>>>  > git --version # timeout=10
>>>>> using GIT_SSH to set credentials Jenkins private ssh key
>>>>>  > git fetch --tags --progress ssh://g...@gitlab-.com/xx.git 
>>>>> +refs/heads/*:refs/remotes/origin/* # timeout=7
>>>>> ERROR: Error cloning remote repo 'origin'
>>>>> hudson.plugins.git.GitException: Command "git fetch --tags --progress 
>>>>> ssh://g...@gitlab-.com/xx.git +refs/heads/*:refs/remotes/origin/*" 
>>>>> returned status code 128:
>>>>> stdout:
>>>>> stderr: Load key 
>>>>> "E:\\workspace\\Main_Build_master-HAJ7MPMVYIUEWROZ6RHLXJYVT3JUCE7ZDT7PHAOWUKJQYMDSW5KQ@tmp\\ssh8872120221702825356.key":
>>>>>  invalid format
>>>>> Permission denied, please try again.
>>>>> Permission denied, please try again@gitlab-.com/xx.git: 
>>>>> Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).
>>>>> fatal: Could not read from remote repository.
>>>>>
>>>>> Please make sure you have the correct access rights
>>>>> and the repository exists.
>>>>>
>>>>>   at 
>>>>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2002)
>>>>>   at 
>>>>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launch

Re: Jenkins Windows Slave GIT_SSH Invalid format

2019-04-10 Thread Venkatapathi Jaligama

Hello Mark,

First time i created key on linux, second-time I created on windows slave
from putty gen and convert to openssh format and then use the keys, even
these keys work for linux slaves but not for windows slave, gives invalid
format

On Wed, Apr 10, 2019 at 1:38 PM Mark Waite 
wrote:

> I've seen problems in the past where I needed to generate the private key
> / public key pair on the machine that would be using the key.  When you
> created the private key, did you run ssh-keygen on the Windows computer
> that is using the key?  If not, you might try that.
>
> On Wed, Apr 10, 2019 at 11:23 AM Venkatapathi Jaligama <
> jvenkat...@gmail.com> wrote:
>
>> Hello Mark,
>> Thank you for you prompt response, I have already tested this scenario
>> also removed all the jeys from windows slave and only use the jenkins
>> credentials still does not work, I generated new keys and added the private
>> key in the jenkins credentials and public key in Gitlab still same issue.
>> Could you think of anything else.
>>
>> Thanks,
>> Venkat
>>
>> On Wed, Apr 10, 2019 at 11:43 AM Mark Waite 
>> wrote:
>>
>>> Compare the contents of the private key definition in the Jenkins
>>> credentials UI with the private key that is being used on the Windows
>>> agent.  If the key is incorrectly defined in the Jenkins credentials, that
>>> might cause the problem you're seeing.
>>>
>>> Move (or hide) all other private keys on the Windows agent to be sure
>>> that your successful interactive test was not using a different private key
>>> than the private key used in the Jenkins credential.
>>>
>>> On Wed, Apr 10, 2019 at 3:47 AM  wrote:
>>>
>>>> Hello Users,
>>>>
>>>> I have Jenkins with master slave configuration, I have linux slaves and
>>>> windows slaves
>>>> I am unable to use the Gitlab  SSH credentials on Windows Slave
>>>> Fails on scm checkout, The scm checkout works fine for the linux slaves
>>>> To test the id_rsa key, I put the id_rsa in .ssh of home directory  and
>>>> do git clone, it works fine, but somehow from git credentials it seem to
>>>> have a problem
>>>> Is there a workaround for this issue any help is very much appreciated
>>>>
>>>> using credential 2090ffbd-ddc3-45a9-adfb-e9c0e5ca4c75
>>>> Wiping out workspace first.
>>>> Cloning the remote Git repository
>>>> Cloning repository ssh://g...@gitlab-.com/xx.git
>>>>  > git init 
>>>> E:\workspace\Main_Build_master-HAJ7MPMVYIUEWROZ6RHLXJYVT3JUCE7ZDT7PHAOWUKJQYMDSW5KQ
>>>>  # timeout=10
>>>> Fetching upstream changes from ssh://g...@gitlab-.com/xx.git
>>>>  > git --version # timeout=10
>>>> using GIT_SSH to set credentials Jenkins private ssh key
>>>>  > git fetch --tags --progress ssh://g...@gitlab-.com/xx.git 
>>>> +refs/heads/*:refs/remotes/origin/* # timeout=7
>>>> ERROR: Error cloning remote repo 'origin'
>>>> hudson.plugins.git.GitException: Command "git fetch --tags --progress 
>>>> ssh://g...@gitlab-.com/xx.git +refs/heads/*:refs/remotes/origin/*" 
>>>> returned status code 128:
>>>> stdout:
>>>> stderr: Load key 
>>>> "E:\\workspace\\Main_Build_master-HAJ7MPMVYIUEWROZ6RHLXJYVT3JUCE7ZDT7PHAOWUKJQYMDSW5KQ@tmp\\ssh8872120221702825356.key":
>>>>  invalid format
>>>> Permission denied, please try again.
>>>> Permission denied, please try again@gitlab-.com/xx.git: Permission 
>>>> denied (publickey,gssapi-keyex,gssapi-with-mic,password).
>>>> fatal: Could not read from remote repository.
>>>>
>>>> Please make sure you have the correct access rights
>>>> and the repository exists.
>>>>
>>>>at 
>>>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2002)
>>>>at 
>>>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1721)
>>>>at 
>>>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:72)
>>>>at 
>>>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:405)
>>>>at 
>>>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:614)
>>>>at 
>>>> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)

Re: Jenkins Windows Slave GIT_SSH Invalid format

2019-04-10 Thread Mark Waite

I've seen problems in the past where I needed to generate the private key /
public key pair on the machine that would be using the key.  When you
created the private key, did you run ssh-keygen on the Windows computer
that is using the key?  If not, you might try that.

On Wed, Apr 10, 2019 at 11:23 AM Venkatapathi Jaligama 
wrote:

> Hello Mark,
> Thank you for you prompt response, I have already tested this scenario
> also removed all the jeys from windows slave and only use the jenkins
> credentials still does not work, I generated new keys and added the private
> key in the jenkins credentials and public key in Gitlab still same issue.
> Could you think of anything else.
>
> Thanks,
> Venkat
>
> On Wed, Apr 10, 2019 at 11:43 AM Mark Waite 
> wrote:
>
>> Compare the contents of the private key definition in the Jenkins
>> credentials UI with the private key that is being used on the Windows
>> agent.  If the key is incorrectly defined in the Jenkins credentials, that
>> might cause the problem you're seeing.
>>
>> Move (or hide) all other private keys on the Windows agent to be sure
>> that your successful interactive test was not using a different private key
>> than the private key used in the Jenkins credential.
>>
>> On Wed, Apr 10, 2019 at 3:47 AM  wrote:
>>
>>> Hello Users,
>>>
>>> I have Jenkins with master slave configuration, I have linux slaves and
>>> windows slaves
>>> I am unable to use the Gitlab  SSH credentials on Windows Slave
>>> Fails on scm checkout, The scm checkout works fine for the linux slaves
>>> To test the id_rsa key, I put the id_rsa in .ssh of home directory  and
>>> do git clone, it works fine, but somehow from git credentials it seem to
>>> have a problem
>>> Is there a workaround for this issue any help is very much appreciated
>>>
>>> using credential 2090ffbd-ddc3-45a9-adfb-e9c0e5ca4c75
>>> Wiping out workspace first.
>>> Cloning the remote Git repository
>>> Cloning repository ssh://g...@gitlab-.com/xx.git
>>>  > git init 
>>> E:\workspace\Main_Build_master-HAJ7MPMVYIUEWROZ6RHLXJYVT3JUCE7ZDT7PHAOWUKJQYMDSW5KQ
>>>  # timeout=10
>>> Fetching upstream changes from ssh://g...@gitlab-.com/xx.git
>>>  > git --version # timeout=10
>>> using GIT_SSH to set credentials Jenkins private ssh key
>>>  > git fetch --tags --progress ssh://g...@gitlab-.com/xx.git 
>>> +refs/heads/*:refs/remotes/origin/* # timeout=7
>>> ERROR: Error cloning remote repo 'origin'
>>> hudson.plugins.git.GitException: Command "git fetch --tags --progress 
>>> ssh://g...@gitlab-.com/xx.git +refs/heads/*:refs/remotes/origin/*" 
>>> returned status code 128:
>>> stdout:
>>> stderr: Load key 
>>> "E:\\workspace\\Main_Build_master-HAJ7MPMVYIUEWROZ6RHLXJYVT3JUCE7ZDT7PHAOWUKJQYMDSW5KQ@tmp\\ssh8872120221702825356.key":
>>>  invalid format
>>> Permission denied, please try again.
>>> Permission denied, please try again@gitlab-.com/xx.git: Permission 
>>> denied (publickey,gssapi-keyex,gssapi-with-mic,password).
>>> fatal: Could not read from remote repository.
>>>
>>> Please make sure you have the correct access rights
>>> and the repository exists.
>>>
>>> at 
>>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2002)
>>> at 
>>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1721)
>>> at 
>>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:72)
>>> at 
>>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:405)
>>> at 
>>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:614)
>>> at 
>>> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
>>> at 
>>> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
>>> at hudson.remoting.UserRequest.perform(UserRequest.java:212)
>>> at hudson.remoting.UserRequest.perform(UserRequest.java:54)
>>> at hudson.remoting.Request$2.run(Request.java:369)
>>> at 
>>> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
>>> at java.util.concurrent.FutureTask.run(Unknown Source)
>>> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Sour

Re: Jenkins Windows Slave GIT_SSH Invalid format

2019-04-10 Thread Venkatapathi Jaligama

Hello Mark,
Thank you for you prompt response, I have already tested this scenario also
removed all the jeys from windows slave and only use the jenkins
credentials still does not work, I generated new keys and added the private
key in the jenkins credentials and public key in Gitlab still same issue.
Could you think of anything else.

Thanks,
Venkat

On Wed, Apr 10, 2019 at 11:43 AM Mark Waite 
wrote:

> Compare the contents of the private key definition in the Jenkins
> credentials UI with the private key that is being used on the Windows
> agent.  If the key is incorrectly defined in the Jenkins credentials, that
> might cause the problem you're seeing.
>
> Move (or hide) all other private keys on the Windows agent to be sure that
> your successful interactive test was not using a different private key than
> the private key used in the Jenkins credential.
>
> On Wed, Apr 10, 2019 at 3:47 AM  wrote:
>
>> Hello Users,
>>
>> I have Jenkins with master slave configuration, I have linux slaves and
>> windows slaves
>> I am unable to use the Gitlab  SSH credentials on Windows Slave
>> Fails on scm checkout, The scm checkout works fine for the linux slaves
>> To test the id_rsa key, I put the id_rsa in .ssh of home directory  and
>> do git clone, it works fine, but somehow from git credentials it seem to
>> have a problem
>> Is there a workaround for this issue any help is very much appreciated
>>
>> using credential 2090ffbd-ddc3-45a9-adfb-e9c0e5ca4c75
>> Wiping out workspace first.
>> Cloning the remote Git repository
>> Cloning repository ssh://g...@gitlab-.com/xx.git
>>  > git init 
>> E:\workspace\Main_Build_master-HAJ7MPMVYIUEWROZ6RHLXJYVT3JUCE7ZDT7PHAOWUKJQYMDSW5KQ
>>  # timeout=10
>> Fetching upstream changes from ssh://g...@gitlab-.com/xx.git
>>  > git --version # timeout=10
>> using GIT_SSH to set credentials Jenkins private ssh key
>>  > git fetch --tags --progress ssh://g...@gitlab-.com/xx.git 
>> +refs/heads/*:refs/remotes/origin/* # timeout=7
>> ERROR: Error cloning remote repo 'origin'
>> hudson.plugins.git.GitException: Command "git fetch --tags --progress 
>> ssh://g...@gitlab-.com/xx.git +refs/heads/*:refs/remotes/origin/*" 
>> returned status code 128:
>> stdout:
>> stderr: Load key 
>> "E:\\workspace\\Main_Build_master-HAJ7MPMVYIUEWROZ6RHLXJYVT3JUCE7ZDT7PHAOWUKJQYMDSW5KQ@tmp\\ssh8872120221702825356.key":
>>  invalid format
>> Permission denied, please try again.
>> Permission denied, please try again@gitlab-.com/xx.git: Permission 
>> denied (publickey,gssapi-keyex,gssapi-with-mic,password).
>> fatal: Could not read from remote repository.
>>
>> Please make sure you have the correct access rights
>> and the repository exists.
>>
>>  at 
>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2002)
>>  at 
>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1721)
>>  at 
>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:72)
>>  at 
>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:405)
>>  at 
>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:614)
>>  at 
>> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
>>  at 
>> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
>>  at hudson.remoting.UserRequest.perform(UserRequest.java:212)
>>  at hudson.remoting.UserRequest.perform(UserRequest.java:54)
>>  at hudson.remoting.Request$2.run(Request.java:369)
>>  at 
>> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
>>  at java.util.concurrent.FutureTask.run(Unknown Source)
>>  at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>>  at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>>  at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93)
>>  at java.lang.Thread.run(Unknown Source)
>>  Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to 
>> JNLP4-connect connection from 10.171.1.123/10.171.1.123:1035
>>  at 
>> hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)
>>  at 
>> hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)
>>  at hudson.remoting.Channel.call(Channel.java:955)
>>  at

Re: Jenkins Windows Slave GIT_SSH Invalid format

2019-04-10 Thread Mark Waite

Compare the contents of the private key definition in the Jenkins
credentials UI with the private key that is being used on the Windows
agent.  If the key is incorrectly defined in the Jenkins credentials, that
might cause the problem you're seeing.

Move (or hide) all other private keys on the Windows agent to be sure that
your successful interactive test was not using a different private key than
the private key used in the Jenkins credential.

On Wed, Apr 10, 2019 at 3:47 AM  wrote:

> Hello Users,
>
> I have Jenkins with master slave configuration, I have linux slaves and
> windows slaves
> I am unable to use the Gitlab  SSH credentials on Windows Slave
> Fails on scm checkout, The scm checkout works fine for the linux slaves
> To test the id_rsa key, I put the id_rsa in .ssh of home directory  and do
> git clone, it works fine, but somehow from git credentials it seem to have
> a problem
> Is there a workaround for this issue any help is very much appreciated
>
> using credential 2090ffbd-ddc3-45a9-adfb-e9c0e5ca4c75
> Wiping out workspace first.
> Cloning the remote Git repository
> Cloning repository ssh://g...@gitlab-.com/xx.git
>  > git init 
> E:\workspace\Main_Build_master-HAJ7MPMVYIUEWROZ6RHLXJYVT3JUCE7ZDT7PHAOWUKJQYMDSW5KQ
>  # timeout=10
> Fetching upstream changes from ssh://g...@gitlab-.com/xx.git
>  > git --version # timeout=10
> using GIT_SSH to set credentials Jenkins private ssh key
>  > git fetch --tags --progress ssh://g...@gitlab-.com/xx.git 
> +refs/heads/*:refs/remotes/origin/* # timeout=7
> ERROR: Error cloning remote repo 'origin'
> hudson.plugins.git.GitException: Command "git fetch --tags --progress 
> ssh://g...@gitlab-.com/xx.git +refs/heads/*:refs/remotes/origin/*" 
> returned status code 128:
> stdout:
> stderr: Load key 
> "E:\\workspace\\Main_Build_master-HAJ7MPMVYIUEWROZ6RHLXJYVT3JUCE7ZDT7PHAOWUKJQYMDSW5KQ@tmp\\ssh8872120221702825356.key":
>  invalid format
> Permission denied, please try again.
> Permission denied, please try again@gitlab-.com/xx.git: Permission 
> denied (publickey,gssapi-keyex,gssapi-with-mic,password).
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
>
>   at 
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2002)
>   at 
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1721)
>   at 
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:72)
>   at 
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:405)
>   at 
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:614)
>   at 
> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
>   at 
> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
>   at hudson.remoting.UserRequest.perform(UserRequest.java:212)
>   at hudson.remoting.UserRequest.perform(UserRequest.java:54)
>   at hudson.remoting.Request$2.run(Request.java:369)
>   at 
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
>   at java.util.concurrent.FutureTask.run(Unknown Source)
>   at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>   at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93)
>   at java.lang.Thread.run(Unknown Source)
>   Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to 
> JNLP4-connect connection from 10.171.1.123/10.171.1.123:1035
>   at 
> hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)
>   at 
> hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)
>   at hudson.remoting.Channel.call(Channel.java:955)
>   at 
> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146)
>   at sun.reflect.GeneratedMethodAccessor280.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132)
>   at com.sun.proxy.$Proxy94.execute(Unknown Source)
>   at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1152)
>

Jenkins Windows Slave GIT_SSH Invalid format

2019-04-10 Thread jvenkat099

Hello Users,

I have Jenkins with master slave configuration, I have linux slaves and 
windows slaves
I am unable to use the Gitlab  SSH credentials on Windows Slave
Fails on scm checkout, The scm checkout works fine for the linux slaves 
To test the id_rsa key, I put the id_rsa in .ssh of home directory  and do 
git clone, it works fine, but somehow from git credentials it seem to have 
a problem
Is there a workaround for this issue any help is very much appreciated

using credential 2090ffbd-ddc3-45a9-adfb-e9c0e5ca4c75
Wiping out workspace first.
Cloning the remote Git repository
Cloning repository ssh://g...@gitlab-.com/xx.git
 > git init 
 > E:\workspace\Main_Build_master-HAJ7MPMVYIUEWROZ6RHLXJYVT3JUCE7ZDT7PHAOWUKJQYMDSW5KQ
 >  # timeout=10
Fetching upstream changes from ssh://g...@gitlab-.com/xx.git
 > git --version # timeout=10
using GIT_SSH to set credentials Jenkins private ssh key
 > git fetch --tags --progress ssh://g...@gitlab-.com/xx.git 
 > +refs/heads/*:refs/remotes/origin/* # timeout=7
ERROR: Error cloning remote repo 'origin'
hudson.plugins.git.GitException: Command "git fetch --tags --progress 
ssh://g...@gitlab-.com/xx.git +refs/heads/*:refs/remotes/origin/*" returned 
status code 128:
stdout: 
stderr: Load key 
"E:\\workspace\\Main_Build_master-HAJ7MPMVYIUEWROZ6RHLXJYVT3JUCE7ZDT7PHAOWUKJQYMDSW5KQ@tmp\\ssh8872120221702825356.key":
 invalid format
Permission denied, please try again.
Permission denied, please try again.
g...@gitlab-.com/xx.git: Permission denied 
(publickey,gssapi-keyex,gssapi-with-mic,password).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2002)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1721)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:72)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:405)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:614)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
at hudson.remoting.UserRequest.perform(UserRequest.java:212)
at hudson.remoting.UserRequest.perform(UserRequest.java:54)
at hudson.remoting.Request$2.run(Request.java:369)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93)
at java.lang.Thread.run(Unknown Source)
Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to 
JNLP4-connect connection from 10.171.1.123/10.171.1.123:1035
at 
hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)
at 
hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)
at hudson.remoting.Channel.call(Channel.java:955)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146)
at sun.reflect.GeneratedMethodAccessor280.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132)
at com.sun.proxy.$Proxy94.execute(Unknown Source)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1152)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1192)
at 
org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:113)
at 
org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:85)
at 
org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:75)
at 
org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47)
at hudson.security.ACL.impersonate(ACL.java:290)
at 
org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)
at 
java.util.concurrent.Executors$R

Re: Increase Java heap size of Windows Slave

2018-11-27 Thread gotviseryon

Yes Jeff.  That's where I configured. 
JVM Options - "-Xmx3072m"



On Tuesday, November 27, 2018 at 1:07:10 PM UTC-5, Jeff Thompson wrote:
>
> I suggest you try configuring it at the configuration page for the node in 
> Jenkins. Look under the Advanced button for JVM options.
>
> Jeff Thompson 
>
> On Nov 27, 2018, at 7:32 AM, gotvi...@gmail.com  wrote:
>
> We have a Windows 2016 Slave.  The slave gets disconnected due to heap 
> memory maxing out.  How to increase the heap size to tackle this issue?  
> This is a bit urgent please.
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-use...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/c1393ce1-03c2-43f4-b7df-58a14bb80ebc%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/9dad0670-29bd-4597-b40c-578cb1a0ef97%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Increase Java heap size of Windows Slave

2018-11-27 Thread Jeff Thompson

I suggest you try configuring it at the configuration page for the node in 
Jenkins. Look under the Advanced button for JVM options.

Jeff Thompson

> On Nov 27, 2018, at 7:32 AM, gotviser...@gmail.com wrote:
> 
> We have a Windows 2016 Slave.  The slave gets disconnected due to heap memory 
> maxing out.  How to increase the heap size to tackle this issue?  This is a 
> bit urgent please.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-users+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/c1393ce1-03c2-43f4-b7df-58a14bb80ebc%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/978DF48F-1E34-49DA-8908-FF099846D9BA%40cloudbees.com.
For more options, visit https://groups.google.com/d/optout.

Re: Increase Java heap size of Windows Slave

2018-11-27 Thread gotviseryon

Thanks a lot Victor.  This helps.

On Tuesday, November 27, 2018 at 12:51:31 PM UTC-5, Victor Martinez wrote:
>
> It does depend on how that particular windows agent is launched. The below 
> references can help you:
> - https://issues.jenkins-ci.org/browse/JENKINS-3554
> - 
> https://support.cloudbees.com/hc/en-us/articles/204264000-Why-do-I-receive-java-lang-OutOfMemoryError-PermGen-space
>  
> might also help
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/b2bc2d80-d853-4420-97ad-717d35d6ea45%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Increase Java heap size of Windows Slave

2018-11-27 Thread Victor Martinez

It does depend on how that particular windows agent is launched. The below 
references can help you:
- https://issues.jenkins-ci.org/browse/JENKINS-3554
- 
https://support.cloudbees.com/hc/en-us/articles/204264000-Why-do-I-receive-java-lang-OutOfMemoryError-PermGen-space
 
might also help

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/839b8567-041d-470e-afeb-14ac87c3043d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Increase Java heap size of Windows Slave

2018-11-27 Thread gotviseryon

We have a Windows 2016 Slave.  The slave gets disconnected due to heap 
memory maxing out.  How to increase the heap size to tackle this issue?  
This is a bit urgent please.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/c1393ce1-03c2-43f4-b7df-58a14bb80ebc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins service going down on Windows Slave

Just found it.  In the Slave configuration section, below "Launch method" 
in "Advanced" there is a section called "JVM options".  We can pass it as a 
parameter here.  Need to test it and see if it works.

On Monday, November 26, 2018 at 4:33:11 PM UTC-5, slide wrote:
>
> There should be a way to pass parameters to the JVM in the .xml file 
> (slave.xml or something similar).
>
> On Mon, Nov 26, 2018 at 1:38 PM > wrote:
>
>> Found a log file on the slave machine.  It's Java heap size error.
>>
>> INFO: HttpClient configured for $URL, authenticating as USER
>> Nov 20, 2018 6:25:09 PM 
>> com.microsoft.tfs.core.ws.runtime.transport.IdleHTTPConnectionCloser run
>> SEVERE: unexpected error
>> java.lang.OutOfMemoryError: Java heap space
>> at java.util.Arrays.copyOf(Unknown Source)
>> at java.util.Arrays.copyOf(Unknown Source)
>> at java.util.ArrayList.grow(Unknown Source)
>> at java.util.ArrayList.ensureExplicitCapacity(Unknown Source)
>> at java.util.ArrayList.ensureCapacityInternal(Unknown Source)
>> at java.util.ArrayList.add(Unknown Source)
>> at 
>> com.microsoft.tfs.core.ws.runtime.transport.IdleHTTPConnectionCloser.run(IdleHTTPConnectionCloser.java:109)
>>
>> Nov 20, 2018 6:25:12 PM 
>> org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader run
>> SEVERE: [JNLP4-connect connection to JENKINS_URL/IP:35351] Reader thread 
>> killed by OutOfMemoryError
>> java.lang.OutOfMemoryError: Java heap space
>>
>> Exception in thread "pool-1-thread-3" java.lang.OutOfMemoryError: Java 
>> heap space
>> Nov 20, 2018 6:29:32 PM hudson.slaves.ChannelPinger$1 onDead
>> INFO: Ping failed. Terminating the channel JNLP4-connect connection to 
>> JENKINS_URL/IP:35351.
>> java.util.concurrent.TimeoutException: Ping started at 1542756332316 
>> hasn't completed by 1542756572331
>> at hudson.remoting.PingThread.ping(PingThread.java:134)
>> at hudson.remoting.PingThread.run(PingThread.java:90)
>>
>> Nov 20, 2018 6:34:32 PM hudson.slaves.ChannelPinger$1 onDead
>> INFO: Ping failed. Terminating the channel JNLP4-connect connection to 
>> JENKINS_URL/IP:35351.
>> java.util.concurrent.TimeoutException: Ping started at 1542756632868 
>> hasn't completed by 1542756872880
>> at hudson.remoting.PingThread.ping(PingThread.java:134)
>> at hudson.remoting.PingThread.run(PingThread.java:90)
>>
>> Nov 20, 2018 6:39:32 PM hudson.slaves.ChannelPinger$1 onDead
>> INFO: Ping failed. Terminating the channel JNLP4-connect connection to 
>> JENKINS_URL/IP:35351.
>> java.util.concurrent.TimeoutException: Ping started at 1542756932704 
>> hasn't completed by 1542757172726
>> at hudson.remoting.PingThread.ping(PingThread.java:134)
>> at hudson.remoting.PingThread.run(PingThread.java:90)
>>
>> Nov 20, 2018 8:38:34 PM hudson.remoting.jnlp.Main createEngine
>> INFO: Setting up agent: HOST_NAME
>> Nov 20, 2018 8:38:34 PM hudson.remoting.jnlp.Main$CuiListener 
>> INFO: Jenkins agent is running in headless mode.
>>
>> Trying to figure out way to increase the heap size.
>>
>> Thanks to all those threw in suggestion.
>>
>> On Monday, November 26, 2018 at 12:44:47 PM UTC-5, gotvi...@gmail.com 
>> wrote:
>>>
>>> The agent port is selected as 'fixed' in the Jenkins master 
>>> configuration.
>>>
>>> On Monday, November 26, 2018 at 12:33:43 PM UTC-5, Pranav Kv wrote:

 Did you checked your port number?My be it is an arbitrary selection. So 
 better to configure the port as fixed number on your master configuration.

 Regards
 Pranav

 On Mon, 26 Nov 2018, 10:52 pm >>>
> Any help/suggestion on this?
>
> On Monday, November 26, 2018 at 11:24:45 AM UTC-5, gotvi...@gmail.com 
> wrote:
>>
>> When I looked in Windows Server event logs, I see this error - 
>> sigint to 81192 failed - killing as feedback
>>
>> I see this message multiple times and the number (81192) is defferent 
>> in every error.
>>
>> On Monday, November 26, 2018 at 10:48:58 AM UTC-5, gotvi...@gmail.com 
>> wrote:
>>>
>>> We have couple of more Windows Slaves, but we don't have any issue 
>>> with those.  Just this one slave going down often.
>>>
>>> On Monday, November 26, 2018 at 10:21:14 AM UTC-5, john.mellor wrote:

 We have that problem all the time. IMHO the JNLP connectivity to 
 the master is not robust enough to be used.

 I have tried setting up the agent connection as a service per the 
 Jenkins doc, but it still cannot survive momentary network or 
 performance 
 outages. The only way that I have managed to get this machine 
 consistent, 
 is to reboot the Windows machine and the service will shortly 
 re-establish 
 connectivity. JNLP connections are just-plain defective.



 On Mon, 2018-11-26 at 07:06 -0800, gotvi...@gmail.com wrote:

 Hello, 

 We have a Windows Server 2016 Jenkins Slave.  The Jenkins service

Re: Jenkins service going down on Windows Slave

2018-11-26 Thread Slide

There should be a way to pass parameters to the JVM in the .xml file
(slave.xml or something similar).

On Mon, Nov 26, 2018 at 1:38 PM  wrote:

> Found a log file on the slave machine.  It's Java heap size error.
>
> INFO: HttpClient configured for $URL, authenticating as USER
> Nov 20, 2018 6:25:09 PM
> com.microsoft.tfs.core.ws.runtime.transport.IdleHTTPConnectionCloser run
> SEVERE: unexpected error
> java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Unknown Source)
> at java.util.Arrays.copyOf(Unknown Source)
> at java.util.ArrayList.grow(Unknown Source)
> at java.util.ArrayList.ensureExplicitCapacity(Unknown Source)
> at java.util.ArrayList.ensureCapacityInternal(Unknown Source)
> at java.util.ArrayList.add(Unknown Source)
> at
> com.microsoft.tfs.core.ws.runtime.transport.IdleHTTPConnectionCloser.run(IdleHTTPConnectionCloser.java:109)
>
> Nov 20, 2018 6:25:12 PM
> org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader run
> SEVERE: [JNLP4-connect connection to JENKINS_URL/IP:35351] Reader thread
> killed by OutOfMemoryError
> java.lang.OutOfMemoryError: Java heap space
>
> Exception in thread "pool-1-thread-3" java.lang.OutOfMemoryError: Java
> heap space
> Nov 20, 2018 6:29:32 PM hudson.slaves.ChannelPinger$1 onDead
> INFO: Ping failed. Terminating the channel JNLP4-connect connection to
> JENKINS_URL/IP:35351.
> java.util.concurrent.TimeoutException: Ping started at 1542756332316
> hasn't completed by 1542756572331
> at hudson.remoting.PingThread.ping(PingThread.java:134)
> at hudson.remoting.PingThread.run(PingThread.java:90)
>
> Nov 20, 2018 6:34:32 PM hudson.slaves.ChannelPinger$1 onDead
> INFO: Ping failed. Terminating the channel JNLP4-connect connection to
> JENKINS_URL/IP:35351.
> java.util.concurrent.TimeoutException: Ping started at 1542756632868
> hasn't completed by 1542756872880
> at hudson.remoting.PingThread.ping(PingThread.java:134)
> at hudson.remoting.PingThread.run(PingThread.java:90)
>
> Nov 20, 2018 6:39:32 PM hudson.slaves.ChannelPinger$1 onDead
> INFO: Ping failed. Terminating the channel JNLP4-connect connection to
> JENKINS_URL/IP:35351.
> java.util.concurrent.TimeoutException: Ping started at 1542756932704
> hasn't completed by 1542757172726
> at hudson.remoting.PingThread.ping(PingThread.java:134)
> at hudson.remoting.PingThread.run(PingThread.java:90)
>
> Nov 20, 2018 8:38:34 PM hudson.remoting.jnlp.Main createEngine
> INFO: Setting up agent: HOST_NAME
> Nov 20, 2018 8:38:34 PM hudson.remoting.jnlp.Main$CuiListener 
> INFO: Jenkins agent is running in headless mode.
>
> Trying to figure out way to increase the heap size.
>
> Thanks to all those threw in suggestion.
>
> On Monday, November 26, 2018 at 12:44:47 PM UTC-5, gotvi...@gmail.com
> wrote:
>>
>> The agent port is selected as 'fixed' in the Jenkins master configuration.
>>
>> On Monday, November 26, 2018 at 12:33:43 PM UTC-5, Pranav Kv wrote:
>>>
>>> Did you checked your port number?My be it is an arbitrary selection. So
>>> better to configure the port as fixed number on your master configuration.
>>>
>>> Regards
>>> Pranav
>>>
>>> On Mon, 26 Nov 2018, 10:52 pm >>
 Any help/suggestion on this?

 On Monday, November 26, 2018 at 11:24:45 AM UTC-5, gotvi...@gmail.com
 wrote:
>
> When I looked in Windows Server event logs, I see this error -
> sigint to 81192 failed - killing as feedback
>
> I see this message multiple times and the number (81192) is defferent
> in every error.
>
> On Monday, November 26, 2018 at 10:48:58 AM UTC-5, gotvi...@gmail.com
> wrote:
>>
>> We have couple of more Windows Slaves, but we don't have any issue
>> with those.  Just this one slave going down often.
>>
>> On Monday, November 26, 2018 at 10:21:14 AM UTC-5, john.mellor wrote:
>>>
>>> We have that problem all the time. IMHO the JNLP connectivity to the
>>> master is not robust enough to be used.
>>>
>>> I have tried setting up the agent connection as a service per the
>>> Jenkins doc, but it still cannot survive momentary network or 
>>> performance
>>> outages. The only way that I have managed to get this machine 
>>> consistent,
>>> is to reboot the Windows machine and the service will shortly 
>>> re-establish
>>> connectivity. JNLP connections are just-plain defective.
>>>
>>>
>>>
>>> On Mon, 2018-11-26 at 07:06 -0800, gotvi...@gmail.com wrote:
>>>
>>> Hello,
>>>
>>> We have a Windows Server 2016 Jenkins Slave.  The Jenkins service in
>>> this slave goes down at times.  We then go back and start it manually
>>> though the service is set to start automatically.  Need help figuring 
>>> out
>>> what's causing it to go down and why it isn't coming back online on its 
>>> own.
>>>
>>> --
 You received this message because you are subscribed to the Google
 Groups "Jenkins Users" group.
 To unsubscribe from this group and

Re: Jenkins service going down on Windows Slave

Found a log file on the slave machine.  It's Java heap size error.

INFO: HttpClient configured for $URL, authenticating as USER
Nov 20, 2018 6:25:09 PM 
com.microsoft.tfs.core.ws.runtime.transport.IdleHTTPConnectionCloser run
SEVERE: unexpected error
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Unknown Source)
at java.util.Arrays.copyOf(Unknown Source)
at java.util.ArrayList.grow(Unknown Source)
at java.util.ArrayList.ensureExplicitCapacity(Unknown Source)
at java.util.ArrayList.ensureCapacityInternal(Unknown Source)
at java.util.ArrayList.add(Unknown Source)
at 
com.microsoft.tfs.core.ws.runtime.transport.IdleHTTPConnectionCloser.run(IdleHTTPConnectionCloser.java:109)

Nov 20, 2018 6:25:12 PM 
org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader run
SEVERE: [JNLP4-connect connection to JENKINS_URL/IP:35351] Reader thread 
killed by OutOfMemoryError
java.lang.OutOfMemoryError: Java heap space

Exception in thread "pool-1-thread-3" java.lang.OutOfMemoryError: Java heap 
space
Nov 20, 2018 6:29:32 PM hudson.slaves.ChannelPinger$1 onDead
INFO: Ping failed. Terminating the channel JNLP4-connect connection to 
JENKINS_URL/IP:35351.
java.util.concurrent.TimeoutException: Ping started at 1542756332316 hasn't 
completed by 1542756572331
at hudson.remoting.PingThread.ping(PingThread.java:134)
at hudson.remoting.PingThread.run(PingThread.java:90)

Nov 20, 2018 6:34:32 PM hudson.slaves.ChannelPinger$1 onDead
INFO: Ping failed. Terminating the channel JNLP4-connect connection to 
JENKINS_URL/IP:35351.
java.util.concurrent.TimeoutException: Ping started at 1542756632868 hasn't 
completed by 1542756872880
at hudson.remoting.PingThread.ping(PingThread.java:134)
at hudson.remoting.PingThread.run(PingThread.java:90)

Nov 20, 2018 6:39:32 PM hudson.slaves.ChannelPinger$1 onDead
INFO: Ping failed. Terminating the channel JNLP4-connect connection to 
JENKINS_URL/IP:35351.
java.util.concurrent.TimeoutException: Ping started at 1542756932704 hasn't 
completed by 1542757172726
at hudson.remoting.PingThread.ping(PingThread.java:134)
at hudson.remoting.PingThread.run(PingThread.java:90)

Nov 20, 2018 8:38:34 PM hudson.remoting.jnlp.Main createEngine
INFO: Setting up agent: HOST_NAME
Nov 20, 2018 8:38:34 PM hudson.remoting.jnlp.Main$CuiListener 
INFO: Jenkins agent is running in headless mode.

Trying to figure out way to increase the heap size.

Thanks to all those threw in suggestion.

On Monday, November 26, 2018 at 12:44:47 PM UTC-5, gotvi...@gmail.com wrote:
>
> The agent port is selected as 'fixed' in the Jenkins master configuration.
>
> On Monday, November 26, 2018 at 12:33:43 PM UTC-5, Pranav Kv wrote:
>>
>> Did you checked your port number?My be it is an arbitrary selection. So 
>> better to configure the port as fixed number on your master configuration.
>>
>> Regards
>> Pranav
>>
>> On Mon, 26 Nov 2018, 10:52 pm >
>>> Any help/suggestion on this?
>>>
>>> On Monday, November 26, 2018 at 11:24:45 AM UTC-5, gotvi...@gmail.com 
>>> wrote:

 When I looked in Windows Server event logs, I see this error - 
 sigint to 81192 failed - killing as feedback

 I see this message multiple times and the number (81192) is defferent 
 in every error.

 On Monday, November 26, 2018 at 10:48:58 AM UTC-5, gotvi...@gmail.com 
 wrote:
>
> We have couple of more Windows Slaves, but we don't have any issue 
> with those.  Just this one slave going down often.
>
> On Monday, November 26, 2018 at 10:21:14 AM UTC-5, john.mellor wrote:
>>
>> We have that problem all the time. IMHO the JNLP connectivity to the 
>> master is not robust enough to be used.
>>
>> I have tried setting up the agent connection as a service per the 
>> Jenkins doc, but it still cannot survive momentary network or 
>> performance 
>> outages. The only way that I have managed to get this machine 
>> consistent, 
>> is to reboot the Windows machine and the service will shortly 
>> re-establish 
>> connectivity. JNLP connections are just-plain defective.
>>
>>
>>
>> On Mon, 2018-11-26 at 07:06 -0800, gotvi...@gmail.com wrote:
>>
>> Hello, 
>>
>> We have a Windows Server 2016 Jenkins Slave.  The Jenkins service in 
>> this slave goes down at times.  We then go back and start it manually 
>> though the service is set to start automatically.  Need help figuring 
>> out 
>> what's causing it to go down and why it isn't coming back online on its 
>> own.
>>
>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to jenkinsci-use...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-users/317ec954-f56e-4990-b183-55f1327aa9ae%40googlegroups.com
>>>  
>>>

Re: Jenkins service going down on Windows Slave

The agent port is selected as 'fixed' in the Jenkins master configuration.

On Monday, November 26, 2018 at 12:33:43 PM UTC-5, Pranav Kv wrote:
>
> Did you checked your port number?My be it is an arbitrary selection. So 
> better to configure the port as fixed number on your master configuration.
>
> Regards
> Pranav
>
> On Mon, 26 Nov 2018, 10:52 pm  wrote:
>
>> Any help/suggestion on this?
>>
>> On Monday, November 26, 2018 at 11:24:45 AM UTC-5, gotvi...@gmail.com 
>> wrote:
>>>
>>> When I looked in Windows Server event logs, I see this error - 
>>> sigint to 81192 failed - killing as feedback
>>>
>>> I see this message multiple times and the number (81192) is defferent in 
>>> every error.
>>>
>>> On Monday, November 26, 2018 at 10:48:58 AM UTC-5, gotvi...@gmail.com 
>>> wrote:

 We have couple of more Windows Slaves, but we don't have any issue with 
 those.  Just this one slave going down often.

 On Monday, November 26, 2018 at 10:21:14 AM UTC-5, john.mellor wrote:
>
> We have that problem all the time. IMHO the JNLP connectivity to the 
> master is not robust enough to be used.
>
> I have tried setting up the agent connection as a service per the 
> Jenkins doc, but it still cannot survive momentary network or performance 
> outages. The only way that I have managed to get this machine consistent, 
> is to reboot the Windows machine and the service will shortly 
> re-establish 
> connectivity. JNLP connections are just-plain defective.
>
>
>
> On Mon, 2018-11-26 at 07:06 -0800, gotvi...@gmail.com wrote:
>
> Hello, 
>
> We have a Windows Server 2016 Jenkins Slave.  The Jenkins service in 
> this slave goes down at times.  We then go back and start it manually 
> though the service is set to start automatically.  Need help figuring out 
> what's causing it to go down and why it isn't coming back online on its 
> own.
>
> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/317ec954-f56e-4990-b183-55f1327aa9ae%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/7e622ae9-df97-4d9a-a8d1-9d65cd5d8ad5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins service going down on Windows Slave

2018-11-26 Thread Pranav Kv

Did you checked your port number?My be it is an arbitrary selection. So
better to configure the port as fixed number on your master configuration.

Regards
Pranav

On Mon, 26 Nov 2018, 10:52 pm  Any help/suggestion on this?
>
> On Monday, November 26, 2018 at 11:24:45 AM UTC-5, gotvi...@gmail.com
> wrote:
>>
>> When I looked in Windows Server event logs, I see this error -
>> sigint to 81192 failed - killing as feedback
>>
>> I see this message multiple times and the number (81192) is defferent in
>> every error.
>>
>> On Monday, November 26, 2018 at 10:48:58 AM UTC-5, gotvi...@gmail.com
>> wrote:
>>>
>>> We have couple of more Windows Slaves, but we don't have any issue with
>>> those.  Just this one slave going down often.
>>>
>>> On Monday, November 26, 2018 at 10:21:14 AM UTC-5, john.mellor wrote:

 We have that problem all the time. IMHO the JNLP connectivity to the
 master is not robust enough to be used.

 I have tried setting up the agent connection as a service per the
 Jenkins doc, but it still cannot survive momentary network or performance
 outages. The only way that I have managed to get this machine consistent,
 is to reboot the Windows machine and the service will shortly re-establish
 connectivity. JNLP connections are just-plain defective.

 On Mon, 2018-11-26 at 07:06 -0800, gotvi...@gmail.com wrote:

 Hello,

 We have a Windows Server 2016 Jenkins Slave.  The Jenkins service in
 this slave goes down at times.  We then go back and start it manually
 though the service is set to start automatically.  Need help figuring out
 what's causing it to go down and why it isn't coming back online on its 
 own.

 --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/317ec954-f56e-4990-b183-55f1327aa9ae%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAHwQEkKzS4VBF3LrYAXhKpE2v%2BVM86%3DqnWgxKsyFQQ47ih0f1w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins service going down on Windows Slave

Any help/suggestion on this?

On Monday, November 26, 2018 at 11:24:45 AM UTC-5, gotvi...@gmail.com wrote:
>
> When I looked in Windows Server event logs, I see this error - 
> sigint to 81192 failed - killing as feedback
>
> I see this message multiple times and the number (81192) is defferent in 
> every error.
>
> On Monday, November 26, 2018 at 10:48:58 AM UTC-5, gotvi...@gmail.com 
> wrote:
>>
>> We have couple of more Windows Slaves, but we don't have any issue with 
>> those.  Just this one slave going down often.
>>
>> On Monday, November 26, 2018 at 10:21:14 AM UTC-5, john.mellor wrote:
>>>
>>> We have that problem all the time. IMHO the JNLP connectivity to the 
>>> master is not robust enough to be used.
>>>
>>> I have tried setting up the agent connection as a service per the 
>>> Jenkins doc, but it still cannot survive momentary network or performance 
>>> outages. The only way that I have managed to get this machine consistent, 
>>> is to reboot the Windows machine and the service will shortly re-establish 
>>> connectivity. JNLP connections are just-plain defective.
>>>
>>>
>>>
>>> On Mon, 2018-11-26 at 07:06 -0800, gotvi...@gmail.com wrote:
>>>
>>> Hello, 
>>>
>>> We have a Windows Server 2016 Jenkins Slave.  The Jenkins service in 
>>> this slave goes down at times.  We then go back and start it manually 
>>> though the service is set to start automatically.  Need help figuring out 
>>> what's causing it to go down and why it isn't coming back online on its own.
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/317ec954-f56e-4990-b183-55f1327aa9ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins service going down on Windows Slave

When I looked in Windows Server event logs, I see this error - 
sigint to 81192 failed - killing as feedback

I see this message multiple times and the number (81192) is defferent in 
every error.

On Monday, November 26, 2018 at 10:48:58 AM UTC-5, gotvi...@gmail.com wrote:
>
> We have couple of more Windows Slaves, but we don't have any issue with 
> those.  Just this one slave going down often.
>
> On Monday, November 26, 2018 at 10:21:14 AM UTC-5, john.mellor wrote:
>>
>> We have that problem all the time. IMHO the JNLP connectivity to the 
>> master is not robust enough to be used.
>>
>> I have tried setting up the agent connection as a service per the Jenkins 
>> doc, but it still cannot survive momentary network or performance outages. 
>> The only way that I have managed to get this machine consistent, is to 
>> reboot the Windows machine and the service will shortly re-establish 
>> connectivity. JNLP connections are just-plain defective.
>>
>>
>>
>> On Mon, 2018-11-26 at 07:06 -0800, gotvi...@gmail.com wrote:
>>
>> Hello, 
>>
>> We have a Windows Server 2016 Jenkins Slave.  The Jenkins service in this 
>> slave goes down at times.  We then go back and start it manually though the 
>> service is set to start automatically.  Need help figuring out what's 
>> causing it to go down and why it isn't coming back online on its own.
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/8e3018ab-b95d-47f0-9433-24ac44861005%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins service going down on Windows Slave

We have couple of more Windows Slaves, but we don't have any issue with 
those.  Just this one slave going down often.

On Monday, November 26, 2018 at 10:21:14 AM UTC-5, john.mellor wrote:
>
> We have that problem all the time. IMHO the JNLP connectivity to the 
> master is not robust enough to be used.
>
> I have tried setting up the agent connection as a service per the Jenkins 
> doc, but it still cannot survive momentary network or performance outages. 
> The only way that I have managed to get this machine consistent, is to 
> reboot the Windows machine and the service will shortly re-establish 
> connectivity. JNLP connections are just-plain defective.
>
>
>
> On Mon, 2018-11-26 at 07:06 -0800, gotvi...@gmail.com  wrote:
>
> Hello, 
>
> We have a Windows Server 2016 Jenkins Slave.  The Jenkins service in this 
> slave goes down at times.  We then go back and start it manually though the 
> service is set to start automatically.  Need help figuring out what's 
> causing it to go down and why it isn't coming back online on its own.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/b4d92c64-a769-42c0-90d4-e9df7e1210d9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins service going down on Windows Slave

Any idea on where else I can look for details?

On Monday, November 26, 2018 at 10:24:10 AM UTC-5, slide wrote:
>
> Weird, I have had ZERO issues with JNLP agents. It works flawlessly for me.
>
> On Mon, Nov 26, 2018 at 8:21 AM John Mellor  > wrote:
>
>> We have that problem all the time. IMHO the JNLP connectivity to the 
>> master is not robust enough to be used.
>>
>> I have tried setting up the agent connection as a service per the Jenkins 
>> doc, but it still cannot survive momentary network or performance outages. 
>> The only way that I have managed to get this machine consistent, is to 
>> reboot the Windows machine and the service will shortly re-establish 
>> connectivity. JNLP connections are just-plain defective.
>>
>>
>>
>> On Mon, 2018-11-26 at 07:06 -0800, gotvi...@gmail.com  
>> wrote:
>>
>> Hello, 
>>
>> We have a Windows Server 2016 Jenkins Slave.  The Jenkins service in this 
>> slave goes down at times.  We then go back and start it manually though the 
>> service is set to start automatically.  Need help figuring out what's 
>> causing it to go down and why it isn't coming back online on its own.
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/0643151142ab642b3a0117ea0b42ab1e41ccfda3.camel%40esentire.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> -- 
> Website: http://earl-of-code.com
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/cc698142-b557-4ce9-ac69-8aa85a7ed476%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins service going down on Windows Slave

2018-11-26 Thread John Mellor

Hi Slide,

We run our worker nodes mostly on sometimes-overloaded VMware hosts. We also
interrupt the undersized network fairly routinely, for other reasons. Can you
try hooking in a network degradation service, so that you see network outages,
for instance.

JNLP connections fail in these circumstances, while ssh connections do not.
Unfortunately, Windows essentially requires JNLP-only connections.

On Mon, 2018-11-26 at 08:23 -0700, Slide wrote:
Weird, I have had ZERO issues with JNLP agents. It works flawlessly for me.

On Mon, Nov 26, 2018 at 8:21 AM John Mellor
mailto:john.mel...@esentire.com>> wrote:
We have that problem all the time. IMHO the JNLP connectivity to the master is
not robust enough to be used.

I have tried setting up the agent connection as a service per the Jenkins doc,
but it still cannot survive momentary network or performance outages. The only
way that I have managed to get this machine consistent, is to reboot the
Windows machine and the service will shortly re-establish connectivity. JNLP
connections are just-plain defective.

On Mon, 2018-11-26 at 07:06 -0800,
gotviser...@gmail.com wrote:
Hello,

We have a Windows Server 2016 Jenkins Slave. The Jenkins service in this slave
goes down at times. We then go back and start it manually though the service
is set to start automatically. Need help figuring out what's causing it to go
down and why it isn't coming back online on its own.

--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/0643151142ab642b3a0117ea0b42ab1e41ccfda3.camel%40esentire.com.
For more options, visit https://groups.google.com/d/optout.

--
Website: http://earl-of-code.com

--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/94638a861184c792de1d164a7b17eef0fa402b41.camel%40esentire.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins service going down on Windows Slave

2018-11-26 Thread Slide

Weird, I have had ZERO issues with JNLP agents. It works flawlessly for me.

On Mon, Nov 26, 2018 at 8:21 AM John Mellor 
wrote:

> We have that problem all the time. IMHO the JNLP connectivity to the
> master is not robust enough to be used.
>
> I have tried setting up the agent connection as a service per the Jenkins
> doc, but it still cannot survive momentary network or performance outages.
> The only way that I have managed to get this machine consistent, is to
> reboot the Windows machine and the service will shortly re-establish
> connectivity. JNLP connections are just-plain defective.
>
>
>
> On Mon, 2018-11-26 at 07:06 -0800, gotviser...@gmail.com wrote:
>
> Hello,
>
> We have a Windows Server 2016 Jenkins Slave.  The Jenkins service in this
> slave goes down at times.  We then go back and start it manually though the
> service is set to start automatically.  Need help figuring out what's
> causing it to go down and why it isn't coming back online on its own.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/0643151142ab642b3a0117ea0b42ab1e41ccfda3.camel%40esentire.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Website: http://earl-of-code.com

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVc-xHbnxYWjnpScOZWxOb8Y2qc0TduQ%3DK%2B%3DNskehQZZ2A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins service going down on Windows Slave

This is all I see in the log section of the Slave.  Is there anywhere else 
to see?

JNLP agent connected from IP/IP
Remoting version: 3.17
This is a Windows agent
Agent successfully connected and online




On Monday, November 26, 2018 at 10:16:59 AM UTC-5, slide wrote:
>
> Did you check the logs on the agent or via the Jenkins UI? (FYI, agent is 
> the preferred term instead of "slave").
>
> On Mon, Nov 26, 2018 at 8:06 AM > wrote:
>
>> Hello,
>>
>> We have a Windows Server 2016 Jenkins Slave.  The Jenkins service in this 
>> slave goes down at times.  We then go back and start it manually though the 
>> service is set to start automatically.  Need help figuring out what's 
>> causing it to go down and why it isn't coming back online on its own.
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/fd7cf10d-fd69-4c20-be36-804f6256890a%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> -- 
> Website: http://earl-of-code.com
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/580f8ba5-1b81-4198-9335-034964390f63%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins service going down on Windows Slave

2018-11-26 Thread John Mellor

We have that problem all the time. IMHO the JNLP connectivity to the master is 
not robust enough to be used.

I have tried setting up the agent connection as a service per the Jenkins doc, 
but it still cannot survive momentary network or performance outages. The only 
way that I have managed to get this machine consistent, is to reboot the 
Windows machine and the service will shortly re-establish connectivity. JNLP 
connections are just-plain defective.



On Mon, 2018-11-26 at 07:06 -0800, gotviser...@gmail.com wrote:
Hello,

We have a Windows Server 2016 Jenkins Slave.  The Jenkins service in this slave 
goes down at times.  We then go back and start it manually though the service 
is set to start automatically.  Need help figuring out what's causing it to go 
down and why it isn't coming back online on its own.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0643151142ab642b3a0117ea0b42ab1e41ccfda3.camel%40esentire.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins service going down on Windows Slave

2018-11-26 Thread Slide

Did you check the logs on the agent or via the Jenkins UI? (FYI, agent is
the preferred term instead of "slave").

On Mon, Nov 26, 2018 at 8:06 AM  wrote:

> Hello,
>
> We have a Windows Server 2016 Jenkins Slave.  The Jenkins service in this
> slave goes down at times.  We then go back and start it manually though the
> service is set to start automatically.  Need help figuring out what's
> causing it to go down and why it isn't coming back online on its own.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/fd7cf10d-fd69-4c20-be36-804f6256890a%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Website: http://earl-of-code.com

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVe6keqT58yMu%3Da10FiWUQOwKxDakWbNNg0%3DL-hA_tBfPg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins service going down on Windows Slave

Hello,

We have a Windows Server 2016 Jenkins Slave.  The Jenkins service in this 
slave goes down at times.  We then go back and start it manually though the 
service is set to start automatically.  Need help figuring out what's 
causing it to go down and why it isn't coming back online on its own.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/fd7cf10d-fd69-4c20-be36-804f6256890a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Configure Linux and Windows slave node

2018-10-17 Thread gotviseryon

Hi,

Thanks for the link.  For Windows, I found this link more helpful 
- https://wiki.jenkins.io/pages/viewpage.action?pageId=75893612

On Monday, October 8, 2018 at 10:00:20 AM UTC-4, Pavel Novák wrote:
>
> Hi,
> there is a link with which describes step by step, how to add the agent , 
> new node 
> https://linuxacademy.com/blog/devops/adding-a-jenkins-agent-node/
>
> It seems to be possible add it via pipeline as well
>
> https://support.cloudbees.com/hc/en-us/articles/218154667-Create-a-Permanent-Agent-from-Groovy-Console
>
> launch methods are:
> - via ssh
> - via webstart
> - via execution command on master
> - control windows slave as windows service
>
> I have linux slaves made by ssh access and windows via webstart, eg. 
>
> Dne čtvrtek 4. října 2018 15:35:53 UTC+2 gotvi...@gmail.com napsal(a):
>>
>> What are the methods to configure a Linux and Windows slave node?
>>
>> Is there a runbook for it?
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/cd8619b4-9bf5-4d0c-9d2d-51b6974773be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Configure Linux and Windows slave node

2018-10-08 Thread Pavel Novák

Hi,
there is a link with which describes step by step, how to add the agent , 
new node 
https://linuxacademy.com/blog/devops/adding-a-jenkins-agent-node/

It seems to be possible add it via pipeline as well
https://support.cloudbees.com/hc/en-us/articles/218154667-Create-a-Permanent-Agent-from-Groovy-Console

launch methods are:
- via ssh
- via webstart
- via execution command on master
- control windows slave as windows service

I have linux slaves made by ssh access and windows via webstart, eg. 

Dne čtvrtek 4. října 2018 15:35:53 UTC+2 gotvi...@gmail.com napsal(a):
>
> What are the methods to configure a Linux and Windows slave node?
>
> Is there a runbook for it?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/4b7a213c-1a59-4555-9d2e-f5b02cb76091%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Configure Linux and Windows slave node

2018-10-04 Thread gotviseryon

What are the methods to configure a Linux and Windows slave node?

Is there a runbook for it?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/7569e5ed-93a8-458a-afd5-9fa34a9bf4c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

running jar on remote windows slave

2017-11-21 Thread danish siddiqui



Hi,


I have jenkins setup on linux and am trying to run a jar file on a remote 
windows machine. I have no problem launching the jar file through jenkins, 
but the problem is the jar file does not exit out of a command prompt so 
this translates into the console output in jenkins (the job never finishes).

Can someone please advise how to do I launch the jar and exit out cleanly)

Apologies I am new to jenkins so do not know much. I have tried to search 
all over the internet and though I did find out by using javaw (but that 
returns successfully if I am manually run the command on the windows box)


Please let me know if you need any other information.


Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/59898116-f7bd-46de-891e-06a39f7e0fc1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline Maven: Running on Windows slave

2017-10-04 Thread Sverre Moe

Here follows an update of some observations and configurations I have done 
to get building on Windows to work.

The Windows node is connected in Jenkins with SSH started by sshd in Cygwin.
Using this 
guide: 
https://www.howtogeek.com/howto/41560/how-to-get-ssh-command-line-access-to-windows-7-using-cygwin/

The Windows node's "Remote root directory" is set to 
"C:\cygwin64\home\build", because "/home/build" would not work.
Step withMaven woulld fail with use of the latter:

[myApp_sverre_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ] 
Running shell script
sh: 
/home/build/workspace/myApp_sverre_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ@tmp/durable-e1932da9/pid:
 No such file or directory
sh: 
/home/build/workspace/myApp_sverre_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ@tmp/durable-e1932da9/jenkins-log.txt:
 No such file or directory
sh: 
/home/build/workspace/myApp_sverre_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ@tmp/durable-e1932da9/jenkins-result.txt:
 No such file or directory


I have also added an additional Windows JDK in Jenkins pointing to 
C:\Program Files\Java\jdk1.8.0_144.
Creating a symlink in cygwin at /usr/java/jdk1.8.0_144 to 
/cygdrive/c/Program\ Files/jdk1.8.0_144 allowed me to use the same Jenkins 
JDK tool for both Windows and Linux (though only with the sh step).

For the time being I have been using the pipeline step bat after checking 
!isUnix().
However with the bat step I must use a different JDK that points to the 
real directory in Windows C:\Program Files\Java\jdk1.8.0_144.
Otherwise withMaven fails to find the JDK at /usr/java/jdk1.8.0_144

[myApp_sverre_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ] 
Running batch script

C:\cygwin64\home\build\workspace\myApp_sverre_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ>mvn
 clean install  
- withMaven Wrapper script -
The JAVA_HOME environment variable is not defined correctly 
This environment variable is needed to run this program 
NB: JAVA_HOME should point to a JDK not a JRE 



Using the sh step instead of the bat step in pipeline kinda works. However 
with one Exception.

[withMaven] use Maven installation provided by the build agent with executable 
C:\Program Files\apache-maven-3.5.0\bin\mvn.cmd
[Pipeline] {

[Pipeline] sh
[C:\cygwin64\home\build\workspace\myApp_sverre_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ]
 Running shell script
Cannot contact master-windows7-x86_64: java.io.IOException: Remote call on 
master-windows7-x86_64 failed

+ mvn clean install

The build continues never the less with success, so I am not sure what 
failed here and what it tried to do on the remote node that caused the 
IOException.


tirsdag 12. september 2017 10.51.46 UTC+2 skrev Cyrille Le Clerc følgende:
>
> Hello Svere,
>
> It seems that we have some work to make withMaven(){} more friendly to 
> Windows+Cygwin users.
>
> We have already tracked:
>
>- JENKINS-44089 Request that withMaven pipeline step produce both mvn 
>and mvn.cmd wrappers on Windows 
><https://issues.jenkins-ci.org/browse/JENKINS-44089>
>- JENKINS-44276 Maven fails in pipeline + cygwin 
><https://issues.jenkins-ci.org/browse/JENKINS-44276>
>
> Some refactoring of the code will be needed to generate both standard 
> Windows and Cygwin friendly scripts on Windows agents.
>
> Please feel free to give us hints on what a smooth integration with 
> Windows and Cygwin should look like.
>
> Cyrille
>
> On Monday, September 11, 2017 at 9:08:53 AM UTC+2, Baptiste Mathus wrote:
>>
>> Hello,
>> I know the developers of that plugin would like to make it as good as 
>> possible. To that, if so, could you please try and summarize what you think 
>> could be made easier/better? And even if possibly a config error, if you 
>> think the error could help more quickly understand what is wrong?
>>
>> Thanks!
>>
>> Le 11 sept. 2017 09:03, "Sverre Moe" <sverr...@gmail.com> a écrit :
>>
>>> The fix was to set the Windows slave Remote Root Directory to Windows URI
>>> C:\cygwin64\home\username
>>>
>>> mandag 11. september 2017 08.35.29 UTC+2 skrev Sverre Moe følgende:
>>>>
>>>> Well, adding a new JDK in Jenkins Tools pointing to the Windows path of 
>>>> Java worked
>>>> Then withMaven(jdk: "jdk1.8-win")
>>>>
>>>> I have though hit another snag. Lots of ERROR after build success.
>>>> ERROR: [withMaven] WARNING: Exception archiving and fingerprinting 
>>>> MavenArtifact{no.spacetec:myApp:jar:1.0.0-SNAPSHOT 
>>>> C:\home\username\workspace\myApp_username_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ\target\

Re: Pipeline Maven: Running on Windows slave

2017-09-12 Thread Cyrille Le Clerc

Hello Svere,

It seems that we have some work to make withMaven(){} more friendly to 
Windows+Cygwin users.

We have already tracked:

   - JENKINS-44089 Request that withMaven pipeline step produce both mvn 
   and mvn.cmd wrappers on Windows 
   <https://issues.jenkins-ci.org/browse/JENKINS-44089>
   - JENKINS-44276 Maven fails in pipeline + cygwin 
   <https://issues.jenkins-ci.org/browse/JENKINS-44276>
   
Some refactoring of the code will be needed to generate both standard 
Windows and Cygwin friendly scripts on Windows agents.

Please feel free to give us hints on what a smooth integration with Windows 
and Cygwin should look like.

Cyrille

On Monday, September 11, 2017 at 9:08:53 AM UTC+2, Baptiste Mathus wrote:
>
> Hello,
> I know the developers of that plugin would like to make it as good as 
> possible. To that, if so, could you please try and summarize what you think 
> could be made easier/better? And even if possibly a config error, if you 
> think the error could help more quickly understand what is wrong?
>
> Thanks!
>
> Le 11 sept. 2017 09:03, "Sverre Moe" <sverr...@gmail.com > a 
> écrit :
>
>> The fix was to set the Windows slave Remote Root Directory to Windows URI
>> C:\cygwin64\home\username
>>
>> mandag 11. september 2017 08.35.29 UTC+2 skrev Sverre Moe følgende:
>>>
>>> Well, adding a new JDK in Jenkins Tools pointing to the Windows path of 
>>> Java worked
>>> Then withMaven(jdk: "jdk1.8-win")
>>>
>>> I have though hit another snag. Lots of ERROR after build success.
>>> ERROR: [withMaven] WARNING: Exception archiving and fingerprinting 
>>> MavenArtifact{no.spacetec:myApp:jar:1.0.0-SNAPSHOT 
>>> C:\home\username\workspace\myApp_username_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ\target\myApp-1.0.0-SNAPSHOT.jar},
>>>  
>>> skip archiving of the artifacts
>>>
>>> ERROR: [withMaven] WARNING: Exception archiving and fingerprinting 
>>> MavenArtifact{no.spacetec:myApp:rpm:1.0.0-SNAPSHOT 
>>> C:\home\username\workspace\myApp_username_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ\target\rpm\myApp-windows-installer\RPMS\noarch\myApp-windows-installer-1.0.0-SNAPSHOT20170911082120.noarch.rpm},
>>>  
>>> skip archiving of the artifacts
>>>
>>> ERROR: [withMaven] WARNING Exception executing Maven reporter 'Junit 
>>> Publisher' / 
>>> org.jenkinsci.plugins.pipeline.maven.publishers.JunitTestsPublisher. Please 
>>> report a bug associated for the component 'pipeline-maven-plugin' at 
>>> https://issues.jenkins-ci.org 
>>> java.lang.IllegalArgumentException: Cannot relativize 
>>> 'C:\home\username\workspace\myApp_username_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ\target/surefire-reports'
>>>  
>>> relatively to 
>>> '/home/username/workspace/myApp_username_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ'
>>> at 
>>> org.jenkinsci.plugins.pipeline.maven.util.XmlUtils.getPathInWorkspace(XmlUtils.java:226)
>>> at 
>>> org.jenkinsci.plugins.pipeline.maven.publishers.JunitTestsPublisher.executeReporter(JunitTestsPublisher.java:234)
>>> at 
>>> org.jenkinsci.plugins.pipeline.maven.publishers.JunitTestsPublisher.process(JunitTestsPublisher.java:181)
>>> at org.jenkinsci.plugins.pipeline.maven.MavenSpyLogProcessor.pr
>>> ocessMavenSpyLogs(MavenSpyLogProcessor.java:109)
>>> at 
>>> org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution$Callback.finished(WithMavenStepExecution.java:864)
>>> at 
>>> org.jenkinsci.plugins.workflow.steps.BodyExecutionCallback$TailCall.onSuccess(BodyExecutionCallback.java:114)
>>> at 
>>> org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$SuccessAdapter.receive(CpsBodyExecution.java:362)
>>> at com.cloudbees.groovy.cps.Outcome.resumeFrom(Outcome.java:73)
>>> at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:165)
>>> at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:162)
>>> at org.codehaus.groovy.runtime.Gr
>>> oovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:122)
>>> at org.codehaus.groovy.runtime.Gr
>>> oovyCategorySupport.use(GroovyCategorySupport.java:261)
>>> at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:162)
>>> at 
>>> org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:19)
>>> at 
>>> org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:35)
>>

Re: Pipeline Maven: Running on Windows slave

2017-09-11 Thread Baptiste Mathus

Hello,
I know the developers of that plugin would like to make it as good as
possible. To that, if so, could you please try and summarize what you think
could be made easier/better? And even if possibly a config error, if you
think the error could help more quickly understand what is wrong?

Thanks!

Le 11 sept. 2017 09:03, "Sverre Moe" <sverre@gmail.com> a écrit :

> The fix was to set the Windows slave Remote Root Directory to Windows URI
> C:\cygwin64\home\username
>
> mandag 11. september 2017 08.35.29 UTC+2 skrev Sverre Moe følgende:
>>
>> Well, adding a new JDK in Jenkins Tools pointing to the Windows path of
>> Java worked
>> Then withMaven(jdk: "jdk1.8-win")
>>
>> I have though hit another snag. Lots of ERROR after build success.
>> ERROR: [withMaven] WARNING: Exception archiving and fingerprinting
>> MavenArtifact{no.spacetec:myApp:jar:1.0.0-SNAPSHOT
>> C:\home\username\workspace\myApp_username_work-3U54DPE57F6TM
>> OZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ\target\myApp-1.0.0-SNAPSHOT.jar},
>> skip archiving of the artifacts
>>
>> ERROR: [withMaven] WARNING: Exception archiving and fingerprinting
>> MavenArtifact{no.spacetec:myApp:rpm:1.0.0-SNAPSHOT
>> C:\home\username\workspace\myApp_username_work-3U54DPE57F6TM
>> OZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ\target\rpm\myApp-
>> windows-installer\RPMS\noarch\myApp-windows-installer-1.0.0-
>> SNAPSHOT20170911082120.noarch.rpm}, skip archiving of the artifacts
>>
>> ERROR: [withMaven] WARNING Exception executing Maven reporter 'Junit
>> Publisher' / 
>> org.jenkinsci.plugins.pipeline.maven.publishers.JunitTestsPublisher.
>> Please report a bug associated for the component 'pipeline-maven-plugin' at
>> https://issues.jenkins-ci.org
>> java.lang.IllegalArgumentException: Cannot relativize
>> 'C:\home\username\workspace\myApp_username_work-3U54DPE57F6T
>> MOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ\target/surefire-reports'
>> relatively to '/home/username/workspace/myAp
>> p_username_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ'
>> at org.jenkinsci.plugins.pipeline.maven.util.XmlUtils.getPathIn
>> Workspace(XmlUtils.java:226)
>> at org.jenkinsci.plugins.pipeline.maven.publishers.JunitTestsPu
>> blisher.executeReporter(JunitTestsPublisher.java:234)
>> at org.jenkinsci.plugins.pipeline.maven.publishers.JunitTestsPu
>> blisher.process(JunitTestsPublisher.java:181)
>> at org.jenkinsci.plugins.pipeline.maven.MavenSpyLogProcessor.pr
>> ocessMavenSpyLogs(MavenSpyLogProcessor.java:109)
>> at org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution$
>> Callback.finished(WithMavenStepExecution.java:864)
>> at org.jenkinsci.plugins.workflow.steps.BodyExecutionCallback$T
>> ailCall.onSuccess(BodyExecutionCallback.java:114)
>> at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$SuccessA
>> dapter.receive(CpsBodyExecution.java:362)
>> at com.cloudbees.groovy.cps.Outcome.resumeFrom(Outcome.java:73)
>> at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:165)
>> at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:162)
>> at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCate
>> goryInfo.use(GroovyCategorySupport.java:122)
>> at org.codehaus.groovy.runtime.GroovyCategorySupport.use(Groovy
>> CategorySupport.java:261)
>> at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:162)
>> at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.
>> access$001(SandboxContinuable.java:19)
>> at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.
>> call(SandboxContinuable.java:35)
>> at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.
>> call(SandboxContinuable.java:32)
>> at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySa
>> ndbox.runInSandbox(GroovySandbox.java:108)
>> at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(S
>> andboxContinuable.java:32)
>> at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(
>> CpsThread.java:174)
>> at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(
>> CpsThreadGroup.java:330)
>> at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$
>> 100(CpsThreadGroup.java:82)
>> at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(
>> CpsThreadGroup.java:242)
>> at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(
>> CpsThreadGroup.java:230)
>> at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.
>> call(CpsVmExecutorService.java:64)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>> at hudson.remoting.SingleLan

Re: Pipeline Maven: Running on Windows slave

The fix was to set the Windows slave Remote Root Directory to Windows URI
C:\cygwin64\home\username

mandag 11. september 2017 08.35.29 UTC+2 skrev Sverre Moe følgende:
>
> Well, adding a new JDK in Jenkins Tools pointing to the Windows path of 
> Java worked
> Then withMaven(jdk: "jdk1.8-win")
>
> I have though hit another snag. Lots of ERROR after build success.
> ERROR: [withMaven] WARNING: Exception archiving and fingerprinting 
> MavenArtifact{no.spacetec:myApp:jar:1.0.0-SNAPSHOT 
> C:\home\username\workspace\myApp_username_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ\target\myApp-1.0.0-SNAPSHOT.jar},
>  
> skip archiving of the artifacts
>
> ERROR: [withMaven] WARNING: Exception archiving and fingerprinting 
> MavenArtifact{no.spacetec:myApp:rpm:1.0.0-SNAPSHOT 
> C:\home\username\workspace\myApp_username_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ\target\rpm\myApp-windows-installer\RPMS\noarch\myApp-windows-installer-1.0.0-SNAPSHOT20170911082120.noarch.rpm},
>  
> skip archiving of the artifacts
>
> ERROR: [withMaven] WARNING Exception executing Maven reporter 'Junit 
> Publisher' / 
> org.jenkinsci.plugins.pipeline.maven.publishers.JunitTestsPublisher. Please 
> report a bug associated for the component 'pipeline-maven-plugin' at 
> https://issues.jenkins-ci.org 
> java.lang.IllegalArgumentException: Cannot relativize 
> 'C:\home\username\workspace\myApp_username_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ\target/surefire-reports'
>  
> relatively to 
> '/home/username/workspace/myApp_username_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ'
> at 
> org.jenkinsci.plugins.pipeline.maven.util.XmlUtils.getPathInWorkspace(XmlUtils.java:226)
> at 
> org.jenkinsci.plugins.pipeline.maven.publishers.JunitTestsPublisher.executeReporter(JunitTestsPublisher.java:234)
> at 
> org.jenkinsci.plugins.pipeline.maven.publishers.JunitTestsPublisher.process(JunitTestsPublisher.java:181)
> at 
> org.jenkinsci.plugins.pipeline.maven.MavenSpyLogProcessor.processMavenSpyLogs(MavenSpyLogProcessor.java:109)
> at 
> org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution$Callback.finished(WithMavenStepExecution.java:864)
> at 
> org.jenkinsci.plugins.workflow.steps.BodyExecutionCallback$TailCall.onSuccess(BodyExecutionCallback.java:114)
> at 
> org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$SuccessAdapter.receive(CpsBodyExecution.java:362)
> at com.cloudbees.groovy.cps.Outcome.resumeFrom(Outcome.java:73)
> at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:165)
> at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:162)
> at 
> org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:122)
> at 
> org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:261)
> at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:162)
> at 
> org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:19)
> at 
> org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:35)
> at 
> org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:32)
> at 
> org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108)
> at 
> org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:32)
> at 
> org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:174)
> at 
> org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:330)
> at 
> org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:82)
> at 
> org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:242)
> at 
> org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:230)
> at 
> org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)
> at 
> jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
>
> ERROR: [withMaven] WARNING Exception executing Maven reporter 'Open Task 
> Scanner Publisher' / 
> org.jenkinsci.plugins.pipeline.maven.publishers.Task

Re: Pipeline Maven: Running on Windows slave

 JAVA_HOME = "/usr/java/jdk1.8.0_102" 
> Please set the JAVA_HOME variable in your environment to match the 
> location of your Java installation. 
>
>
> Jenkins have jdk set at /usr/java/jdk1.8.0_102 and I have created a 
> symlink in my Cygwin
> jdk1.8.0_102 -> /cygdrive/c/Program Files/Java/jdk1.8.0_121
> Windows environment variable JAVA_HOME is set to C:\Program 
> Files\Java\jdk1.8.0_121
>
> mandag 11. september 2017 08.07.21 UTC+2 skrev Sverre Moe følgende:
>>
>> I have connected a Windows slave to Jenkins with SSH+Cygwin.
>> So running shell scripts like "sh 'mvn'" should work as I do it locally 
>> on the Windows.
>>
>> Running withMaven fails, and I cannot figure our why.
>>
>> [Pipeline] node
>> Running on master-windows-x86_64 in 
>> /home/username/workspace/myApp_username_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ
>> [Pipeline] {
>> [Pipeline] stage
>> [Pipeline] { (Checkout-Windows)
>> [Pipeline] checkout
>>  > git rev-parse --is-inside-work-tree # timeout=10
>> Fetching changes from the remote Git repository
>>  > git config remote.origin.url ssh://
>> g...@git.company.com/software/myApp.git # timeout=10
>> Fetching without tags
>> Fetching upstream changes from ssh://
>> g...@git.company.com/software/myApp.git
>>  > git --version # timeout=10
>>  > git fetch --no-tags --progress ssh://
>> g...@git.company.com/software/myApp.git 
>> +refs/heads/*:refs/remotes/origin/*
>> Checking out Revision 05cf171deb903a01b5880c30de28d4b1865e3ed5 
>> (username/work)
>> Commit message: "Test Windows build on Jenkins"
>>  > git config core.sparsecheckout # timeout=10
>>  > git checkout -f 05cf171deb903a01b5880c30de28d4b1865e3ed5
>>  > git rev-list f9db8914f5688ca74e571dd1104c279f207bf435 # timeout=10
>> [Pipeline] }
>> [Pipeline] // stage
>> [Pipeline] stage
>> [Pipeline] { (Build-Windows)
>> [Pipeline] withMaven
>> [withMaven] Options: []
>> [withMaven] Available options: 
>> [withMaven] use JDK installation jdk1.8
>> $ where mvn.cmd
>> [withMaven] use Maven installation provided by the build agent with 
>> executable 
>> C:\Users\username.POLAR\Downloads\apache-maven-3.3.9-bin\apache-maven-3.3.9\bin\mvn.cmd
>> [Pipeline] {
>> [Pipeline] sh
>> [myApp_username_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ] 
>> Running shell script
>> sh: 
>> /home/username/workspace/myApp_username_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ@tmp/durable-ff9c24b3/pid:
>>  
>> No such file or directory
>> sh: 
>> /home/username/workspace/myApp_username_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ@tmp/durable-ff9c24b3/jenkins-log.txt:
>>  
>> No such file or directory
>> sh: 
>> /home/username/workspace/myApp_username_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ@tmp/durable-ff9c24b3/jenkins-result.txt:
>>  
>> No such file or directory
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/cd9eb59b-d6f0-45db-abfb-e1f64b1f7212%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline Maven: Running on Windows slave

I took a look at the Maven Pipeline documentation again.
For Windows it says to use bat, not sh. I tried that, and got a little bit 
closer, but now it cannot find JAVA_HOME

- withMaven Wrapper script -

Error: JAVA_HOME is set to an invalid directory. 
JAVA_HOME = "/usr/java/jdk1.8.0_102" 
Please set the JAVA_HOME variable in your environment to match the 
location of your Java installation. 


Jenkins have jdk set at /usr/java/jdk1.8.0_102 and I have created a symlink 
in my Cygwin
jdk1.8.0_102 -> /cygdrive/c/Program Files/Java/jdk1.8.0_121
Windows environment variable JAVA_HOME is set to C:\Program 
Files\Java\jdk1.8.0_121

mandag 11. september 2017 08.07.21 UTC+2 skrev Sverre Moe følgende:
>
> I have connected a Windows slave to Jenkins with SSH+Cygwin.
> So running shell scripts like "sh 'mvn'" should work as I do it locally on 
> the Windows.
>
> Running withMaven fails, and I cannot figure our why.
>
> [Pipeline] node
> Running on master-windows-x86_64 in 
> /home/username/workspace/myApp_username_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ
> [Pipeline] {
> [Pipeline] stage
> [Pipeline] { (Checkout-Windows)
> [Pipeline] checkout
>  > git rev-parse --is-inside-work-tree # timeout=10
> Fetching changes from the remote Git repository
>  > git config remote.origin.url ssh://
> g...@git.company.com/software/myApp.git # timeout=10
> Fetching without tags
> Fetching upstream changes from ssh://
> g...@git.company.com/software/myApp.git
>  > git --version # timeout=10
>  > git fetch --no-tags --progress ssh://
> g...@git.company.com/software/myApp.git +refs/heads/*:refs/remotes/origin/*
> Checking out Revision 05cf171deb903a01b5880c30de28d4b1865e3ed5 
> (username/work)
> Commit message: "Test Windows build on Jenkins"
>  > git config core.sparsecheckout # timeout=10
>  > git checkout -f 05cf171deb903a01b5880c30de28d4b1865e3ed5
>  > git rev-list f9db8914f5688ca74e571dd1104c279f207bf435 # timeout=10
> [Pipeline] }
> [Pipeline] // stage
> [Pipeline] stage
> [Pipeline] { (Build-Windows)
> [Pipeline] withMaven
> [withMaven] Options: []
> [withMaven] Available options: 
> [withMaven] use JDK installation jdk1.8
> $ where mvn.cmd
> [withMaven] use Maven installation provided by the build agent with 
> executable 
> C:\Users\username.POLAR\Downloads\apache-maven-3.3.9-bin\apache-maven-3.3.9\bin\mvn.cmd
> [Pipeline] {
> [Pipeline] sh
> [myApp_username_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ] 
> Running shell script
> sh: 
> /home/username/workspace/myApp_username_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ@tmp/durable-ff9c24b3/pid:
>  
> No such file or directory
> sh: 
> /home/username/workspace/myApp_username_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ@tmp/durable-ff9c24b3/jenkins-log.txt:
>  
> No such file or directory
> sh: 
> /home/username/workspace/myApp_username_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ@tmp/durable-ff9c24b3/jenkins-result.txt:
>  
> No such file or directory
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/96c3a3ff-30c5-4646-991c-495c529657aa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Pipeline Maven: Running on Windows slave