[JIRA] (JENKINS-45318) Add dependancy on net.i2p.crypto inside sshd module
Title: Message Title C R commented on JENKINS-45318 Re: Add dependancy on net.i2p.crypto inside sshd module Submitted a pull request Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52152) xunit cannot read junit time attributes with more than three decimals or using exponential notation
Title: Message Title Nikolas Falco commented on JENKINS-52152 Re: xunit cannot read junit time attributes with more than three decimals or using exponential notation I had already explain the reason of why and which junit format this plugin supports. For any custom junit format refer to this issue and the wiki documentation here Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54255) xUnit sets build status incorrectly
Title: Message Title Nikolas Falco closed an issue as Cannot Reproduce Jenkins / JENKINS-54255 xUnit sets build status incorrectly Change By: Nikolas Falco Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54281) Test Result Trend is broken
Title: Message Title Nikolas Falco commented on JENKINS-54281 Re: Test Result Trend is broken I need the test report to reproduce the issue. I'm not able to run any C compile on my machine. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54668) Unable to provide NodeJS path to Jenkins plugin
Title: Message Title Nikolas Falco closed an issue as Done Jenkins / JENKINS-54668 Unable to provide NodeJS path to Jenkins plugin Change By: Nikolas Falco Status: Open Closed Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54668) Unable to provide NodeJS path to Jenkins plugin
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-54668 Unable to provide NodeJS path to Jenkins plugin Change By: Nikolas Falco Priority: Blocker Trivial Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54682) Allow configuration of listen address for JNLP agents
Title: Message Title Simon Richter created an issue Jenkins / JENKINS-54682 Allow configuration of listen address for JNLP agents Issue Type: Improvement Assignee: Unassigned Components: core Created: 2018-11-17 02:31 Priority: Minor Reporter: Simon Richter I have a Jenkins setup that is running inside a private network together with the agents. A SNI proxy forwards outside connections to the internal address. When agents connect via JNLP, they first connect to the https port, which is properly forwarded back into the internal network, but then they attempt to connect to the agent port using the public IP of the inbound proxy/firewall, which fails. It would be nice if it were possible to configure an IP address for agents to connect to, in addition to a port number, so agents could be instructed to connect to the internal IP. Add Comment
[JIRA] (JENKINS-54681) dir('path') is broken when used within "docker.image().inside{}"
Title: Message Title
Krassimir Valev commented on JENKINS-54681
Re: dir('path') is broken when used within "docker.image().inside{}"
The issue seems to be actually stemming from the durable task plugin, which tries to create the workspace folder (in this case the 'dir' parameter) on the host file system, which fails: https://github.com/jenkinsci/durable-task-plugin/blob/master/src/main/java/org/jenkinsci/plugins/durabletask/FileMonitoringTask.java#L171-L175
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54681) dir('path') is broken when used within "docker.image().inside{}"
Title: Message Title
Krassimir Valev commented on JENKINS-54681
Re: dir('path') is broken when used within "docker.image().inside{}"
The issue seems to be actually stemming from the durable task plugin, which tries to create the workspace folder (in this case the 'dir' parameter) on the host file system, which fails: https://github.com/jenkinsci/durable-task-plugin/blob/master/src/main/java/org/jenkinsci/plugins/durabletask/FileMonitoringTask.java#L171-L175
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54282) Jenkins stuck on 'Please wait while Jenkins is getting ready to work' after pressing 'Reload Configuration from Disk'
Title: Message Title Peter Toennies commented on JENKINS-54282 Re: Jenkins stuck on 'Please wait while Jenkins is getting ready to work' after pressing 'Reload Configuration from Disk' Does anyone monitor posts on this forum? Will this issue be fixed in an upcoming Jenkins version? Did I do something wrong on my system when upgrading Jenkins to cause this issue? Thank you, Peter Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53279) java.lang.NoClassDefFoundError: javax/servlet/ServletException
Title: Message Title Mark Waite updated JENKINS-53279 Fixed in git client plugin 2.7.4 thanks to PR 359 from Vincent Latombe. Jenkins / JENKINS-53279 java.lang.NoClassDefFoundError: javax/servlet/ServletException Change By: Mark Waite Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50019) java.lang.NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins$MasterComputer
Title: Message Title Mark Waite updated JENKINS-50019 Jenkins / JENKINS-50019 java.lang.NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins$MasterComputer Change By: Mark Waite Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50019) java.lang.NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins$MasterComputer
Title: Message Title Mark Waite updated JENKINS-50019 Fixed in git client plugin 2.7.4 thanks to PR 359 from Vincent Latombe. Jenkins / JENKINS-50019 java.lang.NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins$MasterComputer Change By: Mark Waite Status: Closed Fixed but Unreleased Resolution: Cannot Reproduce Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49402) slave fails with java.lang.NoClassDefFoundError: hudson.model.Computer
Title: Message Title Mark Waite updated JENKINS-49402 Jenkins / JENKINS-49402 slave fails with java.lang.NoClassDefFoundError: hudson.model.Computer Change By: Mark Waite Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49402) slave fails with java.lang.NoClassDefFoundError: hudson.model.Computer
Title: Message Title Mark Waite updated JENKINS-49402 Fixed in git client plugin 2.7.4 thanks to PR 359 from Vincent Latombe. Jenkins / JENKINS-49402 slave fails with java.lang.NoClassDefFoundError: hudson.model.Computer Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54651) Refusing to marshal net.sf.json.JSONObject
Title: Message Title Oleg Nenashev commented on JENKINS-54651 Re: Refusing to marshal net.sf.json.JSONObject Yes, this whitelist would be required in the libraries you include, not in your plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36914) stash step is excessively slow on ARM
Title: Message Title Sam Van Oort commented on JENKINS-36914 Re: stash step is excessively slow on ARM Jesse Glick I'd agree we should burn agent CPU over master CPU, but do think it's worth saving some storage space on-master. The happy medium would be a high-performance algorithm such as LZ4, LZO, or LZF which gets most of the benefits of compression and can shrink highly-compressible content with a much lower CPU cost than Deflate (used by GZIP). I've seen very positive results with those algorithms in the past – they're fast enough that if you're transmitting fairly compressible content (ex JSON or XML payloads or source code) you can see time savings even in a data center with gigabit links. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down >Did you want a master thread dump? yep, a master thread dump >I changed the retry settings to keep trying again, but those seem to be ignored. I do not talk about reties, I talk about disable credentials tracking, so set this property `-Dhudson.plugins.sshslaves.SSHLauncher.trackCredentials=false` in Jenkins start options, it is available on 1.27+ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54645) Send queue data in JSON Payload
Title: Message Title Mike Delaney commented on JENKINS-54645 Re: Send queue data in JSON Payload Jakub Bochenski fair enough, is the ideal that we'd be able to set a global level, or project, or both? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54681) dir('path') is broken when used within "docker.image().inside{}"
Title: Message Title
Krassimir Valev created an issue
Jenkins / JENKINS-54681
dir('path') is broken when used within "docker.image().inside{}"
Issue Type:
Bug
Assignee:
Unassigned
Components:
docker-workflow-plugin
Created:
2018-11-16 22:20
Priority:
Blocker
Reporter:
Krassimir Valev
It seems that when 'dir' is used within a docker container, it is expected that the directory exists on the host and not within the docker container. The following minimal Jenkinsfile showcases this issue:
node('docker') {
stage('Build within docker') {
// path to the workspace on the local machine and wthin the docker image
workspace = env.WORKSPACE
workspaceDocker = '/workspace'
image = docker.image("ubuntu:18.04")
image.pull()
image.inside("-v ${workspace}:${workspaceDocker}") {
sh 'pwd'
sh """#!/bin/sh
cd ${workspaceDocker}
pwd
"""
// this fails with the following error:
// java.nio.file.AccessDeniedException: /workspace
dir(workspaceDocker) {
sh 'pwd'
}
}
}
}
[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title John Zila commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down Did you want a master thread dump? For obvious reasons, it'll be difficult to get an agent dump. Re: the issue, it happens quite sporadically–I haven't noticed a correlation between the number of agents and the probability of the issue. Frankly it seems to happen almost every time a node initially attempts to start up. I changed the retry settings to keep trying again, but those seem to be ignored. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52774) Restart from Stage doesn't restore global variable
Title: Message Title
Fernando Nasser commented on JENKINS-52774
Re: Restart from Stage doesn't restore global variable
Daniel Kurzynski I saved some state in a file and if it fails and is restarted I read what I need from that file (you need set preserveStashes() I believe, I did it but I am not sure). It worked fine. For skipping steps, etc., there is a JIRA to get the isRestartedRun() and isRestartedStage() into variables that can be used outside of the when{}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down Did you apply the workaround on https://github.com/jenkinsci/ssh-slaves-plugin/blob/master/doc/TROUBLESHOOTING.md#threads-stuck-at-credentialsprovidertrackall ? there is a thread block with a high number of agents launched with Cloud plugins on 1.27+ (https://issues.jenkins-ci.org/browse/JENKINS-49235), the next version mitigate it a little but requires a change on the credentials plugin, so for the moment disabling the credentials track is the only solution. Do you see the issue when you spin 10+/20+/30+/50+/100+/... agents? When the issue happens can you get a threaddump? https://wiki.jenkins.io/display/JENKINS/Obtaining+a+thread+dump Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52282) JNLPLauncher: Update Java Web Start built-in Documentation and Wiki to reflect unavailability in Java 10+
Title: Message Title Mark Waite commented on JENKINS-52282 Re: JNLPLauncher: Update Java Web Start built-in Documentation and Wiki to reflect unavailability in Java 10+ Refer to the hide-java-web-start-on-jdk-11 branch for my work in progress. I believe the most recent commit is closest to a final implementation and the preceding commit should be discarded. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54668) Unable to provide NodeJS path to Jenkins plugin
Title: Message Title Nikolas Falco commented on JENKINS-54668 Re: Unable to provide NodeJS path to Jenkins plugin I image from the description you are not using the automatic installer. In this case you have to set the installation. All folders you wrote are not nodejs installation folder for sure. There is present only the link to the node executable. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54680) Compressed build logs not rendering with update to workflow-job plugin >= 2.26
Title: Message Title Adam Brousseau created an issue Jenkins / JENKINS-54680 Compressed build logs not rendering with update to workflow-job plugin >= 2.26 Issue Type: Bug Assignee: Daniel Beck Components: compress-build-log-plugin Created: 2018-11-16 21:09 Environment: Jenkins 2.138.3 Compress log plugin 1.2 Pipeline: job plugin 2.29 Labels: regression Priority: Minor Reporter: Adam Brousseau We started using the compress build log plugin right before the revamp to how the pipeline logs were stored in JEP-210 I believe. Before we upgraded the Pipeline: job plugin we had the main log being compressed, and able to be rendered on the console UI. Once we upgraded from 2.25 to 2.29 the console is no longer rendered on the UI. Not sure if this issue is with the compress plugin or the pipeline job plugin. Add
[JIRA] (JENKINS-54662) hudson.model.UsageStatistics not compatible with CasC plugin
Title: Message Title Oleg Nenashev started work on JENKINS-54662 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54662) hudson.model.UsageStatistics not compatible with CasC plugin
Title: Message Title Oleg Nenashev commented on JENKINS-54662 Re: hudson.model.UsageStatistics not compatible with CasC plugin https://github.com/jenkinsci/jenkins/pull/3762 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36914) stash step is excessively slow on ARM
Title: Message Title Jesse Glick commented on JENKINS-36914 Re: stash step is excessively slow on ARM Could just switch to ArchiverFactory.TAR and do the compression on the master side (and similarly for unstashing). There is generally no benefit to using compression at this level regardless of the processor—a LAN is generally quite capable of handling high bandwidth, and many agent connection methods add transport-level compression anyway. On the other hand it is better to burn CPU on an agent, even at the expense of longer build times, if it saves a little CPU on the master, and we do not want to store stashes uncompressed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title John Zila commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down And this: [11/16/18 20:42:53] [SSH] Opening SSH connection to 10.0.2.84:22. ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title John Zila commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down And this, on Windows nodes (usually 2-3 relaunches makes it work): [11/16/18 20:42:35] [SSH] Checking java version of java [11/16/18 20:42:51] [SSH] java -version returned 1.8.0_171. [11/16/18 20:42:51] [SSH] Starting sftp client. [11/16/18 20:42:52] [SSH] Copying latest slave.jar... [11/16/18 20:42:53] [SSH] Copied 776,717 bytes. Expanded the channel window size to 4MB [11/16/18 20:42:53] [SSH] Starting slave process: cd "c:\Jenkins" && java -Xmx8192m -jar slave.jar ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins java.util.concurrent.CancellationException at java.util.concurrent.FutureTask.report(FutureTask.java:121) at java.util.concurrent.FutureTask.get(FutureTask.java:192) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:883) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) java.io.IOException: java.io.InterruptedIOException at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:1120) at hudson.plugins.sshslaves.SSHLauncher.access$500(SSHLauncher.java:148) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:845) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:820) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: java.io.InterruptedIOException at com.trilead.ssh2.channel.ChannelManager.getChannelData(ChannelManager.java:938) at com.trilead.ssh2.channel.ChannelInputStream.read(ChannelInputStream.java:58) at com.trilead.ssh2.channel.ChannelInputStream.read(ChannelInputStream.java:79) at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:409) at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:356) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:431) at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:1110) ... 7 more
[JIRA] (JENKINS-54138) Submit a JEP for audit logging
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-54138 Submit a JEP for audit logging Change By: Liam Newman Summary: Author Submit a JEP for audit logging proposal Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title John Zila commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down I get this a bunch: ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins java.util.concurrent.CancellationException at java.util.concurrent.FutureTask.report(FutureTask.java:121) at java.util.concurrent.FutureTask.get(FutureTask.java:192) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:883) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Re-launching the node almost always fixes it, but the plugin should be doing that automatically. Instead, I get nodes that fail to launch and then engineers complaining that CI is broken. I have to manually relaunch nodes dozens of times a day. Would be nice if the SSH Slaves Plugin retry settings worked. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52282) JNLPLauncher: Update Java Web Start built-in Documentation and Wiki to reflect unavailability in Java 10+
Title: Message Title Oleg Nenashev assigned an issue to Mark Waite Jenkins / JENKINS-52282 JNLPLauncher: Update Java Web Start built-in Documentation and Wiki to reflect unavailability in Java 10+ Change By: Oleg Nenashev Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52282) JNLPLauncher: Update Java Web Start built-in Documentation and Wiki to reflect unavailability in Java 10+
Title: Message Title Oleg Nenashev started work on JENKINS-52282 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52282) JNLPLauncher: Update Java Web Start built-in Documentation and Wiki to reflect unavailability in Java 10+
Title: Message Title Oleg Nenashev commented on JENKINS-52282 Re: JNLPLauncher: Update Java Web Start built-in Documentation and Wiki to reflect unavailability in Java 10+ Hi Mark Waite. Would it be possible to submit a patch with the current state of this change, even if it is not complete? We will be able to pick it up from there if you have no time to work on it. CC Baptiste Mathus Adrien Lecharpentier Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54643) A connection interruption causes the pipeline to fail when USE_WATCHING=true
Title: Message Title Jesse Glick commented on JENKINS-54643 Re: A connection interruption causes the pipeline to fail when USE_WATCHING=true The failure of the second sh step sounds like JENKINS-41854. Why watch mode would trigger that, I am not sure. The channel is getting closed, which is unsurprising if the network is unplugged (for example, a ping thread would be expected to fail); the more interesting question is why it does not get closed when in polling mode. Loss of some output in the face of network outages is hard to avoid in watch mode; this is simply a tradeoff for far more efficient network and master CPU utilization. PR 86 discussed possible alternative approaches that would adjust the tradeoffs. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54487) Offer Java 11 Alpine Docker images for Jenkins agents
Title: Message Title Oleg Nenashev commented on JENKINS-54487 Re: Offer Java 11 Alpine Docker images for Jenkins agents Not a blocker for the release anymore. We agreed to reduce the scope to only Debian images, because there is no Alpine package for OpenJDK11. https://github.com/jenkinsci/jep/tree/master/jep/211#docker-packaging-for-alpine-slim Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54487) Offer Java 11 Alpine Docker images for Jenkins agents
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-54487 Offer Java 11 Alpine Docker images for Jenkins agents Change By: Oleg Nenashev Assignee: Carlos Sanchez Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36914) stash step is excessively slow on ARM
Title: Message Title Sam Van Oort commented on JENKINS-36914 Re: stash step is excessively slow on ARM Jesse Glick I know that the discrepancy vs. raw IO speeds is almost certainly due to GZIP compress/decompress. Using an uncompressed method might be beneficial in some cases (especially with poorly-compressible data). I'd have to benchmark the GZIP implementation on that specific platform and compare to the same one on a Intel/AMD laptop processor – but the benchmarks here show pretty large differences in performance between ARM and Intel processors: https://quixdb.github.io/squash-benchmark/ And if you're only using a single CPU thread to do decompression, with a pure-java implementation that is potentially less than optimal for the platform, then 0.7 MB/s seems not unreasonable for a compression rate. It's in the ballpark anyway - I'm seeing <10 MB compression rates reported for various quad-core+ ARM chips for native-code implementations of that compression algorithm, using multiple threads. Remember we're talking processors that only have a few watts to play with and fairly small cache sizes. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53716) Core Build Flow: ysoserial tests cannot compile on JDK11, Corba was removed
Title: Message Title Oleg Nenashev updated JENKINS-53716 Fixed in https://github.com/jenkinsci/jenkins/pull/3759 Jenkins / JENKINS-53716 Core Build Flow: ysoserial tests cannot compile on JDK11, Corba was removed Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.152 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53863) Core: Upstream JTH patches and test automation to the Jenkins master branch
Title: Message Title Oleg Nenashev resolved as Fixed Jenkins / JENKINS-53863 Core: Upstream JTH patches and test automation to the Jenkins master branch Change By: Oleg Nenashev Status: In Progress Resolved Resolution: Fixed Released As: Jenkins 2.152 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54679) SSHLauncher doesn't continue retrying to connect to remote executor
Title: Message Title
Bert JW Regeer created an issue
Jenkins / JENKINS-54679
SSHLauncher doesn't continue retrying to connect to remote executor
Issue Type:
Bug
Assignee:
Chad Schmutzer
Components:
ec2-fleet-plugin, ssh-agent-plugin
Created:
2018-11-16 20:27
Labels:
plugin regression
Priority:
Critical
Reporter:
Bert JW Regeer
SSHLauncher{host='10.50.10.252', port=22, credentialsId='aaf2ee5e-32bd-4675-9793-0570922f9c66', jvmOptions='', javaPath='', prefixStartSlaveCmd='', suffixStartSlaveCmd='', launchTimeoutSeconds=5, maxNumRetries=120, retryWaitTime=2, sshHostKeyVerificationStrategy=hudson.plugins.sshslaves.verifiers.ManuallyTrustedKeyVerificationStrategy, tcpNoDelay=true, trackCredentials=true} [11/16/18 20:19:40] [SSH] Opening SSH connection to 10.50.10.252:22. Connection refused (Connection refused) SSH Connection failed with IOException: "Connection refused (Connection refused)", retrying in 2 seconds. There are 120 more retries left. Connection refused (Connection refused) SSH Connection failed with IOException: "Connection refused (Connection refused)", retrying in 2 seconds. There are 119 more retries left. Connection refused (Connection refused) SSH Connection failed with IOException: "Connection refused (Connection refused)", retrying in 2 seconds. There are 118 more retries left. ERROR: null java.util.concurrent.CancellationException {{ at java.util.concurrent.FutureTask.report(FutureTask.java:121)}} {{ at java.util.concurrent.FutureTask.get(FutureTask.java:192)}} {{ at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:904)}} {{ at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294)}} {{ at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)}} {{ at
[JIRA] (JENKINS-35708) EC2 Plugin: Ability to round robin EC2 availability zones
Title: Message Title David Fluck commented on JENKINS-35708 Re: EC2 Plugin: Ability to round robin EC2 availability zones It looks like this change has indeed been released. I've also encountered that error before. How are you listing the subnets? Are you using subnet IDs? Are all of the subnets in the same VPC? This is the relevant code: private ListgetEc2SecurityGroups(AmazonEC2 ec2) throws AmazonClientException { List groupIds = new ArrayList (); DescribeSecurityGroupsResult groupResult = getSecurityGroupsBy("group-name", securityGroupSet, ec2); if (groupResult.getSecurityGroups().size() == 0) { groupResult = getSecurityGroupsBy("group-id", securityGroupSet, ec2); } for (SecurityGroup group : groupResult.getSecurityGroups()) { if (group.getVpcId() != null && !group.getVpcId().isEmpty()) { List filters = new ArrayList(); filters.add(new Filter("vpc-id").withValues(group.getVpcId())); filters.add(new Filter("state").withValues("available")); filters.add(new Filter("subnet-id").withValues(getCurrentSubnetId())); DescribeSubnetsRequest subnetReq = new DescribeSubnetsRequest(); subnetReq.withFilters(filters); DescribeSubnetsResult subnetResult = ec2.describeSubnets(subnetReq); List subnets = subnetResult.getSubnets(); if (subnets != null && !subnets.isEmpty()) { groupIds.add(group.getGroupId()); } } } if (securityGroupSet.size() != groupIds.size()) { throw new AmazonClientException("Security groups must all be VPC security groups to work in a VPC context"); } return groupIds; } Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title John Zila commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down HTML Publisher plugin,1.17 Credentials Plugin,2.1.18 Pipeline: Input Step,2.8 Jackson 2 API Plugin,2.9.7.1 Pipeline,2.6 Bitbucket Pipeline for Blue Ocean,1.9.0 Blue Ocean Core JS,1.9.0 Design Language,1.9.0 OWASP Markup Formatter Plugin,1.5 Maven Integration plugin,3.1.2 External Monitor Job Type Plugin,1.7 Pub-Sub "light" Bus,1.12 Pipeline: Declarative Agent API,1.1.1 Pipeline: Declarative Extension Points API,1.3.2 Multiple SCMs plugin,0.6 GitHub Pull Request Builder,1.42.0 Server Sent Events (SSE) Gateway Plugin,1.16 Web for Blue Ocean,1.9.0 Pipeline: Shared Groovy Libraries,2.12 Docker Pipeline,1.17 Common API for Blue Ocean,1.9.0 HSTS Filter Plugin,1.0 Folders Plugin,6.6 SCM API Plugin,2.3.0 AnsiColor,0.6.0 Command Agent Launcher Plugin,1.2 Events API for Blue Ocean,1.9.0 Structs Plugin,1.17 Pipeline: Nodes and Processes,2.26 Docker Commons Plugin,1.13 Pipeline Graph Analysis Plugin,1.9 Email Extension Plugin,2.63 Pipeline: Milestone Step,1.3.1 Lockable Resources plugin,2.3 Display URL for Blue Ocean,2.2.0 Pipeline: Build Step,2.7 Git client plugin,2.7.3 Variant Plugin,1.1 Config API for Blue Ocean,1.9.0 Mercurial plugin,2.4 Bitbucket Branch Source Plugin,2.2.14 MapDB API Plugin,1.0.9.0 Pipeline: API,2.32 GitHub Pipeline for Blue Ocean,1.9.0 Workspace Cleanup Plugin,0.36 JUnit Plugin,1.26.1 GitHub Authentication plugin,0.29 Pipeline SCM API for Blue Ocean,1.9.0 Green Balls,1.15 Pipeline: REST API Plugin,2.10 Pipeline: Basic Steps,2.12 Build Timeout,1.19 Run Condition Plugin,1.2 Matrix Authorization Strategy Plugin,2.3 SSH Credentials Plugin,1.14 Plain Credentials Plugin,1.4 Metrics Plugin,4.0.2.2 Pipeline: Groovy,2.60 Credentials Binding Plugin,1.17 Pipeline: SCM Step,2.7 Rebuilder,1.29 HTTP Request Plugin,1.8.22 Pipeline: GitHub Groovy Libraries,1.0 PAM Authentication plugin,1.4 REST Implementation for Blue Ocean,1.9.0 Display URL API,2.2.0 Pipeline: Declarative,1.3.2 Pipeline: Model API,1.3.2 Port Allocator Plug-in,1.8 Durable Task Plugin,1.28 bouncycastle API Plugin,2.17 Slack Notification Plugin,2.3 GIT server Plugin,1.7 Blue Ocean,1.9.0 JSch dependency plugin,0.1.54.2 Node Iterator API Plugin,1.5.0 JIRA Integration for Blue Ocean,1.9.0 i18n for Blue Ocean,1.9.0 Git plugin,3.9.1 Dashboard for Blue Ocean,1.9.0 Role-based Authorization Strategy,2.9.0 Matrix Project Plugin,1.13 Autofavorite for Blue Ocean,1.2.2 Pipeline Remote Loader Plugin,1.4 Conditional BuildStep,1.3.6 Pipeline: Stage View Plugin,2.10 promoted builds plugin,3.2 Blue Ocean Pipeline Editor,1.9.0 Resource Disposer Plugin,0.12 Copy Artifact Plugin,1.41 _javascript_ GUI Lib: Moment.js bundle plugin,1.1.1 Git Pipeline for Blue Ocean,1.9.0 JIRA plugin,3.0.5 EC2 Fleet Jenkins Plugin,1.1.8-SNAPSHOT (private-cd808d0d-jzila) Pipeline: Job,2.29 Script Security Plugin,1.48 _javascript_ GUI Lib: Handlebars bundle plugin,1.1.1 REST API for Blue Ocean,1.9.0 Mask Passwords Plugin,2.12.0 Windows Slaves Plugin,1.3.1 Favorite,2.3.2 Pipeline: Stage Tags Metadata,1.3.2 Timestamper,1.8.10 Self-Organizing Swarm Plug-in Modules,3.14 Subversion Plug-in,2.12.1 GitHub Branch Source Plugin,2.4.1 LDAP Plugin,1.20 Pipeline: AWS Steps,1.33 SSH Slaves plugin,1.26 GitHub plugin,1.29.3 Monitoring,1.74.0 JWT for Blue Ocean,1.9.0 SSH Agent Plugin,1.17 Xvfb plugin,1.1.4-beta-1 Icon Shim Plugin,2.0.3 Authentication Tokens API Plugin,1.3 Token Macro Plugin,2.5 Apache HttpComponents Client
[JIRA] (JENKINS-36914) stash step is excessively slow on ARM
Title: Message Title Jesse Glick commented on JENKINS-36914 Re: stash step is excessively slow on ARM Do you have some evidence of this being an issue with Gzip on ARM? If so, it would be appropriate to use an uncompressed transfer method on that platform. Really it might be better to do so all the time—the Remoting transport is generally responsible for compression. Of course if you are using https://plugins.jenkins.io/artifact-manager-s3 this would not be an issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title
Ivan Fernandez Calvo commented on JENKINS-53468
Re: Since 1.27 update Channel is closing or has closed down
I need the list of plugins installed is something weird, run this script on the Jenkins script console and attach the output, it is the list of installed plugins and versions. ``` result = '' for (plugin in Jenkins.instance.pluginManager.plugins) { result = result + "${plugin.displayName}" + ',' + "${plugin.version}\n" } return result ```
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54643) A connection interruption causes the pipeline to fail when USE_WATCHING=true
Title: Message Title Jesse Glick commented on JENKINS-54643 Re: A connection interruption causes the pipeline to fail when USE_WATCHING=true We have a functional test for a similar scenario which does not display this issue, but it is probably too simple. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title
Ivan Fernandez Calvo edited a comment on JENKINS-53468
Re: Since 1.27 update Channel is closing or has closed down
I need the list of plugins installed is something weird, run this script on the Jenkins script console and attach the output, it is the list of installed plugins and versions. ``` {code} result = ''for (plugin in Jenkins.instance.pluginManager.plugins) { result = result + "${plugin.displayName}" + ',' + "${plugin.version}\n"}return result ``` {code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54643) A connection interruption causes the pipeline to fail when USE_WATCHING=true
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-54643 A connection interruption causes the pipeline to fail when USE_WATCHING=true Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54634) Jenkins restart wipes out Cucumber Reports
Title: Message Title Damian Szczepanik closed an issue as Cannot Reproduce Jenkins / JENKINS-54634 Jenkins restart wipes out Cucumber Reports Change By: Damian Szczepanik Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54634) Jenkins restart wipes out Cucumber Reports
Title: Message Title Damian Szczepanik resolved as Cannot Reproduce Jenkins / JENKINS-54634 Jenkins restart wipes out Cucumber Reports Change By: Damian Szczepanik Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54634) Jenkins restart wipes out Cucumber Reports
Title: Message Title Damian Szczepanik commented on JENKINS-54634 Re: Jenkins restart wipes out Cucumber Reports Cannot reproduce and symptoms looks like not the plugin issue Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51792) Incorrect Jenkinsfile with >1 steps section produces unclear error about `default` branch name
Title: Message Title Karl Shultz assigned an issue to Karl Shultz Jenkins / JENKINS-51792 Incorrect Jenkinsfile with >1 steps section produces unclear error about `default` branch name Change By: Karl Shultz Assignee: Andrew Bayer Karl Shultz Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53775) FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin
Title: Message Title Basil Crow commented on JENKINS-53775 Re: FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin Hit this again today. I'm not actually as concerned with JobDSL + Pipeline because that's kind of an edge case situation Sam Van Oort, can you explain why you consider this an edge case situation? Is it because you'd rather that users use a Jenkinsfile with the Pipeline Multibranch Plugin rather than Job DSL? I'd love to do that, but I can't. My organization centralizes company-wide build logic in one team, and one repository within that team. Due to JENKINS-43749, the Pipeline Multibranch Plugin doesn't work for my use case. In that bug Jesse recommended the use of Job DSL. So that is what I am doing. Is this an edge case situation? I'd be happy to move to a different setup if one was available, but I don't see any other options, I'm afraid. And this bug continues to affect us. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51145) PowerShell pipeline step does not seem to be durable
Title: Message Title Vivek Pandey commented on JENKINS-51145 Re: PowerShell pipeline step does not seem to be durable Gabriel Loewen No worries. Thanks for the update and details. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53775) FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin
Title: Message Title Basil Crow assigned an issue to Unassigned Jenkins / JENKINS-53775 FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin Change By: Basil Crow Assignee: Daniel Spilker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54678) Logs are lost in Multibranch Pipleline after the build has finished
Title: Message Title Tibor Digana created an issue Jenkins / JENKINS-54678 Logs are lost in Multibranch Pipleline after the build has finished Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2018-11-16 18:45 Environment: Jenkins 2.138.3 Pipeline Multibranch with defaults 2.0 Pipeline Multibranch Plugin 2.20 Build Pipeline Plugin 1.58 Priority: Major Reporter: Tibor Digana The logs in /job/master/167/console are shown when the build is in progress. After it has finished I see nothing. Only a black narrow bar. The BlueOcen shows me this stacktrace java.io.FileNotFoundException: /var/lib/jenkins/jobs/Invoice/branches/master/builds/166/log (No such file or directory) at java.io.RandomAccessFile.open0(Native Method) at java.io.RandomAccessFile.open(RandomAccessFile.java:316) at java.io.RandomAccessFile.(RandomAccessFile.java:243) at org.jenkinsci.plugins.workflow.log.FileLogStorage.stepLog(FileLogStorage.java:259) at org.jenkinsci.plugins.workflow.support.actions.LogStorageAction.getLogText(LogStorageAction.java:62) at io.jenkins.blueocean.rest.impl.pipeline.PipelineStepImpl.getLog(PipelineStepImpl.java:139) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)
[JIRA] (JENKINS-54512) can not change workspace in k8s pipeline
Title: Message Title Andreas Bergmeier commented on JENKINS-54512 Re: can not change workspace in k8s pipeline Also note, that if `/home/jenkins` is mounted noexec (e.g. in OpenShift) that you cannot execute any script there. And since this bug is present, there is no workaround for this! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54661) DataSource properties are ignored
Title: Message Title Cyrille Le Clerc updated JENKINS-54661 Jenkins / JENKINS-54661 DataSource properties are ignored Change By: Cyrille Le Clerc Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54669) Use sensible defaults settings for the datasource configuration
Title: Message Title Cyrille Le Clerc started work on JENKINS-54669 Change By: Cyrille Le Clerc Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54669) Use sensible defaults settings for the datasource configuration
Title: Message Title Cyrille Le Clerc updated JENKINS-54669 Jenkins / JENKINS-54669 Use sensible defaults settings for the datasource configuration Change By: Cyrille Le Clerc Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54677) Switching container does not switch filesystem
Title: Message Title
Andreas Bergmeier created an issue
Jenkins / JENKINS-54677
Switching container does not switch filesystem
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2018-11-16 18:34
Priority:
Major
Reporter:
Andreas Bergmeier
When I do
container('mycontainer') {
script {
def foo = "ls -lah /var"
echo "${foo}"
I get the `/var` of jnlp. Even when inserting `dir('/var')` there is not behavior change. When I however do `ls -lah /var` in `mycontainer` (via kubectl), I get the output of `mycontainer`.
Add Comment
[JIRA] (JENKINS-43408) Provide a standardized way of dealing with variables
Title: Message Title Andrew Bayer updated JENKINS-43408 Jenkins / JENKINS-43408 Provide a standardized way of dealing with variables Change By: Andrew Bayer Status: Open Fixed but Unreleased Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45422) Environment variables
Title: Message Title Andrew Bayer updated JENKINS-45422 Closing these epics. Jenkins / JENKINS-45422 Environment variables Change By: Andrew Bayer Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45382) Documentation
Title: Message Title Andrew Bayer updated JENKINS-45382 Closing these epics. Jenkins / JENKINS-45382 Documentation Change By: Andrew Bayer Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45381) Docker agents
Title: Message Title Andrew Bayer updated JENKINS-45381 Closing these epics. Jenkins / JENKINS-45381 Docker agents Change By: Andrew Bayer Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45421) IDE integration
Title: Message Title Andrew Bayer updated JENKINS-45421 Closing these epics. Jenkins / JENKINS-45421 IDE integration Change By: Andrew Bayer Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45423) Roundtrip
Title: Message Title Andrew Bayer updated JENKINS-45423 Closing these epics. Jenkins / JENKINS-45423 Roundtrip Change By: Andrew Bayer Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45425) Language
Title: Message Title Andrew Bayer updated JENKINS-45425 Closing these epics. Jenkins / JENKINS-45425 Language Change By: Andrew Bayer Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45424) Integrations
Title: Message Title Andrew Bayer updated JENKINS-45424 Closing these epics. Jenkins / JENKINS-45424 Integrations Change By: Andrew Bayer Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45428) Agents (Other)
Title: Message Title Andrew Bayer updated JENKINS-45428 Closing these epics. Jenkins / JENKINS-45428 Agents (Other) Change By: Andrew Bayer Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45427) Post steps
Title: Message Title Andrew Bayer updated JENKINS-45427 Jenkins / JENKINS-45427 Post steps Change By: Andrew Bayer Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45426) Conditional stages
Title: Message Title Andrew Bayer updated JENKINS-45426 Closing these epics. Jenkins / JENKINS-45426 Conditional stages Change By: Andrew Bayer Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44679) need to support script inside options
Title: Message Title Andrew Bayer updated JENKINS-44679 Jenkins / JENKINS-44679 need to support script inside options Change By: Andrew Bayer Status: Open Fixed but Unreleased Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45429) Reusability
Title: Message Title Andrew Bayer updated JENKINS-45429 Closing these epics. Jenkins / JENKINS-45429 Reusability Change By: Andrew Bayer Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48661) Execute stage only after initial pipeline execution
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-48661 Execute stage only after initial pipeline execution Change By: Andrew Bayer Labels: stage-restart-improvements Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50548) Shared Library should be allowed to declare reusable stages
Title: Message Title Andrew Bayer updated JENKINS-50548 Jenkins / JENKINS-50548 Shared Library should be allowed to declare reusable stages Change By: Andrew Bayer Status: Open Fixed but Unreleased Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51145) PowerShell pipeline step does not seem to be durable
Title: Message Title Gabriel Loewen commented on JENKINS-51145 Re: PowerShell pipeline step does not seem to be durable Vivek Pandey You've assigned this bug to me, but I am actually not working on this. The underlying issue is that when Jenkins is running as a windows service and the agent goes offline, once the agent is reconnected the entire process tree under slave.jar including the durable tasks are killed. I believe that the fix for this needs to be process isolation for any durable tasks running on windows agents. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54512) can not change workspace in k8s pipeline
Title: Message Title Andreas Bergmeier commented on JENKINS-54512 Re: can not change workspace in k8s pipeline I tried changing to `/var/jenkins` with the same error message. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52388) Unable to skip Declarative: Checkout SCM when restart from stage
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-52388 Unable to skip Declarative: Checkout SCM when restart from stage Change By: Andrew Bayer Labels: stage-restart-improvements Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52391) Restarting Parallel Stages
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-52391 Restarting Parallel Stages Change By: Andrew Bayer Labels: stage-restart-improvements Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52777) another Jenkinsfile is used than reported to be used if 'rebuild from stage' is used
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-52777 another Jenkinsfile is used than reported to be used if 'rebuild from stage' is used Change By: Andrew Bayer Labels: stage-restart-improvements Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52774) Restart from Stage doesn't restore global variable
Title: Message Title Andrew Bayer commented on JENKINS-52774 Re: Restart from Stage doesn't restore global variable Daniel Kurzynski - no, just stashes - preserving program state (like global variables or singletons) is a deeper, more complex problem area than Declarative goes, and is replete with painpoints. Sorry. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53662) isRestartedRun() is not reset after a successful stage
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-53662 isRestartedRun() is not reset after a successful stage Change By: Andrew Bayer Labels: stage-restart-improvements Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53193) Provide currentBuild.isRestartedRun and .isRestartedStage global variables
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-53193 Provide currentBuild.isRestartedRun and .isRestartedStage global variables Change By: Andrew Bayer Labels: stage-restart-improvements Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53167) Add ability to always run particular stages when restarting
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-53167 Add ability to always run particular stages when restarting Change By: Andrew Bayer Labels: stage-restart-improvements Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title
John Zila edited a comment on JENKINS-53468
Re: Since 1.27 update Channel is closing or has closed down
FYI, things have been deteriorating badly. Nodes are now disconnecting even on 1. 27 26 for no reason. I tried to upgrade to 1.28.1, but then this terrible bug reared its head, making Jenkins completely unusable. I've had to revert back to 1. 27 26 to get back to a "just pretty bad" state.{noformat}Remoting version: 3.27This is a Unix agentEvacuated stdoutAgent successfully connected and onlineNov 16, 2018 5:18:27 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.gitclient.Git$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/Nov 16, 2018 5:18:29 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/Nov 16, 2018 5:19:38 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ERROR: Connection terminatedjava.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2680) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3155) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:861) at java.io.ObjectInputStream.(ObjectInputStream.java:357) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49) at hudson.remoting.Command.readFrom(Command.java:140) at hudson.remoting.Command.readFrom(Command.java:126) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)Caused: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)ERROR: Socket connection to SSH server was lostjava.net.SocketTimeoutException: The connect timeout expired at com.trilead.ssh2.Connection$1.run(Connection.java:762) at com.trilead.ssh2.util.TimeoutService$TimeoutThread.run(TimeoutService.java:91)Slave JVM has not reported exit code before the socket was lost[11/16/18 17:20:40] [SSH] Connection closed. {noformat}
Add Comment
[JIRA] (JENKINS-54386) preserveStashes does not work with parameter
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-54386 preserveStashes does not work with parameter Change By: Andrew Bayer Labels: stage-restart-improvements Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54250) Disable restarting stages in jenkinsfile optionally
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-54250 Disable restarting stages in jenkinsfile optionally Change By: Andrew Bayer Labels: stage-restart-improvements Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title John Zila commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down FYI, things have been deteriorating badly. Nodes are now disconnecting even on 1.27 for no reason. I tried to upgrade to 1.28.1, but then this terrible bug reared its head, making Jenkins completely unusable. I've had to revert back to 1.27 to get back to a "just pretty bad" state. Remoting version: 3.27 This is a Unix agent Evacuated stdout Agent successfully connected and online Nov 16, 2018 5:18:27 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.gitclient.Git$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ Nov 16, 2018 5:18:29 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ Nov 16, 2018 5:19:38 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ ERROR: Connection terminated java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2680) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3155) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:861) at java.io.ObjectInputStream.(ObjectInputStream.java:357) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49) at hudson.remoting.Command.readFrom(Command.java:140) at hudson.remoting.Command.readFrom(Command.java:126) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63) Caused: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77) ERROR: Socket connection to SSH server was lost java.net.SocketTimeoutException: The connect timeout expired at com.trilead.ssh2.Connection$1.run(Connection.java:762) at com.trilead.ssh2.util.TimeoutService$TimeoutThread.run(TimeoutService.java:91) Slave JVM has not reported exit code before the socket was lost [11/16/18 17:20:40] [SSH] Connection closed. Add Comment
[JIRA] (JENKINS-51865) Stage locks are created for skipped stages in declarative pipeline
Title: Message Title Andrew Bayer commented on JENKINS-51865 Re: Stage locks are created for skipped stages in declarative pipeline So the only way we could address this directly would be to add a beforeOptions flag to when - but I'm not sure that's actually worth doing. You can always put lock or timeout (and any other block-scoped options) in your steps instead. The more complexity we add to when flags (since we're already adding beforeInput in JENKINS-50880), the hairier the code gets, and this case is one that can largely be worked around (unlike with agent and input). The workaround would create scenarios where, say, timeout or lock wouldn't be in place for acquiring the agent or waiting for input, but it would still work fine for everything in steps. Does that sound reasonable to you? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51145) PowerShell pipeline step does not seem to be durable
Title: Message Title Gabriel Loewen assigned an issue to Unassigned Jenkins / JENKINS-51145 PowerShell pipeline step does not seem to be durable Change By: Gabriel Loewen Assignee: Gabriel Loewen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54036) Write-Error in powershell step behaves confusingly
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-54036 Write-Error in powershell step behaves confusingly Change By: Vivek Pandey Labels: error exit failure powershell triaged-2018-11 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54206) Merged PRs not being removed from multibranch
Title: Message Title Gunter Grodotzki commented on JENKINS-54206 Re: Merged PRs not being removed from multibranch Yes it does. Same settings - e.g. "1 day" Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54676) Error Creating Flownodes causes Jenkins to not add to queue or mark builds finished
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-54676 Error Creating Flownodes causes Jenkins to not add to queue or mark builds finished Change By: Vivek Pandey Labels: pipeline:groovy pipelines triaged-2018-11 workflow-cps Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54676) Error Creating Flownodes causes Jenkins to not add to queue or mark builds finished
Title: Message Title Junze He created an issue Jenkins / JENKINS-54676 Error Creating Flownodes causes Jenkins to not add to queue or mark builds finished Issue Type: Bug Assignee: Unassigned Components: pipeline, workflow-cps-plugin Created: 2018-11-16 17:57 Environment: Jenkins Version: 2.149 Pipeline Related Plugins: Pipeline: Groovy (workflow-cps): 2.60 Pipeline implementation for Blue Ocean (blueocean-pipeline-api-impl): 1.9.0 Pipeline: GitHub Groovy Libraries (pipeline-github-lib): 1.0 Bitbucket Pipeline for Blue Ocean (blueocean-bitbucket-pipeline): 1.9.0 Pipeline: Shared Groovy Libraries (workflow-cps-global-lib): 2.12 Pipeline: REST API Plugin (pipeline-rest-api): 2.10 Pipeline: Stage View Plugin (pipeline-stage-view): 2.10 Pipeline: Declarative Agent API (pipeline-model-declarative-agent): 1.1.1 GitHub Pipeline for Blue Ocean (blueocean-github-pipeline): 1.9.0 Pipeline Graph Analysis Plugin (pipeline-graph-analysis): 1.7 Pipeline: Job (workflow-job): 2.28 Blue Ocean Pipeline Editor (blueocean-pipeline-editor): 1.9.0 Pipeline SCM API for Blue Ocean (blueocean-pipeline-scm-api): 1.9.0 AWS CodePipeline Plugin (aws-codepipeline): 0.38 Pipeline (workflow-aggregator): 2.6 Pipeline: Milestone Step (pipeline-milestone-step): 1.3.1 Pipeline: Step API (workflow-step-api): 2.16 Docker Pipeline (docker-workflow): 1.17 Pipeline: Multibranch (workflow-multibranch): 2.20 Pipeline: Stage Tags Metadata (pipeline-stage-tags-metadata): 1.3.2 Git Pipeline for Blue Ocean (blueocean-git-pipeline): 1.9.0 Pipeline: Supporting APIs (workflow-support): 2.22 Pipeline: Basic Steps (workflow-basic-steps): 2.12 Pipeline: Declarative Extension Points API (pipeline-model-extensions): 1.3.2 Pipeline: Build Step (pipeline-build-step): 2.7 Pipeline: Stage Step (pipeline-stage-step): 2.3 Pipeline: Nodes and Processes (workflow-durable-task-step): 2.26 Pipeline: Model API (pipeline-model-api): 1.3.2 Pipeline: Declarative (pipeline-model-definition): 1.3.2 Pipeline: SCM Step (workflow-scm-step): 2.7 Pipeline: API (workflow-api): 2.31 Pipeline: Input Step (pipeline-input-step): 2.8 Labels: pipelines workflow-cps pipeline:groovy Priority: Minor
[JIRA] (JENKINS-48415) Pipeline PowerShell won't execute when there's spaces in the path
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-48415 Pipeline PowerShell won't execute when there's spaces in the path Change By: Vivek Pandey Labels: triaged-2018-11 windows Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45303) Slashes in branch names cause 'bat' task error
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-45303 Slashes in branch names cause 'bat' task error Change By: Vivek Pandey Labels: triaged-2018-11 windows Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47195) Information output stream is suppressed when returnStdOut = true
Title: Message Title Vivek Pandey resolved as Fixed Fixed by https://github.com/jenkinsci/durable-task-plugin/pull/45 Jenkins / JENKINS-47195 Information output stream is suppressed when returnStdOut = true Change By: Vivek Pandey Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
