Re: Odd environment problem with git under Jenkins on AIX

[Mark Waite]

Sorry, but no suggestions to offer on how to resolve that issue.

I would suggest that you host the Jenkins master on Linux or Windows and
run an agent on AIX.  Running the master on AIX probably places you in the
"less than 0.1% of all users" category.

On Thu, Apr 25, 2019 at 1:30 PM Rich Stephens  wrote:

> I have finally gotten Jenkins and the git plugin running (I have managed
> to upgrade to Java8).
>
> git works perfectly from the command line.
>
> If I include /opt/freeware/lib into the LIBPATH when starting jenkins,
> when I try to connect to a remove repository, I get basically this error:
>
> OpenSSL version mismatch. Built against 1000105f, you have 10bf
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
>
> Coincidentally, this is the same error that I get if I include
> /opt/freeware/lib in my own LIBPATH.
>
> If I _don't_ include /opt/freeware/lib in the LIBPATH for jenkins, I get:
>
> Failed to connect to repository : Command "git ls-remote -h ssh://
> g...@stash.saas-p.com:7999/optio/core.git HEAD" returned status code 255:
> stdout:
> stderr: exec(): 0509-036 Cannot load program git because of the following
> errors:
> 0509-150   Dependent module /usr/lib/libiconv.a(libiconv.so.2) could not
> be loaded.
> 0509-152   Member libiconv.so.2 is not found in archive
>
> If I don't include it in my own LIBPATH, git works normally.
>
> I tried reproducing my own PATH and LIBPATH in the startup script for git,
> but still no joy.  I get the second error.
>
>
> Obviously there is some sort of environment issue with jenkins, but I
> can't figure out what it is.
> Any thoughts?
>
>
>
>
>
>
>
> --
> 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/87b14e73-7fc1-49aa-b944-e227b473146c%40googlegroups.com
> 
> .
> 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/CAO49JtH0kyvWKvTYGqJ9-GrZea1H7UkyBVrcH7t1Bccw3heJ0w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Remote logging Kubernetes agents dying due to channel closed exception

[Carlos Sanchez]

you should look into the networking layer in your kubernetes cluster, it
may be aggressively closing connections

On Thu, Apr 25, 2019 at 8:34 PM Andrew Feller  wrote:

> We've been trying to troubleshoot OpenShift-support
>  Jenkins
> Kubernetes agents terminating due to closed channel exceptions and reaching
> for straws here.  We're considering enabling remote logging
>  as a
> last ditch effort to debug what is going on within the JNLP container,
> however I'm not sure how configuring -workDir
>  should
> take into account ephemeral Kubernetes pods for agents.
>
> Any help would be appreciated!
> --
>
> [image: BandwidthMaroon.png]
>
> Andy Feller  •  Sr DevOps Engineer
>
> 900 Main Campus Drive, Suite 500, Raleigh, NC 27606
>
>
> e: afel...@bandwidth.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/CAAg6KNENkQCCMSP4%2BOp99rxbcyGeSSjUA4-Fv_o8i1N4gsiJWQ%40mail.gmail.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/CALHFn6N1HsVKQ1Fm6CFXsJ-HN1p%2Bo28eCYR7NaYC%3DBvJ8L2C7Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Recovering jenkins.io account

[Baptiste Mathus]

Likely the infra ml, or on IRC, would better serve this.

Cheers

Le mar. 23 avr. 2019 à 17:43, James Telfer  a
écrit :

> Hi,
>
> Not sure this is the right place, but
> https://accounts.jenkins.io/passwordReset just says 'contact us' without
> a link as to how
>
> I believe I have an existing jenkins.io account linked to an email
> address I no longer have access to.  I'd like to continue using that
> account and link to a new email address (this one).  Any chance that is
> possible?
>
> --
> 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/97ed73a4-f571-42dd-a57c-ccc6aef48046%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/CANWgJS6rcxsyq-BLJR4GdQ7RdkoKngJiG%2BLV10JYNJ9qCM_XDg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Odd environment problem with git under Jenkins on AIX

[Rich Stephens]

I have finally gotten Jenkins and the git plugin running (I have managed to 
upgrade to Java8).

git works perfectly from the command line.

If I include /opt/freeware/lib into the LIBPATH when starting jenkins, when 
I try to connect to a remove repository, I get basically this error:

OpenSSL version mismatch. Built against 1000105f, you have 10bf
fatal: Could not read from remote repository.

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

Coincidentally, this is the same error that I get if I include 
/opt/freeware/lib in my own LIBPATH.

If I _don't_ include /opt/freeware/lib in the LIBPATH for jenkins, I get:

Failed to connect to repository : Command "git ls-remote -h 
ssh://g...@stash.saas-p.com:7999/optio/core.git HEAD" returned status code 
255:
stdout:
stderr: exec(): 0509-036 Cannot load program git because of the following 
errors:
0509-150   Dependent module /usr/lib/libiconv.a(libiconv.so.2) could not be 
loaded.
0509-152   Member libiconv.so.2 is not found in archive 

If I don't include it in my own LIBPATH, git works normally.

I tried reproducing my own PATH and LIBPATH in the startup script for git, 
but still no joy.  I get the second error.


Obviously there is some sort of environment issue with jenkins, but I can't 
figure out what it is.
Any thoughts?







-- 
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/87b14e73-7fc1-49aa-b944-e227b473146c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Remote logging Kubernetes agents dying due to channel closed exception

[Andrew Feller]

We've been trying to troubleshoot OpenShift-support
 Jenkins
Kubernetes agents terminating due to closed channel exceptions and reaching
for straws here.  We're considering enabling remote logging
 as a
last ditch effort to debug what is going on within the JNLP container,
however I'm not sure how configuring -workDir
 should
take into account ephemeral Kubernetes pods for agents.

Any help would be appreciated!
-- 

[image: BandwidthMaroon.png]

Andy Feller  •  Sr DevOps Engineer

900 Main Campus Drive, Suite 500, Raleigh, NC 27606


e: afel...@bandwidth.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/CAAg6KNENkQCCMSP4%2BOp99rxbcyGeSSjUA4-Fv_o8i1N4gsiJWQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: JNLP java.nio.channels.ClosedChannelException with kubernetes-plugin

[Carlos Sanchez]

what flavor of kubernetes ? cloud? on prem? how was it built? what
networking is it using?
there are a lot of variations so the best chance to find out is to relate
with other people's environment and try to isolate

On Thu, Apr 25, 2019 at 6:36 PM Gopi  wrote:

> Hi
> Using latest Kubernetes 1.13 with 3 master nodes.
>
> On Thu, Apr 25, 2019 at 2:15 PM Carlos Sanchez  wrote:
>
>> what kubernetes cluster are you using and with what networking?
>> my guess is that the underlying network layer is killing inactive
>> connections
>>
>> On Thu, Apr 25, 2019 at 4:24 AM Gopi Naidu  wrote:
>>
>>> I have got into the same issue. Could you please post the solution if
>>> anything is found?
>>>
>>> On Sunday, 26 August 2018 04:28:47 UTC+5:30, fabio...@singlepoint.ie
>>> wrote:

 I'm using Kubernetes plugin 1.12.3

 The plugin works well, but whenever the agent does streams the log to
 the master, it causes a connection exception as follows.
 To reproduce, simply create a free style job, restrict to run on the
 kubernetes pod, and add a step to sleep for 300 seconds.


 FATAL: command execution failed
 java.nio.channels.ClosedChannelException
at 
 org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)
at 
 org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:142)
at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:795)
at 
 jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at 
 jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
 Caused: java.io.IOException: Backing channel 'JNLP4-connect connection 
 from ip-192-168-247-3.us-west-2.compute.internal/192.168.247.3:23684' is 
 disconnected.
at 
 hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:214)
at 
 hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283)
at com.sun.proxy.$Proxy110.isAlive(Unknown Source)
at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1137)
at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1129)
at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:155)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:109)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at 
 hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
at hudson.model.Build$BuildExecution.build(Build.java:206)
at hudson.model.Build$BuildExecution.doRun(Build.java:163)
at 
 hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
at hudson.model.Run.execute(Run.java:1798)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429)
 FATAL: Unable to delete script file /tmp/jenkins5788393309854271460.sh
 java.nio.channels.ClosedChannelException
at 
 org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)
at 
 org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:142)
at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:795)
at 
 jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at 
 jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
 Caused: hudson.remoting.ChannelClosedException: Channel "unknown": Remote 
 call on JNLP4-connect connection from 
 ip-192-168-247-3.us-west-2.compute.internal/192.168.247.3:23684 failed. 
 The channel is closing down or has closed down
at hudson.remoting.Channel.call(Channel.java:948)
at hudson.FilePath.act(FilePath.java:1036)
at hudson.FilePath.act(FilePath.java:1025)
at hudson.FilePath.delete(FilePath.java:1511)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:123)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at 
 

Re: JNLP java.nio.channels.ClosedChannelException with kubernetes-plugin

[Gopi]

Hi
Using latest Kubernetes 1.13 with 3 master nodes.

On Thu, Apr 25, 2019 at 2:15 PM Carlos Sanchez  wrote:

> what kubernetes cluster are you using and with what networking?
> my guess is that the underlying network layer is killing inactive
> connections
>
> On Thu, Apr 25, 2019 at 4:24 AM Gopi Naidu  wrote:
>
>> I have got into the same issue. Could you please post the solution if
>> anything is found?
>>
>> On Sunday, 26 August 2018 04:28:47 UTC+5:30, fabio...@singlepoint.ie
>> wrote:
>>>
>>> I'm using Kubernetes plugin 1.12.3
>>>
>>> The plugin works well, but whenever the agent does streams the log to
>>> the master, it causes a connection exception as follows.
>>> To reproduce, simply create a free style job, restrict to run on the
>>> kubernetes pod, and add a step to sleep for 300 seconds.
>>>
>>>
>>> FATAL: command execution failed
>>> java.nio.channels.ClosedChannelException
>>> at 
>>> org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)
>>> at 
>>> org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:142)
>>> at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:795)
>>> at 
>>> jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
>>> at 
>>> jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
>>> at 
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>>> at 
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>>> at java.lang.Thread.run(Thread.java:748)
>>> Caused: java.io.IOException: Backing channel 'JNLP4-connect connection from 
>>> ip-192-168-247-3.us-west-2.compute.internal/192.168.247.3:23684' is 
>>> disconnected.
>>> at 
>>> hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:214)
>>> at 
>>> hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283)
>>> at com.sun.proxy.$Proxy110.isAlive(Unknown Source)
>>> at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1137)
>>> at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1129)
>>> at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:155)
>>> at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:109)
>>> at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66)
>>> at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
>>> at 
>>> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
>>> at hudson.model.Build$BuildExecution.build(Build.java:206)
>>> at hudson.model.Build$BuildExecution.doRun(Build.java:163)
>>> at 
>>> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
>>> at hudson.model.Run.execute(Run.java:1798)
>>> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
>>> at hudson.model.ResourceController.execute(ResourceController.java:97)
>>> at hudson.model.Executor.run(Executor.java:429)
>>> FATAL: Unable to delete script file /tmp/jenkins5788393309854271460.sh
>>> java.nio.channels.ClosedChannelException
>>> at 
>>> org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)
>>> at 
>>> org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:142)
>>> at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:795)
>>> at 
>>> jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
>>> at 
>>> jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
>>> at 
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>>> at 
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>>> at java.lang.Thread.run(Thread.java:748)
>>> Caused: hudson.remoting.ChannelClosedException: Channel "unknown": Remote 
>>> call on JNLP4-connect connection from 
>>> ip-192-168-247-3.us-west-2.compute.internal/192.168.247.3:23684 failed. The 
>>> channel is closing down or has closed down
>>> at hudson.remoting.Channel.call(Channel.java:948)
>>> at hudson.FilePath.act(FilePath.java:1036)
>>> at hudson.FilePath.act(FilePath.java:1025)
>>> at hudson.FilePath.delete(FilePath.java:1511)
>>> at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:123)
>>> at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66)
>>> at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
>>> at 
>>> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
>>> at hudson.model.Build$BuildExecution.build(Build.java:206)
>>> at hudson.model.Build$BuildExecution.doRun(Build.java:163)
>>> at 
>>> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
>>> at 

Hung build with "(part)" status on main page

[Viacheslav Dubrovskyi]

Hi All

I use pipeline for build and sometimes build finished on build page, but 
on main page this build not finished and hung with "(part)" word. Look 
to the screenshot.


Jenkins ver. 2.164.2


My questions:

1. What does it mean?

2. How to fix it?


Thank you for help!

--
WBD,
Viacheslav Dubrovskyi

--
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/d6baad47-ca9b-6e25-3415-3254ccac6e56%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


smime.p7s
Description: Криптографическая подпись S/MIME

OWASP Dependency-Check

[mafiikaaa]

Hi,

I'm trying to run the OWASP Dependency-Check Plugin but with the local 
version of the NVD database. Unfortunately, when I put the database in the 
folder (as a gz lub xml files) and give it a link to Jenkins, Jenkins still 
claims that the database doesn't exist.
Does anyone know how to solve 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/5a60d34d-4369-4ef0-ab27-0ccb6ab3bb78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Under Jenkins SignTool Error "No certificates were found", works fine logged on as user

[Mark Waite]

On Thu, Apr 25, 2019 at 7:10 AM Hello Universe  wrote:

> How to use installed certificates from win8 using signtool?
>
>
Run the Windows agent from the Windows desktop rather than running it from
a service which has been allowed to interact with the desktop.  There seem
to be cases where programs run from services allowed to interact with the
desktop don't have the exact same capabilities as programs run from the
desktop.

Mark Waite


> On Thursday, August 27, 2015 at 10:51:29 PM UTC+8, Ed of the Mountain
> wrote:
>>
>> When I try to code sign in my Jenkins job I receive a SignTool error:
>>
>>
>> c:\jenkins\workspace\codesign-windows>
>>
>> signtool sign /t http://timestamp.digicert.com /n "Acme Inc." code.exe
>>
>> SignTool Error: No certificates were found that met all the given criteria.
>>
>>
>> I am using a DigiCert Extend Validation ( EV ) USB token that requires the 
>> USB token be connected to the build machine.  This works fine when logged on 
>> as normal user.
>>
>>
>>- I am running Jenkins as a Windows service.
>>- Service Log On is set to Local System account.
>>- Service is *allowed to interact with desktop.*
>>
>>
>>
>> When I logon as a normal user to the build machine, it works fine.
>>
>>
>> 1 - signtool sign /t http://timestamp.digicert.com /n "Acme Inc." code.exe
>>
>> 2 - This triggers a pop-up "Token Logon" dialog that requires user 
>> interaction
>>
>> 3 - I have a separate "Token Logon" watcher that finds the WIndows ID and 
>> enters password.
>>
>> 4 - Code is signed automatically
>>
>>
>> C:\jenkins\workspace\codesign-windows>signtool sign /t 
>> http://timestamp.digicert
>> .com /n "The Charles Machine Works, Inc." token-logon.exe
>> Done Adding Additional Store
>> Successfully signed: token-logon.exe
>>
>>
>> Any suggestions to try are much appreciated,
>>
>>
>> -Ed
>>
>> --
> 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/5c8ab94c-96ef-433d-9753-44336a67f2d5%40googlegroups.com
> 
> .
> 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/CAO49JtGEuESLQpVtO-XP9QwAies3w%3D0BV%2BNwt1MoWBLS%3DsyirA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Under Jenkins SignTool Error "No certificates were found", works fine logged on as user

[Slide]

Are the certificates in the certificate store for just the "normal user" or
are they installed in the machine store? The Jenkins service, by default,
it running as LocalSystemUser. That account would need access to the
certificate store.

On Thu, Apr 25, 2019, 06:10 Hello Universe  wrote:

> How to use installed certificates from win8 using signtool?
>
> On Thursday, August 27, 2015 at 10:51:29 PM UTC+8, Ed of the Mountain
> wrote:
>>
>> When I try to code sign in my Jenkins job I receive a SignTool error:
>>
>>
>> c:\jenkins\workspace\codesign-windows>
>>
>> signtool sign /t http://timestamp.digicert.com /n "Acme Inc." code.exe
>>
>> SignTool Error: No certificates were found that met all the given criteria.
>>
>>
>> I am using a DigiCert Extend Validation ( EV ) USB token that requires the 
>> USB token be connected to the build machine.  This works fine when logged on 
>> as normal user.
>>
>>
>>- I am running Jenkins as a Windows service.
>>- Service Log On is set to Local System account.
>>- Service is *allowed to interact with desktop.*
>>
>>
>>
>> When I logon as a normal user to the build machine, it works fine.
>>
>>
>> 1 - signtool sign /t http://timestamp.digicert.com /n "Acme Inc." code.exe
>>
>> 2 - This triggers a pop-up "Token Logon" dialog that requires user 
>> interaction
>>
>> 3 - I have a separate "Token Logon" watcher that finds the WIndows ID and 
>> enters password.
>>
>> 4 - Code is signed automatically
>>
>>
>> C:\jenkins\workspace\codesign-windows>signtool sign /t 
>> http://timestamp.digicert
>> .com /n "The Charles Machine Works, Inc." token-logon.exe
>> Done Adding Additional Store
>> Successfully signed: token-logon.exe
>>
>>
>> Any suggestions to try are much appreciated,
>>
>>
>> -Ed
>>
>> --
> 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/5c8ab94c-96ef-433d-9753-44336a67f2d5%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/CAPiUgVcc50Rg4HO2797kEXNOjVUeiS2%3D8t%2Bb%2BXq0pVNhPNx18w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Under Jenkins SignTool Error "No certificates were found", works fine logged on as user

[Hello Universe]

How to use installed certificates from win8 using signtool?

On Thursday, August 27, 2015 at 10:51:29 PM UTC+8, Ed of the Mountain wrote:
>
> When I try to code sign in my Jenkins job I receive a SignTool error:
>
>
> c:\jenkins\workspace\codesign-windows>
>
> signtool sign /t http://timestamp.digicert.com /n "Acme Inc." code.exe 
>
> SignTool Error: No certificates were found that met all the given criteria.
>
>
> I am using a DigiCert Extend Validation ( EV ) USB token that requires the 
> USB token be connected to the build machine.  This works fine when logged on 
> as normal user.
>
>
>- I am running Jenkins as a Windows service.
>- Service Log On is set to Local System account.
>- Service is *allowed to interact with desktop.*
>
>
>
> When I logon as a normal user to the build machine, it works fine.
>
>
> 1 - signtool sign /t http://timestamp.digicert.com /n "Acme Inc." code.exe
>
> 2 - This triggers a pop-up "Token Logon" dialog that requires user interaction
>
> 3 - I have a separate "Token Logon" watcher that finds the WIndows ID and 
> enters password.
>
> 4 - Code is signed automatically
>
>
> C:\jenkins\workspace\codesign-windows>signtool sign /t 
> http://timestamp.digicert
> .com /n "The Charles Machine Works, Inc." token-logon.exe
> Done Adding Additional Store
> Successfully signed: token-logon.exe
>
>
> Any suggestions to try are much appreciated,
>
>
> -Ed
>
>

-- 
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/5c8ab94c-96ef-433d-9753-44336a67f2d5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Env variable in pipeline resolves to null

[b o b i]

PS 
  sh('printenv | sort')
is also not showing any env var set ... :|

-- 
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/daf69d41-066e-44c6-ab9e-5e26a0b0d3af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Env variable in pipeline resolves to null

[b o b i]

 environment {
   TEST_PATH = "path/to/any"
}

// scriptive pipeline
withEnv(["TEST_PATH1=path/to/any"]) {
  echo env.TEST_PATH1  // path/to/any
}

echo "OOO=${env.TEST_PATH}";  // null
echo "UUU=${env.TEST_PATH1}";  // null


How could I make an environment varialbe known to the pipeline (tha above 
didnt work)?

-- 
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/f373bc34-f02f-41b0-95c9-d058dcf1d50f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: JNLP java.nio.channels.ClosedChannelException with kubernetes-plugin

[Carlos Sanchez]

what kubernetes cluster are you using and with what networking?
my guess is that the underlying network layer is killing inactive
connections

On Thu, Apr 25, 2019 at 4:24 AM Gopi Naidu  wrote:

> I have got into the same issue. Could you please post the solution if
> anything is found?
>
> On Sunday, 26 August 2018 04:28:47 UTC+5:30, fabio...@singlepoint.ie
> wrote:
>>
>> I'm using Kubernetes plugin 1.12.3
>>
>> The plugin works well, but whenever the agent does streams the log to the
>> master, it causes a connection exception as follows.
>> To reproduce, simply create a free style job, restrict to run on the
>> kubernetes pod, and add a step to sleep for 300 seconds.
>>
>>
>> FATAL: command execution failed
>> java.nio.channels.ClosedChannelException
>>  at 
>> org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)
>>  at 
>> org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:142)
>>  at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:795)
>>  at 
>> jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
>>  at 
>> jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
>>  at 
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>>  at 
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>>  at java.lang.Thread.run(Thread.java:748)
>> Caused: java.io.IOException: Backing channel 'JNLP4-connect connection from 
>> ip-192-168-247-3.us-west-2.compute.internal/192.168.247.3:23684' is 
>> disconnected.
>>  at 
>> hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:214)
>>  at 
>> hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283)
>>  at com.sun.proxy.$Proxy110.isAlive(Unknown Source)
>>  at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1137)
>>  at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1129)
>>  at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:155)
>>  at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:109)
>>  at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66)
>>  at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
>>  at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
>>  at hudson.model.Build$BuildExecution.build(Build.java:206)
>>  at hudson.model.Build$BuildExecution.doRun(Build.java:163)
>>  at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
>>  at hudson.model.Run.execute(Run.java:1798)
>>  at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
>>  at hudson.model.ResourceController.execute(ResourceController.java:97)
>>  at hudson.model.Executor.run(Executor.java:429)
>> FATAL: Unable to delete script file /tmp/jenkins5788393309854271460.sh
>> java.nio.channels.ClosedChannelException
>>  at 
>> org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)
>>  at 
>> org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:142)
>>  at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:795)
>>  at 
>> jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
>>  at 
>> jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
>>  at 
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>>  at 
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>>  at java.lang.Thread.run(Thread.java:748)
>> Caused: hudson.remoting.ChannelClosedException: Channel "unknown": Remote 
>> call on JNLP4-connect connection from 
>> ip-192-168-247-3.us-west-2.compute.internal/192.168.247.3:23684 failed. The 
>> channel is closing down or has closed down
>>  at hudson.remoting.Channel.call(Channel.java:948)
>>  at hudson.FilePath.act(FilePath.java:1036)
>>  at hudson.FilePath.act(FilePath.java:1025)
>>  at hudson.FilePath.delete(FilePath.java:1511)
>>  at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:123)
>>  at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66)
>>  at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
>>  at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
>>  at hudson.model.Build$BuildExecution.build(Build.java:206)
>>  at hudson.model.Build$BuildExecution.doRun(Build.java:163)
>>  at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
>>  at hudson.model.Run.execute(Run.java:1798)
>>  at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
>>  at