[JIRA] (JENKINS-62068) jetty ALPN incompatibility - java8 u 252
Title: Message Title Josh Soref updated JENKINS-62068 Jenkins / JENKINS-62068 jetty ALPN incompatibility - java8 u 252 Change By: Josh Soref Status: Fixed but Unreleased Closed 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.205967.1588006254000.18566.1588013100271%40Atlassian.JIRA.
[JIRA] (JENKINS-62068) jetty ALPN incompatibility - java8 u 252
Title: Message Title Josh Soref updated JENKINS-62068 ok, this isn't a jenkins bug. The ALPN APIs have been backported from Java 9 to OpenJDK 8u251/8u252. Therefore, since OpenJDK 8u251/8u252 there is no more need for the Jetty ALPN boot jar provided by this project. https://github.com/jetty-project/jetty-alpn#jetty-alpn What happened was: Start-Date: 2020-04-20 15:30:27 Commandline: apt upgrade Upgrade: jenkins:amd64 (2.232, 2.233) End-Date: 2020-04-20 15:30:31Start-Date: 2020-04-22 13:58:10 Commandline: apt upgrade Upgrade: ... openjdk-8-jre:amd64 (8u242-b08-0ubuntu3~18.04, 8u252-b09-1~18 .04), ... End-Date: 2020-04-22 13:58:32 Start-Date: 2020-04-27 12:14:55 Commandline: apt upgrade Requested-By: jsoref (1005) Upgrade: ..., jenkins:amd64 (2.233, 2.234), ... End-Date: 2020-04-27 12:15:15 So, I had updated to jenkins 2.233 – and things were fine. Then java updated to 8u252 (which is incompatible w/ the jetty alpn, as it integrated it), but jenkins the service wasn't restarted. Then I upgraded to jenkins 2.234 – and things exploded. But, the problem wasn't jenkins, it's just that I hadn't restarted it since the java upgrade, which is why downgrading didn't fix the problem. Solution: remove ALPN from the path, as it's no longer needed. Jenkins / JENKINS-62068 jetty ALPN incompatibility - java8 u 252 Change By: Josh Soref Status: Open Fixed but Unreleased Resolution: Not A Defect
[JIRA] (JENKINS-62068) jetty ALPN incompatibility - java8 u 252
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-62068 jetty ALPN incompatibility - java8 u 252 Change By: Josh Soref Summary: jetty ALPN incompatibility - java.lang.NoSuchFieldError: nullSession at sun.security.ssl.ClientHandshaker.getKickstartMessage java8 u 252 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.205967.1588006254000.18512.1588011360300%40Atlassian.JIRA.
[JIRA] (JENKINS-62068) ALPN incompatibility - java.lang.NoSuchFieldError: nullSession at sun.security.ssl.ClientHandshaker.getKickstartMessage
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-62068 ALPN incompatibility - java.lang.NoSuchFieldError: nullSession at sun.security.ssl.ClientHandshaker.getKickstartMessage Change By: Josh Soref Summary: ALPN incompatibility - java.lang.NoSuchFieldError: nullSession at sun.security.ssl.ClientHandshaker.getKickstartMessage 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.205967.1588006254000.18508.1588011060152%40Atlassian.JIRA.
[JIRA] (JENKINS-62068) java.lang.NoSuchFieldError: nullSession at sun.security.ssl.ClientHandshaker.getKickstartMessage
Title: Message Title Josh Soref commented on JENKINS-62068 Re: java.lang.NoSuchFieldError: nullSession at sun.security.ssl.ClientHandshaker.getKickstartMessage Ok. https://github.com/jetty-project/jetty-alpn/issues/30 it's ALPN (again). 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.205967.1588006254000.18505.1588011000723%40Atlassian.JIRA.
[JIRA] (JENKINS-62068) java.lang.NoSuchFieldError: nullSession at sun.security.ssl.ClientHandshaker.getKickstartMessage
Title: Message Title Josh Soref commented on JENKINS-62068 Re: java.lang.NoSuchFieldError: nullSession at sun.security.ssl.ClientHandshaker.getKickstartMessage Oleg Nenashev: See the second case where it's just the update server check. It feels like something screwy happened to the general SSL stack. Note: rolling back to 2.233 didn't fix this . # ok to this point Start-Date: 2020-04-27 12:14:55 Commandline: apt upgrade Requested-By: jsoref (1005) Upgrade: libcups2:amd64 (2.2.7-1ubuntu2.7, 2.2.7-1ubuntu2.8), update-manager-core:amd64 (1:18.04.11.10, 1:18.04.11.12), zabbix-agent:amd64 (1:4.0.19-1+buster, 1:4.0.20-1+buster), jenkins:amd64 (2.2 33, 2.234), libkmod2:amd64 (24-1ubuntu3.2, 24-1ubuntu3.3), kmod:amd64 (24-1ubuntu3.2, 24-1ubuntu3.3), python3-update-manager:amd64 (1:18.04.11.10, 1:18.04.11.12), distro-info-data:amd64 (0.37ubuntu 0.6, 0.37ubuntu0.7), zabbix-proxy-sqlite3:amd64 (1:4.0.19-1+buster, 1:4.0.20-1+buster) End-Date: 2020-04-27 12:15:15 # broken at this point Start-Date: 2020-04-27 12:48:13 Commandline: apt install jenkins=2.233 Requested-By: jsoref (1005) Downgrade: jenkins:amd64 (2.234, 2.233) End-Date: 2020-04-27 12:48:16 # not fixed at this point 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"
[JIRA] (JENKINS-62068) java.lang.NoSuchFieldError: nullSession at sun.security.ssl.ClientHandshaker.getKickstartMessage
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-62068 java.lang.NoSuchFieldError: nullSession at sun.security.ssl.ClientHandshaker.getKickstartMessage Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-04-27 16:50 Priority: Minor Reporter: Josh Soref -- Logs begin at Thu 2018-11-01 01:50:46 EDT, end at Mon 2020-04-27 12:35:24 EDT. -- Apr 27 12:34:00 hostname jenkins[22240]: 2020-04-27 16:34:00.042+ [id=193]SEVEREh.triggers.SCMTrigger$Runner#runPolling: Failed to record SCM polling for hudson.model.FreeStyleProject@21c303b6[SomePrject] Apr 27 12:34:00 hostname jenkins[22240]: java.lang.NoSuchFieldError: nullSession Apr 27 12:34:00 hostname jenkins[22240]: at sun.security.ssl.ClientHandshaker.getKickstartMessage(ClientHandshaker.java:1350) Apr 27 12:34:00 hostname jenkins[22240]: at sun.security.ssl.Handshaker.kickstart(Handshaker.java:1117) Apr 27 12:34:00 hostname jenkins[22240]: at sun.security.ssl.SSLSocketImpl.kickstartHandshake(SSLSocketImpl.java:1500) Apr 27 12:34:00 hostname jenkins[22240]: at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1367) Apr 27 12:34:00 hostname jenkins[22240]: at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1416) Apr 27 12:34:00 hostname jenkins[22240]: at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1400) Apr 27 12:34:00 hostname jenkins[22240]: at org.tmatesoft.svn.core.internal.util.SVNSocketFactory.createSSLSocket(SVNSocketFactory.java:96) Apr 27 12:34:00 hostname jenkins[22240]: at ... ... Apr 27 12:34:10 hostname jenkins[22240]: 2020-04-27 16:34:10.783+ [id=45]INFOhudson.util.Retrier#start: Attempt #1 to do the action check updates server Apr 27
[JIRA] (JENKINS-61696) Replace "top page"
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-61696 Replace "top page" Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-03-26 15:08 Priority: Minor Reporter: Josh Soref I installed some plugins using the plugin manager, which eventually took me to: http://jenkins.example.com/updateCenter/ Installing Plugins/Upgrades Go back to the top page (you can start using the installed plugins right away) I don't think "top page" is a term Jenkins generally uses. Add Comment
[JIRA] (JENKINS-61595) checkApiToken - NullPointerException
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-61595 checkApiToken - NullPointerException Issue Type: Bug Assignee: Anatoliy Varanitsa Components: ecs-publisher-plugin Created: 2020-03-19 23:52 Priority: Minor Reporter: Josh Soref 2020-03-19 23:21:40.400+ [id=25]WARNING o.e.j.s.h.ContextHandler$Context#log: Error while serving http://localhost:9000/descriptorByName/de.eacg.ecs.publisher.PublisherCredentials/checkApiToken java.lang.NullPointerException at de.eacg.ecs.publisher.PublisherCredentials$DescriptorImpl.doCheckApiToken(PublisherCredentials.java:156) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:485) ... 2020-03-19 23:21:40.402+ [id=25]WARNING h.i.i.InstallUncaughtExceptionHandler#handleException: Caught unhandled exception with ID 52f18e9c-a099-4612-a49f-a2fc2c840d53 java.lang.NullPointerException at de.eacg.ecs.publisher.PublisherCredentials$DescriptorImpl.doCheckApiToken(PublisherCredentials.java:156) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:485) Caused: javax.servlet.ServletException 23:21:44.473+ [id=27]WARNING o.e.j.s.h.ContextHandler$Context#log: Error while serving http://localhost:9000/descriptorByName/de.eacg.ecs.publisher.PublisherCredentials/checkApiToken java.lang.NullPointerException at de.eacg.ecs.publisher.PublisherCredentials$DescriptorImpl.doCheckApiToken(PublisherCredentials.java:156) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:485) Caused: java.lang.reflect.InvocationTargetException 2020-03-19 23:21:44.474+ [id=27]WARNING h.i.i.InstallUncaughtExceptionHandler#handleException: Caught unhandled exception with ID d3c40adc-b883-436e-b05f-bea8f26e4204 java.lang.NullPointerException
[JIRA] (JENKINS-61519) Odd rendering of Monitoring of Jenkins master plugin in Manage Jenkins screen
Title: Message Title Josh Soref commented on JENKINS-61519 Re: Odd rendering of Monitoring of Jenkins master plugin in Manage Jenkins screen Oops, I guess it just wasn't as noticably bad without a sibling. 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.205215.1584580258000.9293.1584589860176%40Atlassian.JIRA.
[JIRA] (JENKINS-61519) Odd rendering of Monitoring of Jenkins master plugin in new Manage Jenkins screen
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-61519 Odd rendering of Monitoring of Jenkins master plugin in new Manage Jenkins screen Issue Type: Bug Assignee: evernat Attachments: image-2020-03-18-21-06-23-144.png Components: core, monitoring-plugin Created: 2020-03-19 01:10 Priority: Minor Reporter: Josh Soref Jenkins ver. 2.226 Support Core Plugin 2.67 GitHub plugin 1.29.5 Monitoring 1.82.0 Add Comment
[JIRA] (JENKINS-61518) update notice odd spacing before closing parenthesis
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-61518 update notice odd spacing before closing parenthesis Issue Type: Bug Assignee: Unassigned Attachments: image-2020-03-18-20-51-32-428.png Components: core Created: 2020-03-19 00:53 Priority: Minor Reporter: Josh Soref New version of Jenkins (2.226) is available for download (changelog). [Manage Jenkins] Add Comment
[JIRA] (JENKINS-61441) Move alert buttons below warnings
Title: Message Title Josh Soref assigned an issue to Josh Soref Jenkins / JENKINS-61441 Move alert buttons below warnings Change By: Josh Soref Assignee: Josh Soref 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.205119.158395120.5891.1583966580056%40Atlassian.JIRA.
[JIRA] (JENKINS-61445) Broken plugin description
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-61445 Broken plugin description Issue Type: Bug Assignee: Brad Kimmel Attachments: image-2020-03-11-18-28-10-820.png Components: google-cloudbuild-plugin Created: 2020-03-11 22:28 Priority: Minor Reporter: Josh Soref Add Comment
[JIRA] (JENKINS-61444) GitHub should be spelled as such
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-61444 GitHub should be spelled as such Issue Type: Bug Assignee: Steven Foster Attachments: image-2020-03-11-18-20-01-368.png Components: github-scm-trait-notification-context-plugin Created: 2020-03-11 22:20 Priority: Minor Reporter: Josh Soref Add Comment
[JIRA] (JENKINS-61443) Plugin description renders poorly
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-61443 Plugin description renders poorly Issue Type: Bug Assignee: Phuong Huynh Attachments: image-2020-03-11-18-12-59-780.png Components: aws-codecommit-trigger-plugin Created: 2020-03-11 22:14 Priority: Minor Reporter: Josh Soref The code in question assumes that https://github.com/jenkinsci/aws-codecommit-jobs-plugin/edit/develop/src/main/resources/index.jelly renders with distinct lines: foo bar It does not: Add Comment
[JIRA] (JENKINS-61441) Move alert buttons below warnings
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-61441 Move alert buttons below warnings Issue Type: Improvement Assignee: Unassigned Attachments: image-2020-03-11-14-24-44-740.png Components: core Created: 2020-03-11 18:26 Priority: Minor Reporter: Josh Soref Currently: Preferred: New version ... available Warnings have been published... Plugins... Go to plugin manager | Configure which of these warnings are shown
[JIRA] (JENKINS-61019) java.lang.NullPointerException at org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution.cancel
Title: Message Title Josh Soref assigned an issue to Josh Soref Jenkins / JENKINS-61019 java.lang.NullPointerException at org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution.cancel Change By: Josh Soref Assignee: Josh Soref 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.204490.1581107937000.4581.1581109560071%40Atlassian.JIRA.
[JIRA] (JENKINS-61019) java.lang.NullPointerException at org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution.cancel
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-61019 java.lang.NullPointerException at org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution.cancel Issue Type: Bug Assignee: Unassigned Components: workflow-basic-steps-plugin Created: 2020-02-07 20:38 Priority: Minor Reporter: Josh Soref Feb 07, 2020 3:35:37 PM org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl$1 onFailureFeb 07, 2020 3:35:37 PM org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl$1 onFailureWARNING: Failed to load CpsFlowExecution[Owner[retry-timeout/7:retry-timeout #7]]java.lang.NullPointerException at org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution.cancel(TimeoutStepExecution.java:154) at org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution.setupTimer(TimeoutStepExecution.java:142) at org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution.onResume(TimeoutStepExecution.java:93) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl$1.onSuccess(FlowExecutionList.java:185) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl$1.onSuccess(FlowExecutionList.java:180) at com.google.common.util.concurrent.Futures$6.run(Futures.java:975) at com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:253) at com.google.common.util.concurrent.ExecutionList$RunnableExecutorPair.execute(ExecutionList.java:149) at com.google.common.util.concurrent.ExecutionList.execute(ExecutionList.java:134) at com.google.common.util.concurrent.AbstractFuture.set(AbstractFuture.java:170) at com.google.common.util.concurrent.SettableFuture.set(SettableFuture.java:53) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$5.onSuccess(CpsFlowExecution.java:1011) at
[JIRA] (JENKINS-59839) java.lang.NullPointerException at hudson.util.Secret$1.convert
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-59839 java.lang.NullPointerException at hudson.util.Secret$1.convert Change By: Josh Soref Summary: java.lang.NullPointerException at hudson.util.Secret$1.convert 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.202574.1571388185000.4575.1581107940242%40Atlassian.JIRA.
[JIRA] (JENKINS-61007) pipeline-model-definition is using findbugs without providing / depending on it
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-61007 pipeline-model-definition is using findbugs without providing / depending on it Issue Type: Bug Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2020-02-06 23:45 Priority: Minor Reporter: Josh Soref I'm using hpi:run from the workflow-basic-steps-plugin. I bumped the 2.150.3 because the Credentials Plugin objects to 2.150.1. Expected results: I should be able to test a pipeline. Actual results: Started by user Admin Running in Durability level: MAX_SURVIVABILITY [Pipeline] Start of Pipeline [Pipeline] End of Pipeline hudson.remoting.ProxyException: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: jar:file:~/code/jenkinsci/workflow-basic-steps-plugin/work/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy: 29: unable to resolve class edu.umd.cs.findbugs.annotations.SuppressFBWarnings @ line 29, column 1. import edu.umd.cs.findbugs.annotations.SuppressFBWarnings ^ Steps: mvn hpi:run Load http://localhost:8080/jenkins/pluginManager/available Select Pipeline Click Download now and install after restart Restart the mvn hpi:run command
[JIRA] (JENKINS-61004) Provide css to limit build history rows
Title: Message Title Josh Soref assigned an issue to Josh Soref Jenkins / JENKINS-61004 Provide css to limit build history rows Change By: Josh Soref Assignee: Josh Soref 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.204474.158101961.3036.1581025140062%40Atlassian.JIRA.
[JIRA] (JENKINS-61004) Provide css to limit build history rows
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-61004 Provide css to limit build history rows Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-02-06 20:06 Priority: Minor Reporter: Josh Soref https://github.com/jenkinsci/jenkins/pull/4209 removed a limit but the lack of a limit resulted in an explosion of content for people who insert lots of content into those fields. I'm proposing to set default limits. This also will make it easier for people to see what css they'll have to write if they don't like the limits. Add Comment
[JIRA] (JENKINS-60299) Make build description in build history widget configurable or possible to hide
Title: Message Title
Josh Soref commented on JENKINS-60299
Re: Make build description in build history widget configurable or possible to hide
You could use this:
td.build-row-cell > div > .build-link {
background-color: pink;
max-height: 3em;
overflow-y: hidden;
}
td.build-row-cell > div.desc {
background-color: yellow;
max-height: 5em;
overflow-y: hidden;
}
The coloring is included just to make it easy to identify the pieces. Personally, I think having some default css with some em based limits for both fields would be nice. I like including stack traces or similar in the second field, and the behavior we got wasn't particularly ideal.
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.203294.1574852635000.2987.1581017940211%40Atlassian.JIRA.
[JIRA] (JENKINS-60299) Make build description in build history widget configurable or possible to hide
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-60299 Make build description in build history widget configurable or possible to hide Change By: Josh Soref Attachment: image-2020-02-06-14-37-27-125.png 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.203294.1574852635000.2982.1581017880425%40Atlassian.JIRA.
[JIRA] (JENKINS-60927) Use disconnect icon for Disconnect and Delete Agent
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-60927 Use disconnect icon for Disconnect and Delete Agent Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-01-30 20:46 Priority: Minor Reporter: Josh Soref http://jenkins/computer/node/ Back to List Status Delete Agent ... Disconnect ... The icon itself is called "delete", which means that delete agent should win the fight for the icon, and disconnect should get a different icon. Add Comment This
[JIRA] (JENKINS-59486) Restart Jenkins when installation is complete and no jobs are running should preload the restarting jenkins image
Title: Message Title Josh Soref started work on JENKINS-59486 Change By: Josh Soref Status: Open In Progress 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.202101.1569248989000.3517.1579650720353%40Atlassian.JIRA.
[JIRA] (JENKINS-59486) Restart Jenkins when installation is complete and no jobs are running should preload the restarting jenkins image
Title: Message Title Josh Soref assigned an issue to Josh Soref Jenkins / JENKINS-59486 Restart Jenkins when installation is complete and no jobs are running should preload the restarting jenkins image Change By: Josh Soref Assignee: Josh Soref 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.202101.1569248989000.3516.1579650720233%40Atlassian.JIRA.
[JIRA] (JENKINS-60716) Loss of exception detail in LogRotator failures
Title: Message Title Josh Soref updated JENKINS-60716 Jenkins / JENKINS-60716 Loss of exception detail in LogRotator failures Change By: Josh Soref Status: Fixed but Unreleased Resolved 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.203964.1578599933000.3371.1579640100363%40Atlassian.JIRA.
[JIRA] (JENKINS-60577) computer/(master)/builds/rssLatest error 404 not found
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-60577 computer/(master)/builds/rssLatest error 404 not found Change By: Josh Soref Released As: 2.215 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.203700.1577144725000.3374.1579640100404%40Atlassian.JIRA.
[JIRA] (JENKINS-60577) computer/(master)/builds/rssLatest error 404 not found
Title: Message Title Josh Soref updated JENKINS-60577 Jenkins / JENKINS-60577 computer/(master)/builds/rssLatest error 404 not found Change By: Josh Soref Status: In Review Resolved Resolution: Fixed 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.203700.1577144725000.3368.1579640040346%40Atlassian.JIRA.
[JIRA] (JENKINS-57206) Support draft pull requests from GitHub
Title: Message Title Josh Soref commented on JENKINS-57206 Re: Support draft pull requests from GitHub Ebrahim Moshaya: that's JENKINS-54126 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.198963.1556379411000.3351.1579639440338%40Atlassian.JIRA.
[JIRA] (JENKINS-60495) Downstream multibranch pipeline does not receive parameters for initial build
Title: Message Title Josh Soref commented on JENKINS-60495 Re: Downstream multibranch pipeline does not receive parameters for initial build I suspect you're running into a problem relating to the fact that pipelines only seem to be willing to deliver parameters they know about to jobs. And since the first time a job runs, the system doesn't know about parameters, it can't deliver yours. As a workaround, I'd probably just adjust the pipeline to recognize the first-run case, declare its parameters, and stop (possibly w/ some magic code that enables the caller to check for it). You could then have the caller job recognize that case and trigger the job again. I haven't really looked into this much. We hit it – whenever we add a new value to a parameter, we can't use that value until we let the system build once normally. 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.203585.1576480822000.2378.1579500360361%40Atlassian.JIRA.
[JIRA] (JENKINS-48915) Build Executor Status should show "launching"
Title: Message Title Josh Soref updated JENKINS-48915 Someone fixed this at some point. Although I can't figure out where/how. Jenkins / JENKINS-48915 Build Executor Status should show "launching" Change By: Josh Soref Status: Open Fixed but Unreleased Resolution: Fixed 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
[JIRA] (JENKINS-60774) Parallel stages are painted outside the lines for stages that will never happen
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-60774 Parallel stages are painted outside the lines for stages that will never happen Issue Type: Bug Assignee: Unassigned Attachments: image-2020-01-14-17-35-59-021.png Components: blueocean-plugin Created: 2020-01-14 22:38 Priority: Minor Reporter: Josh Soref A parallel stage in the third stage of a five stage pipeline failed. It was painted red, and this caused the whole job to die. The fifth stage also has parallel stages, but they were skipped because the job died. Pipeline still painted the stage names, but didn't paint any of the cute little lines to get to the stages. Expected results: Don't list the substages for a stage that's skipped, or, failing that: draw a bunch of grayed lines for skipped substages in the same way that primary stages are skipped (e.g. Dependabot here)
[JIRA] (JENKINS-60718) Replace upload disclosure title with replace
Title: Message Title Josh Soref assigned an issue to Josh Soref Jenkins / JENKINS-60718 Replace upload disclosure title with replace Change By: Josh Soref Assignee: Josh Soref 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.203966.1578613274000.5993.1578613440056%40Atlassian.JIRA.
[JIRA] (JENKINS-60718) Replace upload disclosure title with replace
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-60718 Replace upload disclosure title with replace Issue Type: Improvement Assignee: Unassigned Attachments: image-2020-01-09-18-39-03-309.png, image-2020-01-09-18-39-57-282.png, image-2020-01-09-18-41-02-567.png Components: plain-credentials-plugin Created: 2020-01-09 23:41 Priority: Minor Reporter: Josh Soref Currently: One notable confusing thing is that it wasn't remotely apparent to me that credentials was the file name and not a generic message. Proposal: For comparison, here's the equivalent UI for a password: Add Comment
[JIRA] (JENKINS-60682) Improve scriptApproval ux
Title: Message Title Josh Soref assigned an issue to Josh Soref Jenkins / JENKINS-60682 Improve scriptApproval ux Change By: Josh Soref Assignee: Josh Soref 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.203926.1578432846000.5963.1578599640062%40Atlassian.JIRA.
[JIRA] (JENKINS-60682) Improve scriptApproval ux
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-60682 Improve scriptApproval ux Issue Type: Improvement Assignee: Unassigned Attachments: image-2020-01-07-16-33-07-031.png, image-2020-01-07-16-33-19-734.png Components: core Created: 2020-01-07 21:34 Priority: Minor Reporter: Josh Soref Current: Replacement: Add Comment
[JIRA] (JENKINS-60666) Stack overflow? with hudson.model.Computer$TerminationRequest
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-60666 Stack overflow? with hudson.model.Computer$TerminationRequest Issue Type: Bug Assignee: Unassigned Components: core, pipeline Created: 2020-01-06 23:24 Priority: Minor Reporter: Josh Soref Could not update commit status, please check if your scan credentials belong to a member of the organization or a collaborator of the repository and repo:status scope is selected GitHub has been notified of this commit’s build result Also: hudson.model.Computer$TerminationRequest: Termination requested at Tue Dec 24 00:20:08 EST 2019 by Thread[jenkins.util.Timer [#4],5,main] [id=44] at hudson.model.Computer.recordTermination(Computer.java:226) at hudson.model.Computer.disconnect(Computer.java:490) at hudson.slaves.SlaveComputer.disconnect(SlaveComputer.java:727) at hudson.slaves.RetentionStrategy$Demand.check(RetentionStrategy.java:269) at hudson.slaves.RetentionStrategy$Demand.check(RetentionStrategy.java:177) at hudson.slaves.ComputerRetentionWork$1.run(ComputerRetentionWork.java:70) at hudson.model.Queue._withLock(Queue.java:1392) at hudson.model.Queue.withLock(Queue.java:1269) at hudson.slaves.ComputerRetentionWork.doRun(ComputerRetentionWork.java:61) 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) Also:
[JIRA] (JENKINS-60659) Aborted task died
Title: Message Title
Josh Soref created an issue
Jenkins / JENKINS-60659
Aborted task died
Issue Type:
Bug
Assignee:
Unassigned
Components:
junit-plugin, pipeline
Created:
2020-01-06 21:38
Priority:
Minor
Reporter:
Josh Soref
We're running on Google Cloud Preemptive instances. I've configured a shutdown script in the metadata. I've configured the shutdown script to get a list of running jobs on the node and then asks the master to "Stop" them. This mostly works. But occasionally it fails. We have a pipeline (built using a library) which is somewhat akin to this:
pipeline {
agent {
label "katalon"
}
options {
timeout(time: 19, unit: 'MINUTES')
disableConcurrentBuilds()
}
triggers { cron('H/20 * * * *') }
stages {
stage("Run tests") {
steps {
script {
parallelTests("katalon/*.prj", ["apple", "lemon", "peach"], "katalon")
}
}
post {
regression {
script {
if (currentBuild.rawBuild.getActions(jenkins.model.InterruptedBuildAction.class).isEmpty()) {
echo "regression"
}
}
}
fixed {
echo "recovered"
}
}
}
}
}
}
def parallelTests(projectPath, profiles, agentLabel) {
tests = profiles.collectEntries { profile ->
["${profile}": test(projectPath, profile, agentLabel)]
}
parallel tests
}
def test(projectPath, profile, agentLabel) {
katalonPath = "/opt/katalon-studio/katalon"
return {
[JIRA] (JENKINS-60635) Build periodically help should offer timezones as a pop out
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-60635 Build periodically help should offer timezones as a pop out Issue Type: New Feature Assignee: Unassigned Components: core Created: 2020-01-03 20:38 Priority: Minor Reporter: Josh Soref Go to a classic job and check Build periodically. Then click the next to the schedule. You'll get an incredibly long box: Time zone specification Periodic tasks are normally executed at the scheduled time in the time zone of the Jenkins master JVM (currently America/Toronto). This behavior can optionally be changed by specifying an alternative time zone in the first line of the field. Time zone specification starts with TZ=, followed by the ID of a time zone.Complete example of a schedule with a time zone specification:TZ=Europe/London # This job needs to be run in the morning, London time H 8 * * * # Butlers do not have a five o'clock, so we run the job again H(0-30) 17 * * * The supported time zones depend on the Java runtime Jenkins is running on. The list of supported time zone IDs on this instance is: Africa/Abidjan Africa/Accra Africa/Addis_Ababa Africa/Algiers Africa/Asmara Africa/Asmera Africa/Bamako Africa/Bangui Africa/Banjul Africa/Bissau Africa/Blantyre Africa/Brazzaville Africa/Bujumbura Africa/Cairo Africa/Casablanca Africa/Ceuta Africa/Conakry Africa/Dakar Africa/Dar_es_Salaam Africa/Djibouti Africa/Douala Africa/El_Aaiun Africa/Freetown Africa/Gaborone Africa/Harare Africa/Johannesburg Africa/Juba Africa/Kampala Africa/Khartoum Africa/Kigali Africa/Kinshasa Africa/Lagos Africa/Libreville Africa/Lome Africa/Luanda Africa/Lubumbashi Africa/Lusaka Africa/Malabo Africa/Maputo Africa/Maseru Africa/Mbabane Africa/Mogadishu Africa/Monrovia Africa/Nairobi Africa/Ndjamena Africa/Niamey Africa/Nouakchott
[JIRA] (JENKINS-60575) Blueocean should show triggered jobs while pending
Title: Message Title
Josh Soref created an issue
Jenkins / JENKINS-60575
Blueocean should show triggered jobs while pending
Issue Type:
New Feature
Assignee:
Unassigned
Attachments:
image-2019-12-23-11-52-51-685.png
Components:
blueocean-plugin
Created:
2019-12-23 16:57
Priority:
Minor
Reporter:
Josh Soref
Consider a pipeline like this:
pipeline {
stages {
stage("Trigger Deploy") {
steps {
build "happy-integration"
}
}
}
}
While the triggered build is running, the blue ocean view doesn't provide any way to get to the resultant build. Once it's built, an extra table is presented called Triggered Builds which provides easy access to it:
Add Comment
[JIRA] (JENKINS-60480) github is deprecating basic authentication using password
Title: Message Title
Josh Soref edited a comment on JENKINS-60480
Re: github is deprecating basic authentication using password
Ok, for us, there were apparently two items. I've switched things over to the other one. Hopefully that will make the alert go away.But this experience was painful.One thing that would help immensely is the ability to search for credentials whose password matches an entered value. Expected results should only include passwords the searching user is allowed to use. Had I been able to do that, I could have quickly identified the problem. Fwiw, the best I've managed is:{code:java}admin:org, admin:public_key, admin:repo_hook, read:user, repo {code}We had credentials of:{code:java}repo {code}{code:java}admin:repo_hook, repo {code}But they weren't sufficient for us.
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.203567.1576268869000.13364.1576717380248%40Atlassian.JIRA.
[JIRA] (JENKINS-60480) github is deprecating basic authentication using password
Title: Message Title Josh Soref commented on JENKINS-60480 Re: github is deprecating basic authentication using password Ok, for us, there were apparently two items. I've switched things over to the other one. Hopefully that will make the alert go away. But this experience was painful. One thing that would help immensely is the ability to search for credentials whose password matches an entered value. Expected results should only include passwords the searching user is allowed to use. Had I been able to do that, I could have quickly identified the problem. 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.203567.1576268869000.13358.1576715160212%40Atlassian.JIRA.
[JIRA] (JENKINS-60480) github is deprecating basic authentication using password
Title: Message Title Josh Soref commented on JENKINS-60480 Re: github is deprecating basic authentication using password Also, a quick look at my jenkins /credentials/store/system/domain/_/ shows that the account currently has a token with repo which was Last used within the last week according to github, and yet, I'm still getting warnings. 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.203567.1576268869000.13340.1576713540465%40Atlassian.JIRA.
[JIRA] (JENKINS-60480) github is deprecating basic authentication using password
Title: Message Title Josh Soref commented on JENKINS-60480 Re: github is deprecating basic authentication using password Mark Waite: Do you know what permissions we should give it in https://github.com/settings/tokens/new? My ticket isn't claiming that work necessarily needs to be done in the plugin, just that a "what to do" should be published. (Although, probably it's best for the plugin to just guide people through the process since it seems like it'd be pretty easy for it to do that and remember "this token is good" or something.) 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.203567.1576268869000.13322.1576713300264%40Atlassian.JIRA.
[JIRA] (JENKINS-60480) github is deprecating basic authentication using password
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-60480 github is deprecating basic authentication using password Issue Type: New Feature Assignee: Kirill Merkushev Components: github-api-plugin, github-branch-source-plugin, github-plugin Created: 2019-12-13 20:27 Priority: Minor Reporter: Josh Soref You recently used a password to access an endpoint through the GitHub API using okhttp/2.7.5. We will deprecate basic authentication using password to this endpoint soon: https://api.github.com/repositories/155774655 We recommend using a personal access token (PAT) with the appropriate scope to access this endpoint instead. Visit https://github.com/settings/tokens for more information. This might be just something that admins need to deal w/, but it would be helpful if there was a migration page explaining what to do from the jenkins side. (it isn't particularly obvious to me) Add Comment
[JIRA] (JENKINS-60324) nested Parallel in declarative results in temporary misrendering
Title: Message Title
Josh Soref created an issue
Jenkins / JENKINS-60324
nested Parallel in declarative results in temporary misrendering
Issue Type:
New Feature
Assignee:
Unassigned
Attachments:
image-2019-11-28-15-13-12-961.png, image-2019-11-28-15-13-20-794.png, image-2019-11-28-15-13-25-702.png
Components:
blueocean-plugin, pipeline
Created:
2019-11-28 21:10
Priority:
Minor
Reporter:
Josh Soref
We're using a declarative pipeline that happens to use
def {}
// and
script {}
// and
parallel objects
def projectName(projectPrefix, flavor) {
return "${projectPrefix} ${flavor}"
}
def templateProjectNode (project, flavor, publish) {
return {
node {
stage(projectName(project, flavor)) {
try {
sh "hostname"
script {
sh label: "Compile + Test + Publish", script: "hostname"
}
}
finally {
junit "*/target/test-reports/**/*.xml"
archiveArtifacts "*/target/test-reports/**"
archiveArtifacts "*/target/*/*report/**"
}
}
}
}
}
def generateProjects (projectList) {
def projects = projectList.collectEntries {
[(projectName(it[0],
[JIRA] (JENKINS-60215) Show ssh public keys in ssh key editing ui
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-60215 Show ssh public keys in ssh key editing ui Change By: Josh Soref Component/s: ssh-credentials-plugin Component/s: core 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.203188.157419007.4023.1574202900072%40Atlassian.JIRA.
[JIRA] (JENKINS-60215) Show ssh public keys in ssh key editing ui
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-60215 Show ssh public keys in ssh key editing ui Issue Type: New Feature Assignee: Unassigned Components: core Created: 2019-11-19 19:01 Priority: Minor Reporter: Josh Soref visit http://jenkins/credentials/store/system/domain/_/ click the wrench for a SSH Username with private key item Actual results: Scope ID Description Username Private Key Enter directly Key Concealed for Confidentiality [Replace] Passphrase Expected results: Private Key should be Key, and under Enter directly, there should be a Public Key showing the current calculated Public Key. The item currently labeled as Key should be renamed Private Key. See also JENKINS-56940
[JIRA] (JENKINS-60162) Restore files previously stashed should mention the name of the stash
Title: Message Title
Josh Soref updated an issue
Jenkins / JENKINS-60162
Restore files previously stashed should mention the name of the stash
Change By:
Josh Soref
We use multiple stashes w/ pipeline. We see:{code:java}Restore files previously stashed 2s...Restore files previously stashed <1s... {code}It would be nice if the name of the stash was shown in gray. Similarly for{code:java}Stash some files to be used later in the build...Stash some files to be used later in the build... {code}
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.203114.1573695978000.222.1573696080072%40Atlassian.JIRA.
[JIRA] (JENKINS-60162) Restore files previously stashed should mention the name of the stash
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-60162 Restore files previously stashed should mention the name of the stash Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin, core Created: 2019-11-14 01:46 Priority: Minor Reporter: Josh Soref We use multiple stashes w/ pipeline. We see: Restore files previously stashed 2s ... Restore files previously stashed <1s ... It would be nice if the name of the stash was shown in gray. Add Comment
[JIRA] (JENKINS-60064) upgrading git(client)plugin from 4.0.0rc/3.0.0rc to 4.0.0/3.0.0 resulted in 1024 changes being attributed to single commit
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-60064 upgrading git(client)plugin from 4.0.0rc/3.0.0rc to 4.0.0/3.0.0 resulted in 1024 changes being attributed to single commit Issue Type: Bug Assignee: Mark Waite Components: git-client-plugin, git-plugin Created: 2019-11-05 18:03 Priority: Minor Reporter: Josh Soref We use github-branch-source-plugin to detect changes. Getting remote branch master... [Tue Nov 05 11:54:53 EST 2019] Received Push event to branch master in repository org/repo UPDATED event from 192.30.252.91 ⇒ https://jenkins/github-webhook/ with timestamp Tue Nov 05 11:54:48 EST 2019 11:54:53 Connecting to https://api.github.com using u...@example.com/** (User account for GitHub) Checking branch master Getting remote pull requests from branch master... ‘Jenkinsfile’ found Met criteria Changes detected: master (OLD-SHA → NEXT-SHA) This is what triggered the build. I checked github and confirmed, this is a single commit. Actual result: Both classic and blueocean show 1024 changes listed for the build instead of the expected single commit (NEXT-SHA).
[JIRA] (JENKINS-59965) Update log levels management ui
Title: Message Title
Josh Soref created an issue
Jenkins / JENKINS-59965
Update log levels management ui
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2019-10-28 16:02
Priority:
Minor
Reporter:
Josh Soref
I've tried changing the default ("") log level for "INFO" to "ALL", via jenkins/log/levels, but this doesn't do anything. As it's available and described as a thing, there should be a note explaining this constraint. It doesn't have to be the full details, it can be a link to a page that explains them.
# If you create a new logger, its jenkins/log/loggerName/configure page has a field for a logger name, and when you type, it offers completion suggestions. The main page jenkins/log/levels doesn't offer suggestions. I don't think there's a good reason for this discrepancy.
There is a lot of other strange behavior about the main logger. I really don't understand why I can't seem to use it to (sorry, lost train of thought, filing anyway, we can fix later)
[JIRA] (JENKINS-59929) blueocean should indicate when a PR is closed
Title: Message Title Josh Soref commented on JENKINS-59929 Re: blueocean should indicate when a PR is closed When I start from the Activity tab of blue ocean, things tend to have the PR pop out link... 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.202730.1571954987000.778.1571955120124%40Atlassian.JIRA.
[JIRA] (JENKINS-59929) blueocean should indicate when a PR is closed
Title: Message Title Josh Soref commented on JENKINS-59929 Re: blueocean should indicate when a PR is closed Oddly, when I'm starting from the Pull Requests tab of blue ocean, things tend not to have the PR pop out link... 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.202730.1571954987000.777.1571955120071%40Atlassian.JIRA.
[JIRA] (JENKINS-59929) blueocean should indicate when a PR is closed
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-59929 blueocean should indicate when a PR is closed Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin, github-branch-source-plugin Created: 2019-10-24 22:09 Priority: Minor Reporter: Josh Soref (blueocean-dashboard) I can't quite describe what's going on. Open pull requests generally show: https://github.com/jenkinsci/blueocean-plugin/blob/3aca1b85452de1ceba39d86f318efb42ce03cc26/blueocean-dashboard/src/main/js/components/RunDetailsHeader.jsx#L146 Sometimes, closed PRs don't seem to show this. It's possible that I'm in the wrong view. Sometimes, closed PRs do show this, but it would be more helpful if it could indicate that the PR is closed (yes, I can click the link, but it's an expensive operation for a user, whereas the information would be more valuable displayed directly to the user in blue ocean). Add Comment
[JIRA] (JENKINS-59928) Add first and last build buttons to blueocean
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-59928 Add first and last build buttons to blueocean Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2019-10-24 21:52 Priority: Minor Reporter: Josh Soref JENKINS-49827 added Next/Previous buttons. I think the right iconography is |< and >| for first/last. There may be some value to have << and >> for jumping back/forward some number of builds (5 or 10 at a time?). Add Comment This message was
[JIRA] (JENKINS-59927) Test Result Trend / show test # and failure # are unhelpful
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-59927 Test Result Trend / show test # and failure # are unhelpful Issue Type: Improvement Assignee: Unassigned Components: junit-plugin Created: 2019-10-24 21:36 Priority: Minor Reporter: Josh Soref We have a project which has approximately 2500 tests which are run in an average build. For a given run, between 0 and 3 tests may fail (on average, 0). The default view "Test Result Trend" shows a blue graph of all of our passing tests – the scale of the failing tests is invisible. This makes the default view absolutely useless. As it happens, the number of tests we run in a given run actually fluctuates significantly (50 one run, 1900 the next). To make the graphs useful for us, a couple of presentations could be considered: Just show two graphs side by side. – Personally, I don't think this is a great approach. Use independent Y axes (typically a left axis for the total tests, and a right axis for failed tests) – this is fairly common in charts with mismatched scales. – In this model, the left y-axis label could be tests and the right y-axis label could be failures. Use an inverted graph for failures and stack them so that they share a common x-axis but total tests counts grow up, and failed tests grow down from the common x-axis (with independently labeled y-axes on the left). Beyond that: The label for the link to change the view show test # and failure # isn't really a great link text, it's both fairly long and annoyingly terse at the same time.
[JIRA] (JENKINS-59849) Spaces don't work in resource root paths
Title: Message Title Josh Soref closed an issue as Fixed Picked up the change, verified it works. Thanks Jenkins / JENKINS-59849 Spaces don't work in resource root paths Change By: Josh Soref Status: Resolved Closed 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.202585.1571419376000.18630.1571865300230%40Atlassian.JIRA.
[JIRA] (JENKINS-59850) Use of toString() on hudson.util.Secret from hudson.util.jelly.MorphTagLibrary$1.run(MorphTagLibrary.java:91)
Title: Message Title Josh Soref commented on JENKINS-59850 Re: Use of toString() on hudson.util.Secret from hudson.util.jelly.MorphTagLibrary$1.run(MorphTagLibrary.java:91) I'm not sure what I did to trigger it. Which is unfortunate. 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.202586.1571421684000.11023.1571531700341%40Atlassian.JIRA.
[JIRA] (JENKINS-10163) Update Hadoop plugin to latest stable version
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-10163 Update Hadoop plugin to latest stable version Change By: Josh Soref Summary: Uopdate Update Hadoop plugin to latest stable version 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.140351.130941862.10711.1571424900388%40Atlassian.JIRA.
[JIRA] (JENKINS-10162) Update Hadoop plugin to latest stable version
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-10162 Update Hadoop plugin to latest stable version Change By: Josh Soref Summary: Uopdate Update Hadoop plugin to latest stable version 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.140350.1309418588000.10714.1571424900430%40Atlassian.JIRA.
[JIRA] (JENKINS-59849) Spaces don't work in resource root paths
Title: Message Title Josh Soref commented on JENKINS-59849 Re: Spaces don't work in resource root paths Daniel Beck found the problem: https://github.com/jenkinsci/jenkins/blob/11c1146d0dc30e948ade8d1636ae01345c294291/core/src/main/java/jenkins/security/ResourceDomainRootAction.java#L166-L176 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.202585.1571419376000.10708.1571423880168%40Atlassian.JIRA.
[JIRA] (JENKINS-59849) Spaces don't work in resource root paths
Title: Message Title
Josh Soref updated an issue
Jenkins / JENKINS-59849
Spaces don't work in resource root paths
Change By:
Josh Soref
We have an archived folder called {{HeadlessChrome 77.0.3865 (Linux 0.0.0)}} with a file {{index.html}} the contents of that folder fail when served via resource root. If I make a copy of the folder {{HeadlessChrome-77.0.3865-(Linux-0.0.0)}}, that {{index.html}} file will be served successfully.Pipeline for testing:{code:java}node('master') { sh '''mkdir -p " a/ foo bar has lots of spaces to make people unhappy " touch " a/ foo bar has lots of spaces to make people unhappy /index.html" ''' archiveArtifacts ' foo bar a /'}{code}
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
[JIRA] (JENKINS-59852) Strange logging {"enableFile":false,"tagFile":"","emitOnCheckout":false,"enableProperty":false,"tagProperties":""}
Title: Message Title
Josh Soref created an issue
Jenkins / JENKINS-59852
Strange logging {"enableFile":false,"tagFile":"","emitOnCheckout":false,"enableProperty":false,"tagProperties":""}
Issue Type:
Bug
Assignee:
Datadog HQ
Components:
datadog-plugin
Created:
2019-10-18 18:09
Priority:
Minor
Reporter:
Josh Soref
Periodically, this appears in my console where i'm running jenkins:
{"enableFile":false,"tagFile":"","emitOnCheckout":false,"enableProperty":false,"tagProperties":""}
datadog 0.7.1 At the very least, if datadog thinks it's important, it'd be nice if it had some indication it was from datadog.
Add Comment
[JIRA] (JENKINS-59850) Use of toString() on hudson.util.Secret from hudson.util.jelly.MorphTagLibrary$1.run(MorphTagLibrary.java:91)
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-59850 Use of toString() on hudson.util.Secret from hudson.util.jelly.MorphTagLibrary$1.run(MorphTagLibrary.java:91) Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-10-18 18:01 Priority: Minor Reporter: Josh Soref Use of toString() on hudson.util.Secret from hudson.util.jelly.MorphTagLibrary$1.run(MorphTagLibrary.java:91). Prefer getPlainText() or getEncryptedValue() depending your needs. see https://jenkins.io/redirect/hudson.util.Secret/ https://github.com/jenkinsci/jenkins/blob/22aa2e6e766074d11249893e3f35e0b99e20d3d0/core/src/main/java/hudson/util/jelly/MorphTagLibrary.java#L91 Add Comment
[JIRA] (JENKINS-59849) Spaces don't work in resource root paths
Title: Message Title
Josh Soref updated an issue
Jenkins / JENKINS-59849
Spaces don't work in resource root paths
Change By:
Josh Soref
We have an archived folder called {{HeadlessChrome 77.0.3865 (Linux 0.0.0)}} with a file {{index.html}} the contents of that folder fail when served via resource root. If I make a copy of the folder {{HeadlessChrome-77.0.3865-(Linux-0.0.0)}}, that {{index.html}} file will be served successfully.Pipeline for testing:{code :java }node('master') { sh '''mkdir -p "foo bar" touch "foo bar/index.html" ''' archiveArtifacts 'foo bar/'}{code}
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
[JIRA] (JENKINS-59849) Spaces don't work in resource root paths
Title: Message Title
Josh Soref updated an issue
Jenkins / JENKINS-59849
Spaces don't work in resource root paths
Change By:
Josh Soref
We have an archived folder called {{HeadlessChrome 77.0.3865 (Linux 0.0.0)}} with a file {{index.html}} the contents of that folder fail when served via resource root. If I make a copy of the folder {{HeadlessChrome-77.0.3865-(Linux-0.0.0)}}, that {{index.html}} file will be served successfully. Pipeline for testing:{code}node('master') { sh '''mkdir "foo bar" touch "foo bar/index.html" ''' archiveArtifacts 'foo bar/'}{code}
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
[JIRA] (JENKINS-59849) Spaces don't work in resource root paths
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-59849 Spaces don't work in resource root paths Change By: Josh Soref Summary: Parentheses Spaces don't work in resource root paths 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.202585.1571419376000.10642.1571419500069%40Atlassian.JIRA.
[JIRA] (JENKINS-59849) Parentheses don't work in resource root paths
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-59849 Parentheses don't work in resource root paths Issue Type: Improvement Assignee: Unassigned Components: core Created: 2019-10-18 17:22 Priority: Minor Reporter: Josh Soref We have an archived folder called HeadlessChrome 77.0.3865 (Linux 0.0.0) with a file index.html the contents of that folder fail when served via resource root. If I make a copy of the folder HeadlessChrome-77.0.3865-(Linux-0.0.0), that index.html file will be served successfully. Add Comment
[JIRA] (JENKINS-59812) config history should provide helpful error when it can't create history
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-59812 config history should provide helpful error when it can't create history Issue Type: Improvement Assignee: Stefan Brausch Components: jobconfighistory-plugin Created: 2019-10-16 22:53 Priority: Minor Reporter: Josh Soref Some of the directories in jenkins/config-history/jobs were owned by a user other than the jenkins user, which resulted in this error: java.lang.RuntimeException: Could not create rootDir /var/lib/jenkins/.jenkins/config-history/jobs/JOBNAME/2019-10-16_18-41-10 at hudson.plugins.jobConfigHistory.FileHistoryDao.createNewHistoryDir(FileHistoryDao.java:262) at hudson.plugins.jobConfigHistory.FileHistoryDao.getRootDir(FileHistoryDao.java:151) at hudson.plugins.jobConfigHistory.FileHistoryDao.createNewHistoryEntry(FileHistoryDao.java:585) at hudson.plugins.jobConfigHistory.FileHistoryDao.createNewHistoryEntryAndCopyConfig(FileHistoryDao.java:284) at hudson.plugins.jobConfigHistory.FileHistoryDao.saveItem(FileHistoryDao.java:296) at hudson.plugins.jobConfigHistory.JobConfigHistorySaveableListener.onChange(JobConfigHistorySaveableListener.java:58) at hudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:81) at hudson.model.AbstractItem.save(AbstractItem.java:609) at hudson.model.Job.save(Job.java:190) at hudson.model.AbstractProject.save(AbstractProject.java:289) at hudson.BulkChange.commit(BulkChange.java:98) at hudson.model.Job.doConfigSubmit(Job.java:1347) at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:770) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)
[JIRA] (JENKINS-59665) Rework sorting for the Enabled and Uninstall columns of Installed in Plugin Manager
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-59665 Rework sorting for the Enabled and Uninstall columns of Installed in Plugin Manager Change By: Josh Soref open /pluginManager/installed (Jenkins 2.198)Have: # a couple of plugins with dependencies (enabled) # a couple of plugins (disabled) # a couple of plugins that have never been upgraded # a couple of plugins which have been upgradedh3. Actual resultsI can't really explain what it's doing. – It appears to be stable (i.e. toggling the sort direction for one of these columns reverses the sort), but it isn't global (i.e. changing the sort key to a different column, e.g. Name, and then back to the Enabled column results in a new sort).h3. Expected resultsh5. Sorting by Enabled should sort into three sets: # Enabled (checkbox checked) # Enabled (checkbox disabled) and can't be disabled (because they're used by enabled plugins) # Disabled (checkbox unchecked)h5. Sorting by Uninstall should sort into : two sets: # Uninstall button enabled # Uninstall button disabled Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59757) Discovered project-repositories should have Run button
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-59757 Discovered project-repositories should have Run button Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin, branch-api-plugin, github-branch-source-plugin Created: 2019-10-11 21:38 Priority: Minor Reporter: Josh Soref If we go to: /jenkins/blue/organizations/jenkins/standalone-project/activity There are two buttons: [ Run ] [ Disable ] above the Status/Run/Commit/Message/Duration/Completed/(replay) table If we go to /jenkins/blue/organizations/jenkins/GitHub%2Frepo/activity The Run & Disable buttons are missing. Disable being missing is understandable as the repository was discovered by project discovery. Run being missing is unfortunate. /jenkins/job/GitHub/job/repo/job/master/ has a [ Build ] or [ Build with parameters ] button (depending on whether or not the job supports parameters) – And for the standalone-project the Run button works as Build or Build with parameters as applicable. Add Comment
[JIRA] (JENKINS-59388) Broken formatting for Boolean parameters
Title: Message Title Josh Soref commented on JENKINS-59388 Re: Broken formatting for Boolean parameters It's by design. It will look better when we switch away from the table layout. 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.201944.1568631629000.5124.1570726270265%40Atlassian.JIRA.
[JIRA] (JENKINS-59267) Timeout exceptions in jenkins log when jenkins-cli executes a long-running command
Title: Message Title
Josh Soref updated an issue
Jenkins / JENKINS-59267
Timeout exceptions in jenkins log when jenkins-cli executes a long-running command
Change By:
Josh Soref
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. {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 '"' 0x00 0x00 0x00 0x01 0x05 'h' 0x00 0x00 0x00
[JIRA] (JENKINS-59267) Timeout exceptions in jenkins log when jenkins-cli executes a long-running command
Title: Message Title
Josh Soref updated an issue
Jenkins / JENKINS-59267
Timeout exceptions in jenkins log when jenkins-cli executes a long-running command
Change By:
Josh Soref
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. {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 '"' 0x00 0x00 0x00 0x01 0x05 'h' 0x00 0x00 0x00
[JIRA] (JENKINS-59267) Timeout exceptions in jenkins log when jenkins-cli executes a long-running command
Title: Message Title
Josh Soref updated an issue
Jenkins / JENKINS-59267
Timeout exceptions in jenkins log when jenkins-cli executes a long-running command
Change By:
Josh Soref
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. {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 '"' 0x00 0x00 0x00 0x01 0x05 'h' 0x00 0x00 0x00
[JIRA] (JENKINS-59665) Rework sorting for the Enabled and Uninstall columns of Installed in Plugin Manager
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-59665 Rework sorting for the Enabled and Uninstall columns of Installed in Plugin Manager Issue Type: Improvement Assignee: Unassigned Components: core Created: 2019-10-04 18:27 Priority: Minor Reporter: Josh Soref open /pluginManager/installed Have: a couple of plugins with dependencies (enabled) a couple of plugins (disabled) a couple of plugins that have never been upgraded a couple of plugins which have been upgraded Actual results I can't really explain what it's doing. – It appears to be stable (i.e. toggling the sort direction for one of these columns reverses the sort), but it isn't global (i.e. changing the sort key to a different column, e.g. Name, and then back to the Enabled column results in a new sort). Expected results Sorting by Enabled should sort into three sets: Enabled (checkbox checked) Enabled (checkbox disabled) and can't be disabled (because they're used by enabled plugins) Disabled (checkbox unchecked) Sorting by Uninstall should sort into: two sets:
[JIRA] (JENKINS-59665) Rework sorting for the Enabled and Uninstall columns of Installed in Plugin Manager
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-59665 Rework sorting for the Enabled and Uninstall columns of Installed in Plugin Manager Change By: Josh Soref open /pluginManager/installed (Jenkins 2.198) Have: # a couple of plugins with dependencies (enabled) # a couple of plugins (disabled) # a couple of plugins that have never been upgraded # a couple of plugins which have been upgradedh3. Actual resultsI can't really explain what it's doing. – It appears to be stable (i.e. toggling the sort direction for one of these columns reverses the sort), but it isn't global (i.e. changing the sort key to a different column, e.g. Name, and then back to the Enabled column results in a new sort).h3. Expected resultsh5. Sorting by Enabled should sort into three sets: # Enabled (checkbox checked) # Enabled (checkbox disabled) and can't be disabled (because they're used by enabled plugins) # Disabled (checkbox unchecked)h5. Sorting by Uninstall should sort into: two sets: # Uninstall button enabled # Uninstall button disabled Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-48566) Jenkins Stage History Fails When Job is Renamed
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-48566 Jenkins Stage History Fails When Job is Renamed Change By: Josh Soref Summary: Jenkis Jenkins Stage History Fails When Job is Renamed 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.187187.1513269614000.6279.1569523860519%40Atlassian.JIRA.
[JIRA] (JENKINS-23898) Jenkins and Swarm Plugin Installation problem
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-23898 Jenkins and Swarm Plugin Installation problem Change By: Josh Soref Summary: Jinkins Jenkins and Swarm Plugin Instalation Installation problem 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.156363.1405930145000.6276.1569523860436%40Atlassian.JIRA.
[JIRA] (JENKINS-58779) LogRotator stops cleaning, if a build directory has been deleted externally
Title: Message Title
Josh Soref updated an issue
Jenkins / JENKINS-58779
LogRotator stops cleaning, if a build directory has been deleted externally
Change By:
Josh Soref
The deletion of a build/run in Jenkins is handled by the {{ delete() }} method. It throws an exception, when the build directory on disk has already beenremoved been removed and stops deleting the build. Unfortunately, the {{ hudson.tasks.LogRotator.perform(Job) }} method does not check for this exception and will STOP _STOP_ cleaning up, once even just one build throws that exception. This behaviour can be fixed in the following ways (a pull-request will be uploaded shortly): # The {{ Run.delete() }} method must still unlink the job, even if the build directory has been removed externally. # The log output of {{ Run.delete() }} must be made less verbose (it prints the ENTIRE folder content by default, into the job that is doing the cleanup) # The {{ LogRotator.perform() }} method must handle the exceptions being thrown by {{ delete() }} gracefully.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-58779) LogRotator stops cleaning, if a build directory has been deleted externally
Title: Message Title Josh Soref started work on JENKINS-58779 Change By: Josh Soref Status: Open In Progress 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.201089.1564737737000.3598.1569268380428%40Atlassian.JIRA.
[JIRA] (JENKINS-58779) LogRotator stops cleaning, if a build directory has been deleted externally
Title: Message Title Josh Soref stopped work on JENKINS-58779 Change By: Josh Soref Status: In Progress Open 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.201089.1564737737000.3600.1569268380453%40Atlassian.JIRA.
[JIRA] (JENKINS-58779) LogRotator stops cleaning, if a build directory has been deleted externally
Title: Message Title Josh Soref updated JENKINS-58779 Jenkins / JENKINS-58779 LogRotator stops cleaning, if a build directory has been deleted externally Change By: Josh Soref Status: Open Fixed but Unreleased Resolution: Fixed 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.201089.1564737737000.3602.1569268380480%40Atlassian.JIRA.
[JIRA] (JENKINS-59486) Restart Jenkins when installation is complete and no jobs are running should preload the restarting jenkins image
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-59486 Restart Jenkins when installation is complete and no jobs are running should preload the restarting jenkins image Issue Type: Improvement Assignee: Unassigned Components: core Created: 2019-09-23 14:29 Priority: Minor Reporter: Josh Soref Steps: visit jenkins/pluginManager/installed select a plugin to update click the install button check the Restart Jenkins when installation is complete and no jobs are running box Actual results: Installing Plugins/Upgrades Preparation Checking internet connectivity Checking update center connectivity Success Mailer
[JIRA] (JENKINS-59435) Pull request blue ocean links should go to the relevant blue ocean view
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-59435 Pull request blue ocean links should go to the relevant blue ocean view Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin, branch-api-plugin, github-branch-source-plugin, scm-api-plugin Created: 2019-09-18 16:43 Priority: Minor Reporter: Josh Soref Steps Go to: Jenkins > New Item. Fill in Enter an item name: "test". Select GitHub Organization. Click OK. In Projects: Fill in Credentials. Fill in Owner. Add Behaviors for Within repository: Add Discover branches: Exclude branches that are also filed as PRs. Add Filter by name (with regular _expression_): "master|.PR.". Click Save. Go to the "test" project: /jenkins/job/test/. Click on a repository "repo": /jenkins/job/test/repo/.
[JIRA] (JENKINS-59412) Clarify that build history does not include pipeline stages
Title: Message Title Josh Soref assigned an issue to Josh Soref Jenkins / JENKINS-59412 Clarify that build history does not include pipeline stages Change By: Josh Soref Assignee: Josh Soref 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.201973.1568739433000.5616.1568744460309%40Atlassian.JIRA.
[JIRA] (JENKINS-59409) Please support logging stages that are tasked to a node
Title: Message Title Josh Soref assigned an issue to Unassigned Jenkins / JENKINS-59409 Please support logging stages that are tasked to a node Change By: Josh Soref Assignee: David Olorundare 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.201969.1568735833000.5618.1568744460445%40Atlassian.JIRA.
[JIRA] (JENKINS-59412) Clarify that build history does not include pipeline stages
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-59412 Clarify that build history does not include pipeline stages Issue Type: Improvement Assignee: Unassigned Components: core Created: 2019-09-17 16:57 Priority: Minor Reporter: Josh Soref Per JENKINS-38877, Jenkins doesn't report stage information for pipeline jobs. This surprising. It's IMO helpful for people to at least be aware of this. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59409) Please support logging stages that are tasked to a node
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-59409 Please support logging stages that are tasked to a node Issue Type: Improvement Assignee: David Olorundare Components: audit-log-plugin Created: 2019-09-17 15:57 Priority: Minor Reporter: Josh Soref JENKINS-38877 notes that the integrated build history doesn't include information about when build stages in pipeline jobs are run on nodes. It would be very helpful if the audit-log-plugin could, for each stage, log: job run stage (probably a path, or link or something) start time status end time Add Comment
[JIRA] (JENKINS-38401) Jenkinsfile Changelist number doesn't get updated when using pipeline Script from SCM.
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-38401 Jenkinsfile Changelist number doesn't get updated when using pipeline Script from SCM. Change By: Josh Soref Summary: Jekinsfile Jenkinsfile Changelist number doesn't get updated when using pipeline Script from SCM. 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.174578.147309000.5253.1568734260355%40Atlassian.JIRA.
[JIRA] (JENKINS-25822) No more connections to slaves - no log - truncated command
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-25822 No more connections to slaves - no log - truncated command Change By: Josh Soref Summary: No more connections to slaves - no log - troncated truncated command 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.159397.1417169004000.5250.1568734203277%40Atlassian.JIRA.
[JIRA] (JENKINS-49121) Ability to skip stages and preserve build history
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-49121 Ability to skip stages and preserve build history Change By: Josh Soref It would be nice, when you can skip single stages in a pipeline withut loosing without losing the build history in the visualization.At the moment I have two choices:* Skip the complete stage: The whole build history in the visualization will be lost.* Execute the stage but not the content: The build history is preserved, but the stage color will be the same as the rest of the stage. It should be clear, that the stage content wasn't executed. Maybe there could be a step to set the stage status and so change the color of the stage (just an idea). 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
[JIRA] (JENKINS-42938) Agent build history does not show pipeline steps
Title: Message Title Josh Soref updated JENKINS-42938 Jenkins / JENKINS-42938 Agent build history does not show pipeline steps Change By: Josh Soref Status: Reopened Fixed but Unreleased Resolution: Duplicate 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.179949.1490017403000.5234.1568734022878%40Atlassian.JIRA.
[JIRA] (JENKINS-42938) Agent build history does not show pipeline steps
Title: Message Title Josh Soref updated JENKINS-42938 Jenkins / JENKINS-42938 Agent build history does not show pipeline steps Change By: Josh Soref Status: Open Fixed but Unreleased Resolution: Duplicate 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.179949.1490017403000.5226.1568734022723%40Atlassian.JIRA.
[JIRA] (JENKINS-42938) Agent build history does not show pipeline steps
Title: Message Title Josh Soref updated JENKINS-42938 Jenkins / JENKINS-42938 Agent build history does not show pipeline steps Change By: Josh Soref Resolution: Duplicate Status: Fixed but Unreleased Reopened 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.179949.1490017403000.5232.1568734022829%40Atlassian.JIRA.
[JIRA] (JENKINS-59398) blueocean header should show who replayed a job run
Title: Message Title Josh Soref commented on JENKINS-59398 Re: blueocean header should show who replayed a job run I can see a couple of ways to do this: as in PR#323, changing the ReplayCause to report the user directly – there's a slight risk of showing the same information more than once. changing all clients of ReplayCause to do the same work – lots of consumers are stuck reinventing some code. changing blueocean to report (and try to flatten) all of the causes into this field – I don't think this will be particularly pretty (which is probably why it wasn't done already). I don't really care which way it's implemented, I'd just like to see the information I need when I'm looking at blueocean. 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.201955.1568664348000.4708.1568671740055%40Atlassian.JIRA.
