[JIRA] (JENKINS-59776) workflow-basic-steps-plugin "waitUntil" should have a quiet mode
Title: Message Title Kevin Puetz commented on JENKINS-59776 Re: workflow-basic-steps-plugin "waitUntil" should have a quiet mode Just to update the status here: https://github.com/jenkinsci/workflow-basic-steps-plugin/pull/100 is now merged (not by me, I just got notified by github and see the status isn't updated here) Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202500.1571053928000.5747.1583947560254%40Atlassian.JIRA.
[JIRA] (JENKINS-59267) Timeout exceptions in jenkins log when jenkins-cli executes a long-running command
Title: Message Title Kevin Puetz commented on JENKINS-59267 Re: Timeout exceptions in jenkins log when jenkins-cli executes a long-running command Looks good to me, I see the 3s pings in -logger FINE and I no longer seem timeouts using default settings. Obviously I can still provoke a timeout if I set Jenkins shorter (e.g. 1s), without adjusting jenkins-cli accordingly, but that's to be expected and the defaults now seem to be well-behaved. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201766.1567817431000.4131.1570680540140%40Atlassian.JIRA.
[JIRA] (JENKINS-59267) Timeout exceptions in jenkins log when jenkins-cli executes a long-running command
Title: Message Title Kevin Puetz updated an issue Jenkins / JENKINS-59267 Timeout exceptions in jenkins log when jenkins-cli executes a long-running command Change By: Kevin Puetz Whenever a long-running command is run via {{ jenkins-cli -s [ http://localhost:8080 |http: / /localhost:8080/] -auth ... }} , the jenkins.log will show a timeout error, and echo back all the bytes of the input command as well. e.g. {noformat}$ echo 'println "hello"; sleep 6000; println "world"' | jenkins-cli - s http://localhost:8080/ - auth ... groovy = {noformat}will log a message like{noformat}2019-09-07 00:26:20.912+ [id=201] WARNING h.c.PlainCLIProtocol$EitherSide$Reader#runAlso: java.lang.Throwable: HttpInput failureat org.eclipse.jetty.server.HttpInput.failed(HttpInput.java:831)at org.eclipse.jetty.server.HttpConnection$BlockingReadCallback.failed(HttpConnection.java:661)at org.eclipse.jetty.io.FillInterest.onFail(FillInterest.java:138)at org.eclipse.jetty.io.AbstractEndPoint.onIdleExpired(AbstractEndPoint.java:406)java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 msat org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:166)at org.eclipse.jetty.io.IdleTimeout$1.run(IdleTimeout.java:50)at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)at java.util.concurrent.FutureTask.run(FutureTask.java:266)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)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.IOExceptionat org.eclipse.jetty.server.HttpInput$ErrorState.noContent(HttpInput.java:1085)at org.eclipse.jetty.server.HttpInput.read(HttpInput.java:318)at org.eclipse.jetty.server.HttpInput.read(HttpInput.java:256)at org.apache.commons.io.input.ProxyInputStream.read(ProxyInputStream.java:59)at hudson.cli.FlightRecorderInputStream.read(FlightRecorderInputStream.java:88)at java.io.DataInputStream.readInt(DataInputStream.java:387)at hudson.cli.PlainCLIProtocol$EitherSide$Reader.run(PlainCLIProtocol.java:110)Caused: hudson.cli.DiagnosedStreamCorruptionExceptionRead back: 0x00 0x00 0x00 0x08 0x00 0x00 0x06 'groovy' 0x00 0x00 0x00 0x03 0x00 0x00 0x01 '=' 0x00 0x00 0x00 0x07 0x02 0x00 0x05 'UTF-8' 0x00 0x00 0x00 0x07 0x01 0x00 0x05 'en_US' 0x00 0x00 0x00 0x00 0x03 0x00 0x00 0x00 0x01 0x05 'p' 0x00 0x00 0x00 0x01 0x05 'r' 0x00 0x00 0x00 0x01 0x05 'i' 0x00 0x00 0x00 0x01 0x05 'n' 0x00 0x00 0x00 0x01 0x05 't' 0x00 0x00 0x00 0x01 0x05 'l' 0x00 0x00 0x00 0x01 0x05 'n' 0x00 0x00 0x00 0x01 0x05 ' ' 0x00 0x00 0x00 0x01 0x05 '"' 0
[JIRA] (JENKINS-59267) Timeout exceptions in jenkins log when jenkins-cli executes a long-running command
Title: Message Title Kevin Puetz created an issue Jenkins / JENKINS-59267 Timeout exceptions in jenkins log when jenkins-cli executes a long-running command Issue Type: Bug Assignee: Unassigned Components: cli Created: 2019-09-07 00:50 Environment: Jenkins 2.193, installed from https://pkg.jenkins.io/debian Ubuntu 16.04 amd64 openjdk version "1.8.0_222" OpenJDK Runtime Environment (build 1.8.0_222-8u222-b10-1ubuntu1~16.04.1-b10) OpenJDK 64-Bit Server VM (build 25.222-b10, mixed mode) Jenkins is self-hosting in Jetty: /usr/bin/java -Djava.awt.headless=true -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 Priority: Minor Reporter: Kevin Puetz Whenever a long-running command is run via jenkins-cli -s http://localhost:8080 -auth ..., the jenkins.log will show a timeout error, and echo back all the bytes of the input command as well. e.g. $ echo 'println "hello"; sleep 6000; println "world"' | jenkins-cli -auth ... groovy = will log a message like 2019-09-07 00:26:20.912+ [id=201] WARNING h.c.PlainCLIProtocol$EitherSide$Reader#run Also: java.lang.Throwable: HttpInput failure at org.eclipse.jetty.server.HttpInput.failed(HttpInput.java:831) at org.eclipse.jetty.server.HttpConnection$BlockingReadCallback.failed(Ht
[JIRA] (JENKINS-28035) Space delimiter is not supported
Title: Message Title Kevin Puetz commented on JENKINS-28035 Re: Space delimiter is not supported newlines don't work either, probably the same cause. Maybe it's related to XML whitespace normalization (which generally trims leading/trailing whitespace, etc) while reading the tag? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.