[JIRA] (JENKINS-61719) Create tests for TestConfiguration (in TestScoreTest)
Title: Message Title Lion Kosiuk assigned an issue to Lion Kosiuk Jenkins / JENKINS-61719 Create tests for TestConfiguration (in TestScoreTest) Change By: Lion Kosiuk Assignee: Lion Kosiuk 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.205545.1585335461000.2356.1585553580262%40Atlassian.JIRA.
[JIRA] (JENKINS-61719) Create tests for TestConfiguration (in TestScoreTest)
Title: Message Title Lion Kosiuk started work on JENKINS-61719 Change By: Lion Kosiuk Status: Open In Progress 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.205545.1585335461000.2360.1585553640242%40Atlassian.JIRA.
[JIRA] (JENKINS-61720) Create tests for CoverageConfiguration (in CoverageScoreTest)
Title: Message Title Johannes Hintermaier started work on JENKINS-61720 Change By: Johannes Hintermaier Status: Open In Progress 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.205546.1585336422000.2364.1585553760345%40Atlassian.JIRA.
[JIRA] (JENKINS-61720) Create tests for CoverageConfiguration (in CoverageScoreTest)
Title: Message Title Johannes Hintermaier assigned an issue to Johannes Hintermaier Jenkins / JENKINS-61720 Create tests for CoverageConfiguration (in CoverageScoreTest) Change By: Johannes Hintermaier Assignee: Johannes Hintermaier 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.205546.1585336422000.2362.1585553760289%40Atlassian.JIRA.
[JIRA] (JENKINS-61253) Remoting using WebSocket fails with "Handshake response not received" Exception
Title: Message Title ethorsa reopened an issue Jenkins / JENKINS-61253 Remoting using WebSocket fails with "Handshake response not received" Exception Change By: ethorsa Resolution: Not A Defect Status: Closed Reopened 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.204820.1582797002000.2366.1585553820230%40Atlassian.JIRA.
[JIRA] (JENKINS-61253) Remoting using WebSocket fails with "Handshake response not received" Exception
Title: Message Title ethorsa commented on JENKINS-61253 Re: Remoting using WebSocket fails with "Handshake response not received" Exception Unfortunately I run into the same problem with Jenkins 2.222.1 (Remoting 4.3) too. My minimal steps to reproduce the error: Create a new static agent on the master (test-websocket in this example) Enable "Use WebSocket" in it's configuration Start the agent: java -jar remoting-4.3.jar -jnlpUrl https://:/computer/test-websocket/slave-agent.jnlp -secret -workDir "C:\temp\jenkins-test" After ~ 30 sec the agent fails by exception: Mar 30, 2020 9:35:24 AM hudson.remoting.jnlp.Main$CuiListener error SEVERE: Handshake response not received. io.jenkins.remoting.shaded.javax.websocket.DeploymentException: Handshake response not received. at io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager$3$1.run(ClientManager.java:694) at io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager$3.run(ClientManager.java:712) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager$SameThreadExecutorService.execute(ClientManager.java:866) at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118) at io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager.connectToServer(ClientManager.java:511) at io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager.connectToServer(ClientManager.java:355) at hudson.remoting.Engine.runWebSocket(Engine.java:627) at hudson.remoting.Engine.run(Engine.java:469) The master log shows a single related entry: INFO jenkins.slaves.DefaultJnlpSlaveReceiver channelClosed Jetty (winstone)-2975 for test-websocket terminated: java.nio.channels.ClosedChannelException
[JIRA] (JENKINS-35905) Add option to Fail the build if node label does not exist or if it cannot be provisioned within a timeout
Title: Message Title Marcus Schulmann commented on JENKINS-35905 Re: Add option to Fail the build if node label does not exist or if it cannot be provisioned within a timeout I wonder why this is still not yet implemented. This clogged our whole build-pipeline over the weekend because one agent was down, which was needed for specific tests. 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.171838.1465967113000.2389.1585554721651%40Atlassian.JIRA.
[JIRA] (JENKINS-61253) Remoting using WebSocket fails with "Handshake response not received" Exception
Title: Message Title
ethorsa edited a comment on JENKINS-61253
Re: Remoting using WebSocket fails with "Handshake response not received" Exception
Unfortunately I run into the same problem with Jenkins 2.222.1 (Remoting 4.3) too. My minimal steps to reproduce the error: # Create a new static agent on the master (_test-websocket_ in this example) # Enable _"Use WebSocket"_ in it's configuration # Start the agent:{noformat}java -jar remoting-4.3.jar -jnlpUrl https://:/computer/test-websocket/slave-agent.jnlp -secret -workDir "C:\temp\jenkins-test"{noformat}After ~ 30 sec the agent fails by exception:{noformat}Mar 30, 2020 9:35:24 AM hudson.remoting.jnlp.Main$CuiListener errorSEVERE: Handshake response not received.io.jenkins.remoting.shaded.javax.websocket.DeploymentException: Handshake response not received. at io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager$3$1.run(ClientManager.java:694) at io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager$3.run(ClientManager.java:712) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager$SameThreadExecutorService.execute(ClientManager.java:866) at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118) at io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager.connectToServer(ClientManager.java:511) at io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager.connectToServer(ClientManager.java:355) at hudson.remoting.Engine.runWebSocket(Engine.java:627) at hudson.remoting.Engine.run(Engine.java:469){noformat}The master log shows a single related entry:{noformat}INFO jenkins.slaves.DefaultJnlpSlaveReceiver channelClosedJetty (winstone)-2975 for test-websocket terminated: java.nio.channels.ClosedChannelException{noformat} Error on the agent after connection failed:{noformat}java.nio.channels.ClosedChannelException at jenkins.agents.WebSocketAgents$Session.closed(WebSocketAgents.java:141) at jenkins.websocket.WebSocketSession.onWebSocketSomething(WebSocketSession.java:90) at com.sun.proxy.$Proxy118.onWebSocketClose(Unknown Source) at org.eclipse.jetty.websocket.common.events.JettyListenerEventDriver.onClose(JettyListenerEventDriver.java:119) at org.eclipse.jetty.websocket.common.WebSocketSession.callApplicationOnClose(WebSocketSession.java:389) at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.disconnect(AbstractWebSocketConnection.java:317) at org.eclipse.jetty.websocket.common.io.DisconnectCallback.succeeded(DisconnectCallback.java:42){noformat}
Add Comment
[JIRA] (JENKINS-61253) Remoting using WebSocket fails with "Handshake response not received" Exception
Title: Message Title
ethorsa edited a comment on JENKINS-61253
Re: Remoting using WebSocket fails with "Handshake response not received" Exception
Unfortunately I run into the same problem with Jenkins 2.222.1 (Remoting 4.3) too. My minimal steps to reproduce the error: # Create a new static agent on the master (_test-websocket_ in this example) # Enable _"Use WebSocket"_ in it's configuration # Start the agent:{noformat}java -jar remoting-4.3.jar -jnlpUrl https://:/computer/test-websocket/slave-agent.jnlp -secret -workDir "C:\temp\jenkins-test"{noformat}After ~ 30 sec the agent fails by exception:{noformat}Mar 30, 2020 9:35:24 AM hudson.remoting.jnlp.Main$CuiListener errorSEVERE: Handshake response not received.io.jenkins.remoting.shaded.javax.websocket.DeploymentException: Handshake response not received. at io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager$3$1.run(ClientManager.java:694) at io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager$3.run(ClientManager.java:712) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager$SameThreadExecutorService.execute(ClientManager.java:866) at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118) at io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager.connectToServer(ClientManager.java:511) at io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager.connectToServer(ClientManager.java:355) at hudson.remoting.Engine.runWebSocket(Engine.java:627) at hudson.remoting.Engine.run(Engine.java:469){noformat}The master log shows a single related entry:{noformat}INFO jenkins.slaves.DefaultJnlpSlaveReceiver channelClosedJetty (winstone)-2975 for test-websocket terminated: java.nio.channels.ClosedChannelException{noformat}Error on the agent after connection failed:{noformat}java.nio.channels.ClosedChannelException at jenkins.agents.WebSocketAgents$Session.closed(WebSocketAgents.java:141) at jenkins.websocket.WebSocketSession.onWebSocketSomething(WebSocketSession.java:90) at com.sun.proxy.$Proxy118.onWebSocketClose(Unknown Source) at org.eclipse.jetty.websocket.common.events.JettyListenerEventDriver.onClose(JettyListenerEventDriver.java:119) at org.eclipse.jetty.websocket.common.WebSocketSession.callApplicationOnClose(WebSocketSession.java:389) at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.disconnect(AbstractWebSocketConnection.java:317) at org.eclipse.jetty.websocket.common.io.DisconnectCallback.succeeded(DisconnectCallback.java:42) [...] {noformat}
Add Comment
[JIRA] (JENKINS-56091) no agent with label available clogs pipeline, should fail automatically instead of waiting
Title: Message Title Marcus Schulmann commented on JENKINS-56091 Re: no agent with label available clogs pipeline, should fail automatically instead of waiting This seems to be the same as https://issues.jenkins-ci.org/browse/JENKINS-35905 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.197522.1549911707000.2396.1585554780162%40Atlassian.JIRA.
[JIRA] (JENKINS-61409) Websocket connections crash if message size is greater than 64Kb
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-61409 Websocket connections crash if message size is greater than 64Kb Change By: Oliver Gondža Labels: lts-candidate non-trivial-lts-backporting websocket 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.205063.1583801943000.2401.158260352%40Atlassian.JIRA.
[JIRA] (JENKINS-61195) How to avoid "Checks if running on a Unix-like node" in BlueOcean output
Title: Message Title Gabor Mandity commented on JENKINS-61195 Re: How to avoid "Checks if running on a Unix-like node" in BlueOcean output We have updated our Jenkins instances to 2.204.5 LTS, but the problem is still there. docker-commons:1.16 docker-workflow:1.23 pipeline-build-step:2.11 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.204742.158253620.2412.158740174%40Atlassian.JIRA.
[JIRA] (JENKINS-61195) How to avoid "Checks if running on a Unix-like node" in BlueOcean output
Title: Message Title Gabor Mandity updated an issue Jenkins / JENKINS-61195 How to avoid "Checks if running on a Unix-like node" in BlueOcean output Change By: Gabor Mandity Issue Type: Task Bug 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.204742.158253620.2415.158740247%40Atlassian.JIRA.
[JIRA] (JENKINS-61253) Remoting using WebSocket fails with "Handshake response not received" Exception
Title: Message Title
ethorsa edited a comment on JENKINS-61253
Re: Remoting using WebSocket fails with "Handshake response not received" Exception
Unfortunately I run into the same problem with Jenkins 2.222.1 (Remoting 4.3) too . My minimal steps to reproduce the error: # Create a new static agent on the master (_test-websocket_ in this example) # Enable _"Use WebSocket"_ in it's configuration # Start the agent:{noformat}java -jar remoting-4.3.jar -jnlpUrl https://:/computer/test-websocket/slave-agent.jnlp -secret -workDir "C:\temp\jenkins-test"{noformat} After ~ 30 sec the agent fails by exception: {noformat}Mar 30, 2020 9:35:24 AM hudson.remoting.jnlp.Main$CuiListener errorSEVERE: Handshake response not received.io.jenkins.remoting.shaded.javax.websocket.DeploymentException: Handshake response not received. at io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager$3$1.run(ClientManager.java:694) at io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager$3.run(ClientManager.java:712) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager$SameThreadExecutorService.execute(ClientManager.java:866) at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118) at io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager.connectToServer(ClientManager.java:511) at io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager.connectToServer(ClientManager.java:355) at hudson.remoting.Engine.runWebSocket(Engine.java:627) at hudson.remoting.Engine.run(Engine.java:469){noformat} The master log shows a single related entry: {noformat}INFO jenkins.slaves.DefaultJnlpSlaveReceiver channelClosedJetty (winstone)-2975 for test-websocket terminated: java.nio.channels.ClosedChannelException{noformat} Error on the agent after connection failed: {noformat}java.nio.channels.ClosedChannelException at jenkins.agents.WebSocketAgents$Session.closed(WebSocketAgents.java:141) at jenkins.websocket.WebSocketSession.onWebSocketSomething(WebSocketSession.java:90) at com.sun.proxy.$Proxy118.onWebSocketClose(Unknown Source) at org.eclipse.jetty.websocket.common.events.JettyListenerEventDriver.onClose(JettyListenerEventDriver.java:119) at org.eclipse.jetty.websocket.common.WebSocketSession.callApplicationOnClose(WebSocketSession.java:389) at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.disconnect(AbstractWebSocketConnection.java:317) at org.eclipse.jetty.websocket.common.io.DisconnectCallback.succeeded(DisconnectCallback.java:42)[...]{noformat}
Add Comment
[JIRA] (JENKINS-61737) Parallel Build job propagates FAIL while running when child job UNSTABLE
Title: Message Title
Philipp Jung created an issue
Jenkins / JENKINS-61737
Parallel Build job propagates FAIL while running when child job UNSTABLE
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
after_run.png, during_run.png
Components:
blueocean-plugin, pipeline-build-step-plugin, workflow-cps-plugin
Created:
2020-03-30 08:26
Environment:
pipeline-build-step 2.12 workflow-cps 2.80 blueocean 1.22.0
Priority:
Minor
Reporter:
Philipp Jung
I have two Jenkins jobs, a parent job that triggers a child job with different configurations and runs these stages in parallel. When a child job has an UNSTABLE state, the parent job reports this stage as failed as long as the parent job is still running. When the parent job is finished all results are propagated as expected. Example to reproduce:
// Parent job
// With three stages with SUCCESS, UNSTABLE and FAILED stages
node(''){
def stage_map = [:]
stage_map['success'] = trigger('SUCCESS')
stage_map['unstable'] = trigger('UNSTABLE')
stage_map['failed'] = trigger('FAILED')
stage_map['sleep'] = trigger('SUCCESS', true)
parallel(stage_map)
}
def trigger(status, sleep = false){
return {
build job:
'test_child',
parameters: [
string(name: 'status', value: status),
booleanParam(name: 'sleep', value: sleep)
]
}
}
[JIRA] (JENKINS-61478) "Apply" (and similar) banners look really bad with larger header bar
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-61478 "Apply" (and similar) banners look really bad with larger header bar Change By: Daniel Beck Labels: lts-candidate regression ux 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.205161.1584140786000.2428.1585559580216%40Atlassian.JIRA.
[JIRA] (JENKINS-61478) "Apply" (and similar) banners look really bad with larger header bar
Title: Message Title Daniel Beck updated JENKINS-61478 Jenkins / JENKINS-61478 "Apply" (and similar) banners look really bad with larger header bar Change By: Daniel Beck Status: In Progress Review 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.205161.1584140786000.2432.1585559700354%40Atlassian.JIRA.
[JIRA] (JENKINS-61738) Session hijacking protection hardening
Title: Message Title Wadeck Follonier created an issue Jenkins / JENKINS-61738 Session hijacking protection hardening Issue Type: Improvement Assignee: Unassigned Components: core Created: 2020-03-30 09:15 Priority: Minor Reporter: Wadeck Follonier After the recent SECURITY-1774 published in https://jenkins.io/security/advisory/2020-03-25/, we are preventing the usage of semicolon in URL. In Jenkins they could potentially have a legitimate (but not really recommended) usage when included in item names. If you need to activate the escape hatch "jenkins.security.SuspiciousRequestFilter.allowSemicolonsInPath", and you are using a SecurityRealm that does not invalidate the session after authentication, you are vulnerable to a session hijacking attack. Of course, the SecurityRealm issue has to be reported as a vulnerability and then corrected. The problem is that you can trigger a URL in Jenkins with ";jsessionid=xxx" (only "available" in Tomcat). This ticket is about adding a "second" level of protection there (think defense in depth) by forcing the session to be tracked as a cookie (from default which is cookie+url). Add Comment
[JIRA] (JENKINS-61739) Handle project_rename System Hook event
Title: Message Title Vincent Letarouilly created an issue Jenkins / JENKINS-61739 Handle project_rename System Hook event Issue Type: Improvement Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2020-03-30 09:20 Environment: Jenkins 2.228 gitlab-branch-source-plugin 1.4.4 Labels: gitlab Priority: Minor Reporter: Vincent Letarouilly Hello, A great addition would be to handle project_rename system hook event. Currently the behavior is, upon manual scan, the project is duplicated and the old one is displaying as a simple Multibranch pipeline with no way to delete it. I have to delete and re-create the whole GitLab Group, and it triggers all branches for all projects which is very consuming when there's a lot of projects with a lot of branches. Add Comment
[JIRA] (JENKINS-61253) Remoting using WebSocket fails with "Handshake response not received" Exception
Title: Message Title ethorsa commented on JENKINS-61253 Re: Remoting using WebSocket fails with "Handshake response not received" Exception I've made a test on a Linux based Master (Jenkins v2.2221, Remoting v4.3, OpenJDK 11) with an agent configured as above but passing the arguments directly to remoting main(). The agent launches successfully, but it's marked as offline on the master. Remoting log (on Agent): hudson.remoting.jnlp.Main$CuiListener status INFO: WebSocket connection open hudson.remoting.jnlp.Main$CuiListener status INFO: Connected Agent log (Icon of the node): Inbound agent connected from Master Log: WARNING jenkins.agents.WebSocketAgents$Session error null java.io.IOException: Broken pipe at java.base/sun.nio.ch.FileDispatcherImpl.writev0(Native Method) at java.base/sun.nio.ch.SocketDispatcher.writev(SocketDispatcher.java:51) at java.base/sun.nio.ch.IOUtil.write(IOUtil.java:182) at java.base/sun.nio.ch.IOUtil.write(IOUtil.java:130) at java.base/sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:496) at org.eclipse.jetty.io.ChannelEndPoint.flush(ChannelEndPoint.java:263) Caused: org.eclipse.jetty.io.EofException at org.eclipse.jetty.io.ChannelEndPoint.flush(ChannelEndPoint.java:283) at org.eclipse.jetty.io.WriteFlusher.flush(WriteFlusher.java:422) at org.eclipse.jetty.io.WriteFlusher.write(WriteFlusher.java:277) at org.eclipse.jetty.io.AbstractEndPoint.write(AbstractEndPoint.java:381) at org.eclipse.jetty.websocket.common.io.FrameFlusher.flush(FrameFlusher.java:264) at org.eclipse.jetty.websocket.common.io.FrameFlusher.process(FrameFlusher.java:193) at org.eclipse.jetty.util.IteratingCallback.processing(IteratingCallback.java:241) at org.eclipse.jetty.util.IteratingCallback.iterate(IteratingCallback.java:223) at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.outgoingFrame(AbstractWebSocketConnection.java:584) at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.close(AbstractWebSocketConnection.java:181) at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillable(AbstractWebSocketConnection.java:511) at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillable(AbstractWebSocketConnection.java:441) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311) at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103) at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:336) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:313) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:171) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:129) at org.eclipse.jetty.util.thread.ReservedT
[JIRA] (JENKINS-61738) Session hijacking protection hardening
Title: Message Title Wadeck Follonier updated JENKINS-61738 Jenkins / JENKINS-61738 Session hijacking protection hardening Change By: Wadeck Follonier Status: In Progress Review 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.205567.1585559723000.2442.1585561320341%40Atlassian.JIRA.
[JIRA] (JENKINS-61738) Session hijacking protection hardening
Title: Message Title Wadeck Follonier started work on JENKINS-61738 Change By: Wadeck Follonier Status: Open In Progress 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.205567.1585559723000.2441.1585561320249%40Atlassian.JIRA.
[JIRA] (JENKINS-61738) Session hijacking protection hardening
Title: Message Title Wadeck Follonier assigned an issue to Wadeck Follonier Jenkins / JENKINS-61738 Session hijacking protection hardening Change By: Wadeck Follonier Assignee: Wadeck Follonier 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.205567.1585559723000.2447.1585561380331%40Atlassian.JIRA.
[JIRA] (JENKINS-61689) java.lang.NullPointerException when configuring JIRA site in Folder level
Title: Message Title Radek Antoniuk commented on JENKINS-61689 Re: java.lang.NullPointerException when configuring JIRA site in Folder level Yes, you are right, it seems that this is a bug at the moment. As this is a community plugin, feel feel free to give it a shot and contribute to fix this and open a Pull request - see some help here Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205512.158519371.2449.1585561680220%40Atlassian.JIRA.
[JIRA] (JENKINS-61740) since pull request #373 it not possible to set docker registry with groovy script
Title: Message Title
Laurent Hory created an issue
Jenkins / JENKINS-61740
since pull request #373 it not possible to set docker registry with groovy script
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2020-03-30 10:12
Environment:
Jenkins 2.204.5 Docker Pipeline 1.23 Pipeline 2.6 Pipeline: Declarative 1.6.0
Labels:
pipeline
Priority:
Major
Reporter:
Laurent Hory
since pull request https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/373 the GlobalConfig object are removed and the following code not work:
import org.jenkinsci.plugins.pipeline.modeldefinition.config.GlobalConfig;
import org.jenkinsci.plugins.docker.commons.credentials.DockerRegistryEndpoint;
import java.util.logging.Logger;
Logger logger = Logger.getLogger("pipeline-api-endpoint");
logger.info("about to add Docker Registry configuration");
GlobalConfig pipelineConfig = GlobalConfig.get();
DockerRegistryEndpoint registryConfig = new DockerRegistryEndpoint("{{ jenkins_docker_registry_host }}:{{ jenkins_docker_registry_port }}", "");
pipelineConfig.setRegistry(registryConfig);
pipelineConfig.save();
logger.info("added Docker Registry configuration");
I must downgrade pipeline declarative to 1.5.1 to avoid error in jenkins configuration.
[JIRA] (JENKINS-61740) since pull request #373 it is not possible to set docker registry with groovy script
Title: Message Title Laurent Hory updated an issue Jenkins / JENKINS-61740 since pull request #373 it is not possible to set docker registry with groovy script Change By: Laurent Hory Summary: since pull request #373 it is not possible to set docker registry with groovy script 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.205569.1585563122000.2453.1585563240158%40Atlassian.JIRA.
[JIRA] (JENKINS-35905) Add option to Fail the build if node label does not exist or if it cannot be provisioned within a timeout
Title: Message Title Amit Dar commented on JENKINS-35905 Re: Add option to Fail the build if node label does not exist or if it cannot be provisioned within a timeout I totally agree with Marcus Schulmann, sometimes there is a uniqe agent (with specific hardware, for instance) used for tests. I wonder what can we do in order to bump this issue's importance and handling? 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.171838.1465967113000.2455.1585564920474%40Atlassian.JIRA.
[JIRA] (JENKINS-60454) Jenkins.instance is missing after restart
Title: Message Title Wadeck Follonier updated JENKINS-60454 https://github.com/jenkinsci/jenkins/commit/ae99586fd048b8f4cf7faa9cdf9e82ff5283abf9 Jenkins / JENKINS-60454 Jenkins.instance is missing after restart Change By: Wadeck Follonier Status: In Review Resolved Resolution: Fixed Released As: 2.223 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received
[JIRA] (JENKINS-61688) Global build discarders configuration isn't loaded from disk
Title: Message Title Daniel Beck updated JENKINS-61688 Jenkins / JENKINS-61688 Global build discarders configuration isn't loaded from disk Change By: Daniel Beck Status: Fixed but Unreleased Resolved 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.205511.1585182181000.2478.1585567140778%40Atlassian.JIRA.
[JIRA] (JENKINS-61692) "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Title: Message Title Daniel Beck updated JENKINS-61692 Jenkins / JENKINS-61692 "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException Change By: Daniel Beck Status: Fixed but Unreleased Resolved 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.205516.1585227401000.2481.1585567140830%40Atlassian.JIRA.
[JIRA] (JENKINS-56643) hudson.Util.createSymlink is not atomic which means lastSuccessfulBuild updates are not atomic
Title: Message Title Daniel Beck resolved as Fixed Jenkins / JENKINS-56643 hudson.Util.createSymlink is not atomic which means lastSuccessfulBuild updates are not atomic Change By: Daniel Beck Status: Open Resolved Resolution: Fixed Released As: Jenkins 2.229 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.198274.1553112527000.2497.1585567201305%40Atlassian.JIRA.
[JIRA] (JENKINS-61426) Add / remove users from github team for our plugin
Title: Message Title Spotinst team assigned an issue to Unassigned Jenkins / JENKINS-61426 Add / remove users from github team for our plugin Change By: Spotinst team Assignee: Aharon Twizer 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.205098.158392566.2484.1585567200852%40Atlassian.JIRA.
[JIRA] (JENKINS-61409) Websocket connections crash if message size is greater than 64Kb
Title: Message Title Daniel Beck updated JENKINS-61409 Jenkins / JENKINS-61409 Websocket connections crash if message size is greater than 64Kb Change By: Daniel Beck Status: Fixed but Unreleased Resolved Released As: Jenkins 2.229 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.205063.1583801943000.2495.1585567201069%40Atlassian.JIRA.
[JIRA] (JENKINS-61455) Allow Jenkins.MANAGE user to access "About Jenkins"
Title: Message Title Daniel Beck updated JENKINS-61455 Jenkins / JENKINS-61455 Allow Jenkins.MANAGE user to access "About Jenkins" Change By: Daniel Beck Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.229 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.205134.1584015622000.2487.1585567200898%40Atlassian.JIRA.
[JIRA] (JENKINS-60866) Un-inlining JavaScript / CSS
Title: Message Title Daniel Beck started work on JENKINS-60866 Change By: Daniel Beck Status: Open In Progress 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.204240.1579952438000.2502.1585567260520%40Atlassian.JIRA.
[JIRA] (JENKINS-61426) Add / remove users from github team for our plugin
Title: Message Title Spotinst team updated an issue Jenkins / JENKINS-61426 Add / remove users from github team for our plugin Change By: Spotinst team Priority: Minor Major 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.205098.158392566.2499.1585567260397%40Atlassian.JIRA.
[JIRA] (JENKINS-61426) Add / remove users from github team for our plugin
Title: Message Title Spotinst team updated an issue Jenkins / JENKINS-61426 Add / remove users from github team for our plugin Change By: Spotinst team How can we add / remove github Users as committers for our plugin - spotinst-plugin ? 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.205098.158392566.2498.1585567260322%40Atlassian.JIRA.
[JIRA] (JENKINS-60866) Un-inlining JavaScript / CSS
Title: Message Title Daniel Beck assigned an issue to Wadeck Follonier Jenkins / JENKINS-60866 Un-inlining _javascript_ / CSS Change By: Daniel Beck Assignee: Wadeck Follonier 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.204240.1579952438000.2505.1585567320250%40Atlassian.JIRA.
[JIRA] (JENKINS-60921) Revisit base typography
Title: Message Title Daniel Beck commented on JENKINS-60921 Re: Revisit base typography Félix Queiruga Balado Is this finished with the change in Jenkins 2.226, or is more coming? 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.204318.1580393661000.2507.1585567320279%40Atlassian.JIRA.
[JIRA] (JENKINS-61741) Plugin Creation and Addition of Tags
Title: Message Title Mark Symons created an issue Jenkins / JENKINS-61741 Plugin Creation and Addition of Tags Issue Type: Improvement Assignee: Steve Springett Components: dependency-track-plugin Created: 2020-03-30 11:36 Priority: Minor Reporter: Mark Symons Dependency-Track Server allows projects to be provided with tags. This is a very useful way of slicing and dicing projects by team, customer, environment, etc. eg /projects/?tag=java It would be useful if the Jenkins Dependency-Track plugin supported the specification of tags. The ability to add an existing tag or to create and add a new tag might be best controlled by permissions, something requested in Dependency-Track Issue #586. For instance, I would prefer to see a build fail with a permissions issue (and a good error message) when attempting to use a tag that does not already exist in DT. The implementation should also support lowercasing of tags (see also Dependency-Track Issue #238 so that when JAVA is specified in the plugin, what is actually used in DT is java. Add Comment
[JIRA] (JENKINS-60921) Revisit base typography
Title: Message Title Félix Queiruga Balado commented on JENKINS-60921 Re: Revisit base typography More related changes may come in the future (hyperlinks) but there will be other tickets. 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.204318.1580393661000.2511.1585568220324%40Atlassian.JIRA.
[JIRA] (JENKINS-61734) Scan multibranch pipeline from Git does not discover origin/ branches
Title: Message Title FMC Novis commented on JENKINS-61734 Re: Scan multibranch pipeline from Git does not discover origin/ branches Hi, solved issue. I just added the option "Discover other refs" and typed * as filter in the Discover field. Thank you 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.205562.1585511472000.2514.1585568400078%40Atlassian.JIRA.
[JIRA] (JENKINS-61734) Scan multibranch pipeline from Git does not discover origin/ branches
Title: Message Title FMC Novis assigned an issue to FMC Novis Jenkins / JENKINS-61734 Scan multibranch pipeline from Git does not discover origin/ branches Change By: FMC Novis Assignee: FMC Novis 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.205562.1585511472000.2515.1585568400121%40Atlassian.JIRA.
[JIRA] (JENKINS-61734) Scan multibranch pipeline from Git does not discover origin/ branches
Title: Message Title FMC Novis updated JENKINS-61734 Just added the option "Discover other refs" in the Source repository options, and typed "*" in the field "Discover" Jenkins / JENKINS-61734 Scan multibranch pipeline from Git does not discover origin/ branches Change By: FMC Novis Status: Open Fixed but Unreleased Resolution: Fixed 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 jenkins
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Antonio Muñiz edited a comment on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script FTR: I'm hitting this with a "not - so - big" pipeline, ~800 lines, it includes a few separated stages:* Build on Linux (and unit tests)* Build on Windows (and unit tests)* QA (spotbugs, checkstyle, etc)* Security analysis* Integration tests* Release 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.174127.1473169024000.2604.1585568525151%40Atlassian.JIRA.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Antonio Muñiz commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script FTR: I'm hitting this with "not so big" pipeline, ~800 lines, it includes a few separated stages: Build on Linux (and unit tests) Build on Windows (and unit tests) QA (spotbugs, checkstyle, etc) Security analysis Integration tests Release 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.174127.1473169024000.2602.1585568525127%40Atlassian.JIRA.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Antonio Muñiz edited a comment on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script FTR: I'm hitting this with a "not-so-big" (and no matrix) pipeline, ~800 lines, it includes a few separated stages:* Build on Linux (and unit tests)* Build on Windows (and unit tests)* QA (spotbugs, checkstyle, etc)* Security analysis* Integration tests* Release 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.174127.1473169024000.2690.1585568581726%40Atlassian.JIRA.
[JIRA] (JENKINS-56376) remoting kakfa plugin creates too many threads and takes too much cpu time
Title: Message Title Mayur Kumar commented on JENKINS-56376 Re: remoting kakfa plugin creates too many threads and takes too much cpu time Hi Pham Vu Tuan, We have a disconnection issue over TCP and were looking at this plugin as a potential solution to the issue. Are there any plans on for fixing this issue, or is there anyone currently working on it? 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.197962.1551664275000.2777.1585569180195%40Atlassian.JIRA.
[JIRA] (JENKINS-60921) Revisit base typography
Title: Message Title Daniel Beck resolved as Fixed Jenkins / JENKINS-60921 Revisit base typography Change By: Daniel Beck Status: In Progress Resolved Resolution: Fixed Released As: Jenkins 2.226 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.204318.1580393661000.2779.1585570620497%40Atlassian.JIRA.
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Usama Tariq commented on JENKINS-58987 Re: issue_updated trigger handler can't find "name" field in JSON Hi Amrut, Sure. I will share if I found. 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.201336.1566200967000.2784.1585572480333%40Atlassian.JIRA.
[JIRA] (JENKINS-60454) Jenkins.instance is missing after restart
Title: Message Title GMC Software Development B&R Corporate updated an issue Jenkins / JENKINS-60454 Jenkins.instance is missing after restart Change By: GMC Software Development B&R Corporate Labels: lts-candidate 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.203532.1576121478000.2794.1585572720306%40Atlassian.JIRA.
[JIRA] (JENKINS-61742) host network not saved
Title: Message Title X Y created an issue Jenkins / JENKINS-61742 host network not saved Issue Type: Bug Assignee: Unassigned Components: kubernetes-plugin Created: 2020-03-30 13:16 Environment: Jenkins ver. 2.222.1 Kubernetes plugin 1.25.1 Priority: Blocker Reporter: X Y Hello, we're facing an issue while savin the pod template configuration details. Evrey time we set the flag "Host Network" and klick on save or apply button is seems to be saved but on a reload it is not set anymore. It has as well no effect. Add Comment
[JIRA] (JENKINS-61709) Map.get("${var}") returns null
Title: Message Title
Raphael Höser commented on JENKINS-61709
Re: Map.get("${var}") returns null
Just in case someone stumbles upon this: you can use map["key_${id}"] since this works fine. I created this issue, because I wanted to use get with a default parameter and the workaround is way more ugly with if tmp == null.
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.205534.1585316713000.2798.1585574340057%40Atlassian.JIRA.
[JIRA] (JENKINS-61475) Infinite loop in StandardGraphLookupView
Title: Message Title Joe Athman commented on JENKINS-61475 Re: Infinite loop in StandardGraphLookupView I believe we are running in to the same issue. We just started using version 2.204.6 and this began. 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.205156.1584114373000.2811.1585577520120%40Atlassian.JIRA.
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Steven Chaves commented on JENKINS-55287 Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head I don't have rights to zip my Build Job folder. 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.196374.1545361815000.2813.1585579441011%40Atlassian.JIRA.
[JIRA] (JENKINS-61735) Add STAGE_NAME and NODE_NAME to environment parameters
Title: Message Title Jakub Bochenski commented on JENKINS-61735 Re: Add STAGE_NAME and NODE_NAME to environment parameters I'm not sure what do you mean by "parent build" in the context of Jenkins pipeline 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.205563.1585515231000.2855.1585579680116%40Atlassian.JIRA.
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title
Devin Nusbaum updated an issue
Jenkins / JENKINS-55287
Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Change By:
Devin Nusbaum
*IMPORTANT: NOTE FROM A MAINTAINER:*+STOP! YOUR STACK TRACE ALONE IS NOT GOING TO HELP SOLVE THIS!+(sorry to all caps but we're not going to make progress on this issue with commenters adding insufficient information)*Note from maintainer: We'd like to be able to fix this, but we really need more information to do so. Please, whenever you encounter the error in the description of the ticket, zip the build folder ({{$JENKINS_HOME/jobs/$PATH_TO_JOB/builds/$BUILD_NUMBER/}}) of the build that failed and upload it here along with the Jenkins system logs , redacting any sensitive content as necessary, and include any relevant information on frequency of the issue, steps to reproduce (did it happen after Jenkins was restarted normally, or did Jenkins crash), any exceptions or warnings messages in the Jenkins system logs that seem relevant, etc. Thanks!* {noformat}Creating placeholder flownodes because failed loading originals.java.io.IOException: Tried to load head FlowNodes for execution Owner[Platform Service FBI Test/1605:Platform Service FBI Test #1605] but FlowNode was not found in storage for head id:FlowNodeId 1:17 at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.initializeStorage(CpsFlowExecution.java:678) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad(CpsFlowExecution.java:715) at org.jenkinsci.plugins.workflow.job.WorkflowRun.getExecution(WorkflowRun.java:659) at org.jenkinsci.plugins.workflow.job.WorkflowRun.onLoad(WorkflowRun.java:525) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:57) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:499) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:481) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:379) at hudson.model.RunMap.getById(RunMap.java:205) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.run(WorkflowRun.java:896) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.get(WorkflowRun.java:907) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:65) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:57) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl.onLoaded(FlowExecutionList.java:178) at jenkins.model.Jenkins.(Jenkins.java:975) at hudson.model.Hudson.(Hudson.java:85) at hudson.model.Hudson.(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:233)Finished: FAILURE{noformat}
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Falko Modler commented on JENKINS-55287 Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head Devin Nusbaum & Liam Newman I have three zipped build folders (all from around the same time, March 12th) but did not yet have the time ro redact sensitive data. Do you have some hints what and where to look for (regarding sensitive data)? 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.196374.1545361815000.2899.1585580160957%40Atlassian.JIRA.
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Falko Modler edited a comment on JENKINS-55287 Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head [~dnusbaum] & [~bitwiseman]I have three zipped build folders (all from around the same time, March 12th) but did not yet have the time ro to redact sensitive data. Do you have some hints what and where to look for (regarding sensitive data)? 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.196374.1545361815000.2941.1585580220862%40Atlassian.JIRA.
[JIRA] (JENKINS-61253) Remoting using WebSocket fails with "Handshake response not received" Exception
Title: Message Title Jeff Thompson commented on JENKINS-61253 Re: Remoting using WebSocket fails with "Handshake response not received" Exception Try Remoting (agent) 4.2. You're experiencing the fun of being on the bleeding edge. The WebSocket implementation is still in Beta, because we need to get extended real-world testing. It first came out in an LTS release last week, with Remoting 4.2. Unfortunately, at the same time someone reported a problem with large payloads, which we fixed last week. Remoting 4.3 addresses that problem, but, because it's still in Beta, also requires an upgrade to the master, Jenkins 2.229. That fix should get merged back to the next Jenkins LTS refresh. Remoting 4.2: Weekly releases 2.217 through 2.228 LTS release 2.222.1 Remoting 4.3: Weekly releases 2.229+ Upcoming LTS If you're not using the experimental WebSocket feature, then Remoting 4.2 and 4.3 are equivalent. 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.204820.1582797002000.2986.1585580820129%40Atlassian.JIRA.
[JIRA] (JENKINS-61713) Improve tests for PitScore (in PitScoreTest)
Title: Message Title Kevin Richter started work on JENKINS-61713 Change By: Kevin Richter Status: Open In Progress 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.205539.1585329712000.2998.1585581300319%40Atlassian.JIRA.
[JIRA] (JENKINS-61713) Improve tests for PitScore (in PitScoreTest)
Title: Message Title Kevin Richter assigned an issue to Kevin Richter Jenkins / JENKINS-61713 Improve tests for PitScore (in PitScoreTest) Change By: Kevin Richter Assignee: Kevin Richter 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.205539.1585329712000.2996.1585581300257%40Atlassian.JIRA.
[JIRA] (JENKINS-61743) Customizable workspace and working directory of docker.images.inside()
Title: Message Title Mart Rich created an issue Jenkins / JENKINS-61743 Customizable workspace and working directory of docker.images.inside() Issue Type: New Feature Assignee: Unassigned Attachments: example.txt, proposal.txt Components: docker-workflow-plugin Created: 2020-03-30 15:19 Priority: Major Reporter: Mart Rich Hello, I want to have a possibility to change the "workdir" & "volume" destination directory within the image which will be started by the "docker.image.inside"-command. The current problem is that the path to the mount-destination within the container and the working directory are hard-coded: Hard-coded volumes: https://github.com/jenkinsci/docker-workflow-plugin/blob/master/src/main/java/org/jenkinsci/plugins/docker/workflow/WithContainerStep.java#L193 https://github.com/jenkinsci/docker-workflow-plugin/blob/master/src/main/java/org/jenkinsci/plugins/docker/workflow/WithContainerStep.java#L194 Hard-coded Work-Dir (parameter 4 is always "ws" == "workspace"): https://github.com/jenkinsci/docker-workflow-plugin/blob/master/src/main/java/org/jenkinsci/plugins/docker/workflow/WithContainerStep.java#L198 So the "default" image.inside command (on windows) results in something like:
[JIRA] (JENKINS-61744) Remote file plugin should allow to use folders or wildcards as marker files
Title: Message Title AndreY Hura created an issue Jenkins / JENKINS-61744 Remote file plugin should allow to use folders or wildcards as marker files Issue Type: Improvement Assignee: Aytunc BEKEN Components: remote-file-plugin Created: 2020-03-30 15:52 Environment: Any Priority: Minor Reporter: AndreY Hura The current version of the plugin allows to use only one single file as a project recognizer marker. It would be good to have the option to provide a folder name or a wildcard for file names under the folder Add Comment
[JIRA] (JENKINS-61745) Scan multibranch with date range or dop '@now'
Title: Message Title Karl Wirth created an issue Jenkins / JENKINS-61745 Scan multibranch with date range or dop '@now' Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2020-03-30 15:53 Environment: p4-plugin 1.10.9 Priority: Blocker Reporter: Karl Wirth When scanning for changes in multibranch pipelines we use p4 changes -m1 //Path/...@now. This is triggering a similar resource behavior to: JENKINS-57870 For example with a big dataset in the multibranch scan log we see: p4 changes -m1 //Path/branch/...@now Request too large (over 50); see 'p4 help maxresults'. ERROR: [Mon Mar 30 13:07:05 CEST 2020] Could not fetch branches from source d5fe37f7-6c40-4111-af23-d4f539fec120 com.perforce.p4java.exception.RequestException: Request too large (over 50); see 'p4 help maxresults'. When checking this at the command line we see that limiting the query or dropping '@now' works: $ p4 changes -m1 //path/branch/...@now Request too large (over 50); see 'p4 help maxresults'.$ p4 changes -m1 //path/branch/...@2020/03/30 Request too large (over 50); see 'p4 help maxresults'.$ p4 changes -m1 //path/branch/... Change 62552 on 2020/03/30 by user@PC1 'CL Description'$ p4 changes -m1 //path/branch/...@52552,62552 Change 62552 on 2020/03/30 by user@PC1 'CL Description
[JIRA] (JENKINS-61745) Scan multibranch with date range or dop '@now'
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-61745 Scan multibranch with date range or dop '@now' Change By: Karl Wirth Environment: p4-plugin 1. 10. 1. 9 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.205574.1585583601000.3003.1585583760110%40Atlassian.JIRA.
[JIRA] (JENKINS-61745) Scan multibranch with date range or dop '@now'
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-61745 Scan multibranch with date range or dop '@now' Change By: Karl Wirth Labels: P4_VERIFY 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.205574.1585583601000.3004.1585583760157%40Atlassian.JIRA.
[JIRA] (JENKINS-51092) Two Factor Auth in Github Breaks Authentication for Github Organization
Title: Message Title kusuma t commented on JENKINS-51092 Re: Two Factor Auth in Github Breaks Authentication for Github Organization Hi, From Jenkins when we use HTTPS to connect to GitHub using Username/Password option is failing. And from the Github documentation it is mentioned that Authenticating on the command line using HTTPS After you've enabled 2FA, you must create a personal access token to use as a password when authenticating to GitHub on the command line using HTTPS URLs. When prompted for a username and password on the command line, use your GitHub username and personal access token. The command line prompt won't specify that you should enter your personal access token when it asks for your password. Can you point to exact document if we can access HTTPS/SSH using 2FA without Personal access token Thanks, Kusuma 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.190379.1525293379000.3006.1585583820255%40Atlassian.JIRA.
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Devin Nusbaum commented on JENKINS-55287 Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head I was looking into this issue recently and wanted to check whether the code that saves Pipelines using the PERFORMANCE_OPTIMIZED durability level when Jenkins is shutting down (CpsFlowExecution.suspendAll) is running successfully in these cases to make sure that the problem isn't something like the service configuration for Jenkins not giving it enough time to shut down. For users seeing the problem, please check the Jenkins system logs for the shutdown that occurred before you saw this error. Do you see messages similar to these, in particular for the build that failed with the exception in the description of this ticket? About to try to checkpoint the program for buildCpsFlowExecutionOwner[YourJobName/BuildNumber:YourJobName #BuildNumber]] Trying to save program before shutdown org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$8@RandomHash Finished saving program before shutdown org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$8@RandomHash Those messages should come in groups of three, in that order, and are logged at INFO level, and there should not be any WARNING messages interspersed between them or surrounding them. There should be a set of those messages for each Pipeline running using the PERFORMANCE_OPTIMIZED durability level when Jenkins shuts down. If you have configured Jenkins to run as a service, I would also check the service logs to see if Jenkins has been shutting down successfully or if there are any warnings/errors when Jenkins shuts down. Falko Modler It depends on what your builds are doing and what you consider sensitive. The main files to check are build.xml, which contains a textual form of the Pipeline, and log, which contains the build logs. You might want to check for internal hostnames or IP addresses, unmasked passwords or API keys in your build log, etc. Add Comment
[JIRA] (JENKINS-61744) Remote file plugin should allow to use folders or wildcards as marker files
Title: Message Title Andrey Hura updated an issue Jenkins / JENKINS-61744 Remote file plugin should allow to use folders or wildcards as marker files Change By: Andrey Hura Component/s: multibranch-action-triggers-plugin 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.205573.158558355.3056.1585584240153%40Atlassian.JIRA.
[JIRA] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service
Title: Message Title yao wei commented on JENKINS-20356 Re: Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service Ilguiz Latypov Thanks for the update! I tried, my git.exe is also blocked by Cp protection. Thank! 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.151876.1383181122000.3058.1585584540439%40Atlassian.JIRA.
[JIRA] (JENKINS-61746) Jira-Trigger-Plugin - JSONException
Title: Message Title Corentin Jézéquel created an issue Jenkins / JENKINS-61746 Jira-Trigger-Plugin - JSONException Issue Type: Bug Assignee: Wisen Tanasa Components: jira-trigger-plugin Created: 2020-03-30 16:09 Environment: jira-trigger-plugin: 1.0.0 jira 8.8.0 jenkins 2.222.1 xray 3.6.4 Labels: plugin Priority: Critical Reporter: Corentin Jézéquel Hello team, I integrated the jenkins to jira for automated testing. but now I'm faced with the problem that it doesn't trigger automatic deployment. I saw that there were similar errors, however, I also use Xray, and the key that triggers the JSON exception is different. Please find the attached jenkins journal. Have a good day, Corentin 2020-03-30 15:25:53.887+ [id=411] WARNING o.e.j.s.h.ContextHandler$Context#log: Error while serving http://172.17.0.3:8080/jira-trigger-webhook-receiver/ org.codehaus.jettison.json.JSONException: JSONObject["issue"] not found. at org.codehaus.jettison.json.JSONObject.get(JSONObject.java:360) at org.codehaus.jettison.json.JSONObject.getJSONObject(JSONObject.java:454) at org.codehaus.jettison.json.JSONObject$getJSONObject.call(Unknown Source) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.WebhookJsonParserUtils.satisfyRequiredKeys(WebhookJsonParserUtils.groovy:14) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.WebhookJsonParserUtils$satisfyRequiredKeys.callStatic(Unknown Source)
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Jesse Glick commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Antonio Muñiz Scripted? (or “Declarative” with script blocks?) It is unknown whether a general fix is feasible for Scripted. Would likely require a redesign of the CPS transformer, which is possible in principle but this is one of the most difficult areas of Jenkins to edit. 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.174127.1473169024000.3078.1585584721975%40Atlassian.JIRA.
[JIRA] (JENKINS-61744) Remote file plugin should allow to use folders or wildcards as marker files
Title: Message Title Andrey Hura commented on JENKINS-61744 Re: Remote file plugin should allow to use folders or wildcards as marker files Is it possible to filter file/folder names a way other than defined here? https://github.com/jenkinsci/remote-file-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/multibranch/extended/scm/LocalFileSCMSourceCriteria.java 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.205573.158558355.3166.1585585020115%40Atlassian.JIRA.
[JIRA] (JENKINS-61747) Do not write the SP metadata with every login
Title: Message Title Ivan Fernandez Calvo created an issue Jenkins / JENKINS-61747 Do not write the SP metadata with every login Issue Type: Improvement Assignee: Ivan Fernandez Calvo Components: saml-plugin Created: 2020-03-30 16:18 Priority: Minor Reporter: Ivan Fernandez Calvo The SP metadata is written on every login, it is a little exaggerated, take a look if we can write it when the configuration is made. https://github.com/jenkinsci/saml-plugin/blob/master/src/main/java/org/jenkinsci/plugins/saml/OpenSAMLWrapper.java#L149 Add Comment
[JIRA] (JENKINS-55038) `Parameterized Remote Trigger Plugin` sometimes fails with poll interval value more than 5 minutes
Title: Message Title Nick Korsakov commented on JENKINS-55038 Re: `Parameterized Remote Trigger Plugin` sometimes fails with poll interval value more than 5 minutes KaiHsiang Chang, thanks for fast code review. Can we close the issue? 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.196080.1544027892000.3170.1585585140345%40Atlassian.JIRA.
[JIRA] (JENKINS-61370) EC2 instances are terminated during launch
Title: Message Title Jakub Bochenski commented on JENKINS-61370 Re: EC2 instances are terminated during launch After changing to "SSH process" connection method I was able to see additional errors, which are swallowed by the Trilead java connector. Exception in thread "main" java.nio.file.AccessDeniedException: /opt/jenkins at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileSystemProvider.createDirectory(UnixFileSystemProvider.java:384) at java.nio.file.Files.createDirectory(Files.java:674) at java.nio.file.Files.createAndCheckIsDirectory(Files.java:781) at java.nio.file.Files.createDirectories(Files.java:767) at org.jenkinsci.remoting.engine.WorkDirManager.initializeWorkDir(WorkDirManager.java:211 Turns out that if you mount a block device in user-data script it can sometimes not be available when the master SSH connection comes in. The solution seems to be to use the init-script instead. 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
[JIRA] (JENKINS-53649) Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable
Title: Message Title
Andreas Meyer commented on JENKINS-53649
Re: Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable
I believe this is one of the little bugs that are not really serious but still would make many people happy when fixed, because it is so annoying. I've found a generic workaround that doesn't use a shell step, so it's much more efficient. The trick is to temporarily clear the EnvVars for the duration of the "echo" call. DISCLAIMER: This workaround disables the masking of secrets during the echo call, so use it at your own risk and especially don't use it within "withCredentials" scope! If anyone has an idea to prevent this issue, please reply. We could propably call "getContext" to detect any "withCredentials" context and fallback to plain "echo" in this case. I could live with an occassional "Print Message" in "withCredentials" scopes. Unfortunately "getContext" prints a message on its own, so it's not very useful . Sample code:
pipeline{
agent any
environment {
MY_ENV1 = 'foobarbaz'
}
parameters {
string(name: 'MY_PARAM', defaultValue: 'bazbarfoo')
}
stages {
stage('test') {
steps {
script {
env.MY_ENV2 = 'foobazbar'
withEnv(['MY_ENV3=bazfoobar']) {
// Any of the resolved variable values trigger the "Print message" of plain echo
def msg = "MY_ENV1=$MY_ENV1, MY_ENV2=$MY_ENV2, MY_ENV3=$MY_ENV3, MY_PARAM=$MY_PARAM"
echo "echo: $msg"// Displays "Print Message" as the step label
myecho "myecho: $msg"// Displays the message as the step label, as expected
}
}
}
}
}
}
// Workaround for "Print message" that is displayed by original echo step if the message
// contains a value of an environment variable or a pipeline parameter.
//
// WARNING: This disables masking of secrets in the output, so don't call it within witCredentials{} scope!
void myecho( String msg ) {
withContext( new MyEnvClearer() ) {
echo msg
}
}
// Clears all environment variables, to be used from withContext{}.
class MyEnvClearer extends org.jenkinsci.plugins.workflow.steps.EnvironmentExpander {
@NonCPS
void expand( hudson.EnvVars env ) throws IOException, InterruptedException {
env.clear()
}
}
Add Comment
[JIRA] (JENKINS-61743) Customizable workspace and working directory of docker.images.inside()
Title: Message Title tharilya updated an issue Jenkins / JENKINS-61743 Customizable workspace and working directory of docker.images.inside() Change By: tharilya Attachment: proposal.txt 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.205572.1585581551000.3200.1585587480243%40Atlassian.JIRA.
[JIRA] (JENKINS-61743) Customizable workspace and working directory of docker.images.inside()
Title: Message Title tharilya updated an issue Jenkins / JENKINS-61743 Customizable workspace and working directory of docker.images.inside() Change By: tharilya Attachment: proposal.txt 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.205572.1585581551000.3199.1585587480116%40Atlassian.JIRA.
[JIRA] (JENKINS-55719) Allow to configure the git blame command to suppress whitespace changes
Title: Message Title Timothy Brackett commented on JENKINS-55719 Re: Allow to configure the git blame command to suppress whitespace changes Since newer versions of git allow one to ignore specific sha's (Reference), perhaps this could be opened up to allowing arbitrary `git blame` arguments? Probably out-of-scope for this issue and requires a new issue, but for Git 2.23 and forward, maybe add configuration options specifically for `-ignore-rev` and `-ignore-revs-file`. 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.196913.1548140301000.3211.1585595040157%40Atlassian.JIRA.
[JIRA] (JENKINS-38679) Constant builds when svn url contains parameter
Title: Message Title
Morten Breum commented on JENKINS-38679
Re: Constant builds when svn url contains parameter
I observe the same issue, and I agree with Ben M's comment. My polling log continuously says (base URL replaced)
Started on Mar 30, 2020 5:38:00 PM
Workspace doesn't contain https:///products/product_a/${CODE_REPO_SUB_LOC}. Need a new build.
Workspace doesn't contain https:///products/product_a/${CODE_REPO_SUB_LOC}. Need a new build.
Done. Took 0 ms
Changes found
My svn repository contains products/product_a/trunk/ and products/product_a/trunk/tags/1.0.0. There is no difference between building trunk and a tag, so there is one job, Build_ProductA, to do that. That job is invoked from either:
job Release_ProductA with the parameter CODE_REPO_SUB_LOC set to /tags/1.0.0 And the build output is uploaded to a public nexus server
job Snapshot_ProductA with the parameter CODE_REPO_SUB_LOC set to /trunk And the build output is uploaded to a private stash
SCM polling with the parameter set to /trunk (from default)
Because of this bug, I have to have an extra separate job to avoid building when there are no changes.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61515) Git SCM polling fails with skipDefaultCheckout() in pipeline
Title: Message Title Matt G commented on JENKINS-61515 Re: Git SCM polling fails with skipDefaultCheckout() in pipeline In #1, I set it up with a regular (1 minute) polling interval. Then I built the project manually by clicking 'Build now'. I did not use notifyCommit or 'Poll Now'. New changes pushed to the repository never get detected. The polling log timestamps do update, but it never executes any Git commands; it just says no changes detected. 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.205211.1584564029000.3236.1585597680132%40Atlassian.JIRA.
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-55287
Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head
I was looking into this issue recently and wanted to check whether the code that saves Pipelines using the PERFORMANCE_OPTIMIZED durability level when Jenkins is shutting down ([CpsFlowExecution.suspendAll|https://github.com/jenkinsci/workflow-cps-plugin/blob/e8d4c696277a044a808380bab6c6c7b06ef6cab9/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java#L1572]) is running successfully in these cases to make sure that the problem isn't something like the service configuration for Jenkins not giving it enough time to shut down.For users seeing the problem, please check the Jenkins system logs for the shutdown that occurred before you saw this error. Do you see messages similar to these, in particular for the build that failed with the exception in the description of this ticket? * About to try to checkpoint the program for buildCpsFlowExecution \ [Owner \ [YourJobName/BuildNumber:YourJobName #BuildNumber] |#BuildNumber ] ] * Trying to save program before shutdown org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$8@RandomHash * Finished saving program before shutdown org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$8@RandomHashThose messages should come in groups of three, in that order, and are logged at INFO level, and there should not be any WARNING messages interspersed between them or surrounding them. There should be a set of those messages for each Pipeline running using the PERFORMANCE_OPTIMIZED durability level when Jenkins shuts down. If you have configured Jenkins to run as a service, I would also check the service logs to see if Jenkins has been shutting down successfully or if there are any warnings/errors when Jenkins shuts down.[~famod] It depends on what your builds are doing and what you consider sensitive. The main files to check are {{build.xml}}, which contains a textual form of the Pipeline, and {{log}}, which contains the build logs. You might want to check for internal hostnames or IP addresses, unmasked passwords or API keys in your build log, etc.
Add Comment
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title
Dmytro Kryvenko commented on JENKINS-37984
Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
I've said this before in this thread, but as I keep getting notifications about new comments in this issue from people who refuse to admin their pipelines design sucks - I have prepared this detailed walkthrough. Using this technique, I've been able to run 100 stages in both scripted and declarative mode before I'm hitting this issue. I didn't tried the workaround by Liam Newman which might improve Declarative one even further. I want to emphasize on the fact if you are having even half of that many stages - you are doing CICD wrong. You need to fix your process. Jenkins just happens to be a first bottleneck you've faced down that path. That discussion can get really philosophical as we will need to properly redefine what's CI and what's CD, what is a Pipeline and why Jenkins is not a Cron with web-interface. I really have no desire to be doing it here. Exception might be matrix jobs, but, even then I'm not so sure though I admit there might be a valid use case with that many stages in that space. But even then - execute your scripted pipeline in chunks (details below) - and there is no limits at all, I've been able to run a pipeline with 1 stages! Thought then my Jenkins fails to render that many stages in UI. But more on that later. Now, getting into the right way of doing Jenkins. First and foremost - your Jenkinsfile, no matter where it stored, must be small and simple. It doesn't have to tell WHAT to do, nor define any stages. All that is implementation details that you want to hide from your users. An example of such a Jenkinsfile:
library 'method-code-too-large-demo'
loopStagesScripted(100)
Note it doesn't matter if you're going to use scripted or declarative pipelines at this point. Here, you just collecting a user input. In my example I have just one - a number that defines how many stages I want in my pipeline. In real world example it might be any input you need from the user - type of project, platform version, any package/dependency details, etc. Just collect that input in any form and shape you want and pass it to your library. In my example a demo library lives here https://github.com/llibicpep/method-code-too-large-demo and loopStagesScripted is a step I have defined in it. Now, it is up to the library to read the user input, do whatever calculations, and generate your pipeline on the fly and then execute it. But the trick is - the pipeline is just a skeleton, defines the stages and does not actually performs any steps. For the steps it will fall back to the library again. Resulting pipeline from that Jenkinsfile will be looking like this:
stage('Stage 1') {
podTemplate(yaml: getPod(1)) {
node(POD_LABEL) {
doSomethingBasedOnStageNameOrWhatever(1)
}
}
}
stage('Stage 2') {
podTemplate(yaml: getPod(2)) {
node(POD_LABEL) {
doSomethingBasedOnStageNameOrWhatever(2)
}
}
}
...
[JIRA] (JENKINS-61515) Git SCM polling fails with skipDefaultCheckout() in pipeline
Title: Message Title Matt G updated an issue Jenkins / JENKINS-61515 Git SCM polling fails with skipDefaultCheckout() in pipeline Change By: Matt G Attachment: config.xml Attachment: Jenkinsfile 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.205211.1584564029000.3366.1585598460374%40Atlassian.JIRA.
[JIRA] (JENKINS-61515) Git SCM polling fails with skipDefaultCheckout() in pipeline
Title: Message Title Matt G edited a comment on JENKINS-61515 Re: Git SCM polling fails with skipDefaultCheckout() in pipeline In #1, I set it up with a regular (1 minute) polling interval. Then I built the project manually by clicking 'Build now'. I did not use notifyCommit or 'Poll Now'. New changes pushed to the repository never get detected. The polling log timestamps do update, but it never executes any Git commands; it just says no changes detected. I've attached the relevant config.xml for the job and the Jenkinsfile from the repository in question so you can see exactly how it is set up to reproduce the issue. 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.205211.1584564029000.3368.1585598520143%40Atlassian.JIRA.
[JIRA] (JENKINS-61515) Git SCM polling fails with skipDefaultCheckout() in pipeline
Title: Message Title Matt G commented on JENKINS-61515 Re: Git SCM polling fails with skipDefaultCheckout() in pipeline This is what the polling log looks like, even when I know new changes were pushed to the repository: Started on Mar 30, 2020, 12:57:00 PM Done. Took 1 ms No changes 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.205211.1584564029000.3370.1585598580099%40Atlassian.JIRA.
[JIRA] (JENKINS-61726) Nexus Platform plugin fail to connect to the Nexus 2 repository Server
Title: Message Title Justin Young commented on JENKINS-61726 Re: Nexus Platform plugin fail to connect to the Nexus 2 repository Server This appears to be a configuration error. The docker container with Jenkins is not the same machine as the container with NXRM and therefore localhost will not route as expected. Dependent on the host there are various networking approaches such that containers can communicate with each other. See https://docs.docker.com/docker-for-mac/networking/#use-cases-and-workarounds 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.205553.1585357996000.3373.1585599840201%40Atlassian.JIRA.
[JIRA] (JENKINS-44466) Allow plugins to override aspects of the Blue Ocean theme
Title: Message Title Karl Parry commented on JENKINS-44466 Re: Allow plugins to override aspects of the Blue Ocean theme We use Jenkins in the same ways as Brandon Fryslie with different Banner colours per environment (mostly just red banner for Production). As the default view is still the legacy UI it is not a concern for us yet but definitely a nice v2 feature. 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.182294.1495611527000.3379.1585608060307%40Atlassian.JIRA.
[JIRA] (JENKINS-61493) Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist
Title: Message Title Rick Landon commented on JENKINS-61493 Re: Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist While this is being sorted out, does anyone have a suggested workaround? 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.205179.1584360231000.3388.1585611120389%40Atlassian.JIRA.
[JIRA] (JENKINS-61748) Trying to use PriorityQueue.add with custom classes winds up catching CustomClass.compareTo in scripted pipelines
Title: Message Title
Ryan Fenton-Garcia created an issue
Jenkins / JENKINS-61748
Trying to use PriorityQueue.add with custom classes winds up catching CustomClass.compareTo in scripted pipelines
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-cps-plugin
Created:
2020-03-30 23:40
Environment:
Windows Server 2016 Jenkins: 2.204.5 Pipeline: 2.6
Labels:
pipeline workflow-cps-plugin java queue
Priority:
Minor
Reporter:
Ryan Fenton-Garcia
I'm attempting to make use of the native Java priority queue in a pipeline job by defining the following custom class
class PriorityClosure implements Comparable {
int priority
Closure closure
int compareTo(PriorityClosure o) { priority <=> o?.priority }
PriorityClosure(priority, closure) {
this.priority = priority
this.closure = closure
}
}
and then attempting to run the following function
def someFunction() {
def testQueue = new PriorityQueue()
for (int i = 0; i < 23; i++) {
int staticIteratorReference = i
testQueue.add(new PriorityClosure(
staticIteratorReference,
{
println "this is a te
[JIRA] (JENKINS-61748) Trying to use PriorityQueue.add with custom classes winds up catching CustomClass.compareTo in scripted pipelines
Title: Message Title
Ryan Fenton-Garcia updated an issue
Jenkins / JENKINS-61748
Trying to use PriorityQueue.add with custom classes winds up catching CustomClass.compareTo in scripted pipelines
Change By:
Ryan Fenton-Garcia
I'm attempting to make use of the native Java priority queue in a pipeline job by defining the following custom class {code:java} import java.lang.Comparable class PriorityClosure implements Comparable { int priority Closure closure int compareTo(PriorityClosure o) { priority <=> o?.priority } PriorityClosure(priority, closure) {this.priority = prioritythis.closure = closure }}{code}and then attempting to run the following function{code:java} import def someFunction() { def testQueue = new PriorityQueue() for (int i = 0; i < 23; i++) {int staticIteratorReference = itestQueue.add(new PriorityClosure( staticIteratorReference, {println "this is a test" })) } println "Test Queue is: ${testQueue}"}{code} I would expect to get a priority queue with all of my stuff in it, but instead, checking the output console, I receive the following:{code:java}[2020-03-30T23:13:51.564Z] expected to call java.util.PriorityQueue.add but wound up catching PriorityClosure.compareTo; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/[2020-03-30T23:13:51.564Z] expected to call java.util.PriorityQueue.add but wound up catching PriorityClosure.compareTo; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/[2020-03-30T23:13:51.564Z] expected to call java.util.PriorityQueue.add but wound up catching PriorityClosure.compareTo; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/[2020-03-30T23:13:51.564Z] expected to call java.util.PriorityQueue.add but wound up catching PriorityClosure.compareTo; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/[2020-03-30T23:13:51.564Z] expected to call java.util.PriorityQueue.add but wound up catching PriorityClosure.compareTo; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/[2020-03-30T23:13:51.564Z] expected to call java.util.PriorityQueue.add but wound up catching PriorityClosure.compareTo; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/[2020-03-30T23:13:51.564Z] expected to call java.util.PriorityQueue.add but wound up catching PriorityClosure.compareTo; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/[2020-03-30T23:13:51.564Z] expected to call java.util.PriorityQueue.add but wound up catching PriorityClosure.compareTo; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/[2020-03-30T23:13:51.564Z] expected to call java.util.PriorityQueue.add but wound up catching PriorityClosure.compareTo; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/[2020-03-30T23:13:51.564Z] expected to call java.util.PriorityQueue.add but wound up catching PriorityClosure.compareTo; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/[2020-03-30T23:13:51.564Z] expected to call java.util.PriorityQue
[JIRA] (JENKINS-61748) Trying to use PriorityQueue.add with custom classes winds up catching CustomClass.compareTo in scripted pipelines
Title: Message Title
Ryan Fenton-Garcia updated an issue
Jenkins / JENKINS-61748
Trying to use PriorityQueue.add with custom classes winds up catching CustomClass.compareTo in scripted pipelines
Change By:
Ryan Fenton-Garcia
I'm attempting to make use of the native Java priority queue in a pipeline job by defining the following custom class {code:java}import java.lang.Comparableclass PriorityClosure implements Comparable { int priority Closure closure int compareTo(PriorityClosure o) { priority <=> o?.priority } PriorityClosure(priority, closure) {this.priority = prioritythis.closure = closure }}{code}and then attempting to run the following function{code:java}importjava.util.PriorityQueue def someFunction() { def testQueue = new PriorityQueue() for (int i = 0; i < 23; i++) {int staticIteratorReference = itestQueue.add(new PriorityClosure( staticIteratorReference, {println "this is a test" })) } println "Test Queue is: ${testQueue}"}{code}I would expect to get a priority queue with all of my stuff in it, but instead, checking the output console, I receive the following:{code:java}[2020-03-30T23:13:51.564Z] expected to call java.util.PriorityQueue.add but wound up catching PriorityClosure.compareTo; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/[2020-03-30T23:13:51.564Z] expected to call java.util.PriorityQueue.add but wound up catching PriorityClosure.compareTo; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/[2020-03-30T23:13:51.564Z] expected to call java.util.PriorityQueue.add but wound up catching PriorityClosure.compareTo; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/[2020-03-30T23:13:51.564Z] expected to call java.util.PriorityQueue.add but wound up catching PriorityClosure.compareTo; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/[2020-03-30T23:13:51.564Z] expected to call java.util.PriorityQueue.add but wound up catching PriorityClosure.compareTo; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/[2020-03-30T23:13:51.564Z] expected to call java.util.PriorityQueue.add but wound up catching PriorityClosure.compareTo; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/[2020-03-30T23:13:51.564Z] expected to call java.util.PriorityQueue.add but wound up catching PriorityClosure.compareTo; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/[2020-03-30T23:13:51.564Z] expected to call java.util.PriorityQueue.add but wound up catching PriorityClosure.compareTo; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/[2020-03-30T23:13:51.564Z] expected to call java.util.PriorityQueue.add but wound up catching PriorityClosure.compareTo; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/[2020-03-30T23:13:51.564Z] expected to call java.util.PriorityQueue.add but wound up catching PriorityClosure.compareTo; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/[2020-03-30T23:13:51.564Z] expected to cal
[JIRA] (JENKINS-61315) Add documentation for declarative pipeline support.
Title: Message Title Martin Henschke commented on JENKINS-61315 Re: Add documentation for declarative pipeline support. Hi Tim, thanks for the report. If I understand your report correctly, you want Bitbucket Server to perform a merge on your PR branch without modifying the target branch, and having that build status used as the condition for your merge check. Unfortunately, this is a limitation in Bitbucket Server rather than in Jenkins- the plugin will register a build against the commit on the target branch rather than a merged commit, and that is used for the merge check instead. We do not provide any in-product support for build statuses against a merge build of a PR before it has been merged. Based on this however, I feel this is not specifically an issue with the Jenkins plugin documentation, so I will close this ticket for now. Please feel to follow up if you have any further questions. 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.204901.1583274613000.3393.1585613160224%40Atlassian.JIRA.
[JIRA] (JENKINS-61315) Add documentation for declarative pipeline support.
Title: Message Title Martin Henschke closed an issue as Not A Defect Jenkins / JENKINS-61315 Add documentation for declarative pipeline support. Change By: Martin Henschke Status: Open Closed Resolution: Not A Defect 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.204901.1583274613000.3397.1585613280351%40Atlassian.JIRA.
[JIRA] (JENKINS-61315) Add documentation for declarative pipeline support.
Title: Message Title Martin Henschke edited a comment on JENKINS-61315 Re: Add documentation for declarative pipeline support. Hi Tim, thanks for the report.If I understand your report correctly, you want Bitbucket Server to perform a merge on your PR branch without modifying the target branch, and having that build status used as the condition for your merge check. Unfortunately, this is a limitation in Bitbucket Server rather than in Jenkins- the plugin will register a build against the commit on the target branch rather than a merged commit, and that is used for the merge check instead. We do not provide any in-product support for build statuses against a merge build of a PR before it has been merged.Based on this however, I feel this is not specifically an issue with the Jenkins plugin documentation, so I will close this ticket for now. Please feel free to follow up if you have any further questions. 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.204901.1583274613000.3399.1585613280407%40Atlassian.JIRA.
[JIRA] (JENKINS-61749) NPE when trying to use Build Failure Analyzer support
Title: Message Title Jonathan Rogers created an issue Jenkins / JENKINS-61749 NPE when trying to use Build Failure Analyzer support Issue Type: Improvement Assignee: Unassigned Components: periodic-reincarnation-plugin Created: 2020-03-31 00:15 Environment: Jenkins 2.222.1 OpenJDK 1.8 Periodic Reincarnation Plugin 1.13 Build Failure Analyzer Plugin 1.25.1 Labels: exception Priority: Major Reporter: Jonathan Rogers Whenever I visit the Jenkins configuration page, I see a traceback like the following in the "Periodic Reincarnation of failed builds" section under "Build Failure Triggers". The traceback also appears in the main Jenkins log. Stack trace java.lang.NullPointerException at java.util.AbstractCollection.addAll(AbstractCollection.java:343) at org.jenkinsci.plugins.periodicreincarnation.PeriodicReincarnationGlobalConfiguration.doFillBfaValueItems(PeriodicReincarnationGlobalConfiguration.java:247) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:7
[JIRA] (JENKINS-61749) NPE when trying to use Build Failure Analyzer support
Title: Message Title Jonathan Rogers updated an issue Jenkins / JENKINS-61749 NPE when trying to use Build Failure Analyzer support Change By: Jonathan Rogers Issue Type: Improvement Bug 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.205579.1585613758000.3402.1585613820085%40Atlassian.JIRA.
[JIRA] (JENKINS-61253) Remoting using WebSocket fails with "Handshake response not received" Exception
Title: Message Title ethorsa commented on JENKINS-61253 Re: Remoting using WebSocket fails with "Handshake response not received" Exception Thanks Jeff Thompson, downgrading to v4.2 solved the issue and I was able to connect agents over WebSockets. The WebSocket implementation is still in Beta, because we need to get extended real-world testing. I'll let you know if there are other issues. 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.204820.1582797002000.3408.1585631400125%40Atlassian.JIRA.
