Re: Looking for Jenkins stories to turn into case studies

[Rick]

count me pls

On Thu, Jan 9, 2020 at 7:10 AM Alyssa Tong  wrote:

> sweet! thank you Marky. I'll introduce you to Jeanne who will take it from
> here. Standby.
>
> On Wed, Jan 8, 2020 at 3:04 PM Marky Jackson 
> wrote:
>
>> Count me in Alyssa!
>>
>> On Jan 8, 2020, at 3:03 PM, Alyssa Tong  wrote:
>>
>> Hi All,
>>
>> Happy new year!
>>
>> There are so many people (companies) doing great things with Jenkins but
>> we are not really capturing this. I am looking for compelling Jenkins
>> stories to turn into case studies to highlight the wonderful things our
>> community is doing with Jenkins.
>>
>> If you are interested in sharing your stories please reach out to me.
>>
>> The process looks like this: 1 hr interview with the case study
>> writer(s), they will go away to write up the content, there may be follow
>> up emails for clarification. Once they are done with the write up you
>> review and approve the content.
>> The turnaround time is about 30 days but the intent is to not take up too
>> much of your time. Pls let me know if you are interested.
>>
>> Thnx,
>> alyssa
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAC9wNawsGsBf3LuH8cZvpvv%3Dai4tpt2F%2BXdJqZEsPtMJbJSO7g%40mail.gmail.com
>> 
>> .
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/972E92C9-AA57-42AE-849E-94DE4ED54715%40gmail.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/CAMBsfbv25WDJ5r0sUsMSg3HgOK0CZedHXa4rWuEhcTmf0rJyqw%40mail.gmail.com
> 
> .
>


-- 
Zhao Xiaojie (Rick)
Blog: https://github.com/LinuxSuRen
Twitter: https://twitter.com/suren69811254

-- 
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/CAMM7nTGDFhRETxHKJeg_yBSja%3D_ms8EEuBzPANhTMwbLu6QKdg%40mail.gmail.com.

Is it possible to log ENV for all pipelines?

[Daniel Schmidt]

Hi folks,

Many of our Declarative Pipeline jobs start off by printing environment 
variables, which aids in debugging (should that be necessary). In other 
words, the first stage of every job includes this step:
sh "env | sort"

Is it possible to hook this into all pipelines automatically, e.g. with a 
"pipeline decorator" or metaprogramming? Alternatively, is there a better 
solution for inspecting the ENV of builds which have already completed?

-- 
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/b5e83af4-9584-4849-8730-85b0bd2191b7%40googlegroups.com.

Re: Looking for Jenkins stories to turn into case studies

[Alyssa Tong]

sweet! thank you Marky. I'll introduce you to Jeanne who will take it from
here. Standby.

On Wed, Jan 8, 2020 at 3:04 PM Marky Jackson 
wrote:

> Count me in Alyssa!
>
> On Jan 8, 2020, at 3:03 PM, Alyssa Tong  wrote:
>
> Hi All,
>
> Happy new year!
>
> There are so many people (companies) doing great things with Jenkins but
> we are not really capturing this. I am looking for compelling Jenkins
> stories to turn into case studies to highlight the wonderful things our
> community is doing with Jenkins.
>
> If you are interested in sharing your stories please reach out to me.
>
> The process looks like this: 1 hr interview with the case study writer(s),
> they will go away to write up the content, there may be follow up emails
> for clarification. Once they are done with the write up you review and
> approve the content.
> The turnaround time is about 30 days but the intent is to not take up too
> much of your time. Pls let me know if you are interested.
>
> Thnx,
> alyssa
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAC9wNawsGsBf3LuH8cZvpvv%3Dai4tpt2F%2BXdJqZEsPtMJbJSO7g%40mail.gmail.com
> 
> .
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/972E92C9-AA57-42AE-849E-94DE4ED54715%40gmail.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/CAMBsfbv25WDJ5r0sUsMSg3HgOK0CZedHXa4rWuEhcTmf0rJyqw%40mail.gmail.com.

Re: Looking for Jenkins stories to turn into case studies

[Marky Jackson]

Count me in Alyssa!

> On Jan 8, 2020, at 3:03 PM, Alyssa Tong  wrote:
> 
> Hi All,
> 
> Happy new year!
> 
> There are so many people (companies) doing great things with Jenkins but we 
> are not really capturing this. I am looking for compelling Jenkins stories to 
> turn into case studies to highlight the wonderful things our community is 
> doing with Jenkins.
> 
> If you are interested in sharing your stories please reach out to me. 
> 
> The process looks like this: 1 hr interview with the case study writer(s), 
> they will go away to write up the content, there may be follow up emails for 
> clarification. Once they are done with the write up you review and approve 
> the content. 
> The turnaround time is about 30 days but the intent is to not take up too 
> much of your time. Pls let me know if you are interested.
> 
> Thnx,
> alyssa
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-dev+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAC9wNawsGsBf3LuH8cZvpvv%3Dai4tpt2F%2BXdJqZEsPtMJbJSO7g%40mail.gmail.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/972E92C9-AA57-42AE-849E-94DE4ED54715%40gmail.com.

Looking for Jenkins stories to turn into case studies

[Alyssa Tong]

Hi All,

Happy new year!

There are so many people (companies) doing great things with Jenkins but we
are not really capturing this. I am looking for compelling Jenkins stories
to turn into case studies to highlight the wonderful things our community
is doing with Jenkins.

If you are interested in sharing your stories please reach out to me.

The process looks like this: 1 hr interview with the case study writer(s),
they will go away to write up the content, there may be follow up emails
for clarification. Once they are done with the write up you review and
approve the content.
The turnaround time is about 30 days but the intent is to not take up too
much of your time. Pls let me know if you are interested.

Thnx,
alyssa

-- 
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/CAC9wNawsGsBf3LuH8cZvpvv%3Dai4tpt2F%2BXdJqZEsPtMJbJSO7g%40mail.gmail.com.

[ec2-fleet] java.util.concurrent.CancellationException

[Alan Sparks]

I'm using the current (1.17.1) of the ec2-fleet plugin.  I've configured the 
plugin to use an autoscaling group.  It generally works OK, except occasionally 
for unknown reasons it launches extra builder instances, wasting money.

When I see the issue happen, it logs the following to the Jenkins log.  Does 
anyone know what this exception is telling me, why it would be happening?

Thanks in advance for any hints or suggestions.
-Alan


2020-01-08 19:51:07.553+ [id=39]SEVERE  
hudson.slaves.NodeProvisioner#lambda$update$6: Unexpected uncaught exception 
encountered while processing agent FleetNode-0
java.util.concurrent.CancellationException: Task was cancelled.
at 
com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:295)
at 
com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:276)
at 
com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:111)
at 
hudson.slaves.NodeProvisioner.lambda$update$6(NodeProvisioner.java:236)
at hudson.model.Queue._withLock(Queue.java:1392)
at hudson.model.Queue.withLock(Queue.java:1269)
at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:223)
at hudson.slaves.NodeProvisioner.access$900(NodeProvisioner.java:63)
at 
hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:817)
at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:70)
at 
jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
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)
2020-01-08 19:51:07.554+ [id=39]INFO
c.a.j.e.NoDelayProvisionStrategy#apply: currentDemand 1 availableCapacity 0 
(availableExecutors 0 connectingExecutors 0 plannedCapacitySnapshot 0 
additionalPlannedCapacity 0)


-- 
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/SN1PR18MB2141C2BAFEBBC6BD91149758C53E0%40SN1PR18MB2141.namprd18.prod.outlook.com.

Agent fails - windows agent service is restarting - SIGINT to 3460 failed - Killing as fallback

[zakyn]

Hello,

I would like to ask you for a help.

We have a problem, that windows service of all agents/nodes are crashing 
and reconneting again. The longest time is 12 hours sometimes less.
In the windows event log there is - SIGINT to 3460 failed - Killing as 
fallback - message.

I tried all the things I found on google but still without any success.
I tried run agents just from cmd and the behavior is the same.

Could you please help me?

Thank you.

Vladimir



*jenkins-slave-err.log*

Jan 08, 2020 2:03:46 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Terminated
Jan 08, 2020 2:03:56 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Performing onReconnect operation.
Jan 08, 2020 2:03:56 PM 
jenkins.slaves.restarter.JnlpSlaveRestarterInstaller$FindEffectiveRestarters$1 
onReconnect
INFO: Restarting agent via 
jenkins.slaves.restarter.WinswSlaveRestarter@27f599
Jan 08, 2020 2:03:58 PM hudson.remoting.jnlp.Main createEngine
INFO: Setting up agent: MYAGENT
Jan 08, 2020 2:03:58 PM hudson.remoting.jnlp.Main$CuiListener 
INFO: Jenkins agent is running in headless mode.
Jan 08, 2020 2:03:58 PM hudson.remoting.Engine startEngine
INFO: Using Remoting version: 3.36
Jan 08, 2020 2:03:58 PM org.jenkinsci.remoting.engine.WorkDirManager 
initializeWorkDir
INFO: Using c:\_js\remoting as a remoting work directory
Jan 08, 2020 2:03:58 PM org.jenkinsci.remoting.engine.WorkDirManager 
setupLogging
INFO: Both error and output logs will be printed to c:\_js\remoting
Jan 08, 2020 2:03:59 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Locating server among [http://MYADDRESS/]
Jan 08, 2020 2:03:59 PM 
org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]
Jan 08, 2020 2:03:59 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Agent discovery successful
  Agent address: MYADDRESS
  Agent port:49187
  Identity:  3e:36:96:ce:df:53:9a:86:71:99:48:31:27:de:bd:87
Jan 08, 2020 2:03:59 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Handshaking
Jan 08, 2020 2:03:59 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to MYADDRESS:49187
Jan 08, 2020 2:03:59 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Trying protocol: JNLP4-connect
Jan 08, 2020 2:03:59 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Remote identity confirmed: 
3e:36:96:ce:df:53:9a:86:71:99:48:31:27:de:bd:87
Jan 08, 2020 2:04:00 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connected

*wrapper.log*
2020-01-08 10:08:38,702 INFO  - Stopping jenkinsslave-c___js
2020-01-08 10:08:38,703 DEBUG - ProcessKill 2512
2020-01-08 10:08:38,825 INFO  - Found child process: 7408 Name: conhost.exe
2020-01-08 10:08:38,908 INFO  - Stopping process 7408
2020-01-08 10:08:38,911 INFO  - Send SIGINT 7408
2020-01-08 10:08:38,912 WARN  - SIGINT to 7408 failed - Killing as fallback
2020-01-08 10:08:38,914 INFO  - Stopping process 2512
2020-01-08 10:08:38,918 INFO  - Send SIGINT 2512
2020-01-08 10:08:38,919 WARN  - SIGINT to 2512 failed - Killing as fallback
2020-01-08 10:08:38,921 INFO  - Finished jenkinsslave-c___js
2020-01-08 10:08:38,923 DEBUG - Completed. Exit code is 0
2020-01-08 10:08:42,687 INFO  - Starting ServiceWrapper in the service mode
2020-01-08 10:08:42,709 INFO  - Starting C:\Program Files 
(x86)\Java\jre1.8.0\bin\java.exe -Xrs  -jar "c:\_js\slave.jar" -jnlpUrl 
http://MYAGENT/slave-agent.jnlp -secret 
75ef2485eebc894178cbfa9cecd0501cfffb49d4fcb6a240e6
2020-01-08 10:08:42,716 INFO  - Extension loaded: killOnStartup
2020-01-08 10:08:42,720 DEBUG - Checking the potentially runaway process 
with PID=2512
2020-01-08 10:08:42,727 DEBUG - No runaway process with PID=2512. The 
process has been already stopped.
2020-01-08 10:08:42,754 INFO  - Started process 2724
2020-01-08 10:08:42,758 DEBUG - Forwarding logs of the process 
System.Diagnostics.Process (java) to winsw.SizeBasedRollingLogAppender
2020-01-08 10:08:42,761 INFO  - Recording PID of the started process:2724. 
PID file destination is c:\_js\jenkins_agent.pid
2020-01-08 10:08:47,081 DEBUG - Starting ServiceWrapper in the CLI mode
2020-01-08 10:08:47,312 DEBUG - User requested the status of the process 
with id 'jenkinsslave-c___js'
2020-01-08 10:08:47,317 DEBUG - Completed. Exit code is 0
2020-01-08 14:03:56,264 DEBUG - Starting ServiceWrapper in the CLI mode
2020-01-08 14:03:56,457 INFO  - Restarting the service with id 
'jenkinsslave-c___js'
2020-01-08 14:03:56,464 DEBUG - Completed. Exit code is 0
2020-01-08 14:03:56,556 DEBUG - Starting ServiceWrapper in the CLI mode
2020-01-08 14:03:56,760 INFO  - Restarting the service with id 
'jenkinsslave-c___js'
2020-01-08 14:03:56,787 INFO  - Stopping jenkinsslave-c___js
2020-01-08 14:03:56,787 DEBUG - ProcessKill 2724
2020-01-08 14:03:56,908 INFO  - Found child process: 3460 Name: conhost.exe
2020-01-08 14:03:56,987 INFO  - Stopping process 3460
2020-01-08 14:03:56,991 INFO  - Send SIGINT 3460
2020-01-08 14:03:56,994 WARN  - SIGINT