[JIRA] (JENKINS-62039) Jenkins ping thread freezing other threads
Title: Message Title Jeff Thompson commented on JENKINS-62039 Re: Jenkins ping thread freezing other threads It doesn't look like there is enough information here to be able to diagnose much. I don't know what to suggest that would be needed. Is this a repeated problem? Are you able to reproduce it? How did you identify the ping thread as the problem? 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.205930.1587708338000.17493.1587756000134%40Atlassian.JIRA.
[JIRA] (JENKINS-61851) Repeated build failures after agent disconnection
Title: Message Title Jeff Thompson commented on JENKINS-61851 Re: Repeated build failures after agent disconnection So, it worked fine with a regular TCP connection but is now giving problems with a WebSocket connection? We're hoping that the WebSocket mechanism will be more reliable and avoid some of the problems, by reusing more standard ports and networking. My guess would be something to do with the proxy, firewalls, or anything like that. These sorts of issues are usually caused by something external to the agent (Remoting) implementation that causes the base socket connection to close. Maybe something is different in the networking connection for WebSocket to the standard Jenkins port than to the Agent TCP connection port. Good luck on the troubleshooting and please let us know what you find. 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.205714.1586438248000.4.1586887140141%40Atlassian.JIRA.
[JIRA] (JENKINS-61409) Websocket connections crash if message size is greater than 64Kb
Title: Message Title Jeff Thompson commented on JENKINS-61409 Re: Websocket connections crash if message size is greater than 64Kb The Remoting 4.2.1 release is out and available in repo.jenkins.io. The release notes are at https://github.com/jenkinsci/remoting/releases/tag/remoting-4.2.1 . I put together a PR to integrate that version into the 2.222.x LTS Jenkins branch at https://github.com/jenkinsci/jenkins/pull/4635 . 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.7918.1586308200373%40Atlassian.JIRA.
[JIRA] (JENKINS-61409) Websocket connections crash if message size is greater than 64Kb
Title: Message Title Jeff Thompson commented on JENKINS-61409 Re: Websocket connections crash if message size is greater than 64Kb I agree with Jesse. I don't see any risk to previously existing functionality for this change to better support WebSockets. I'm in the middle of preparing a 4.2.1 patch containing just the WebSockets fix over 4.2. That eliminates any concern over https://github.com/jenkinsci/remoting/pull/369 . 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.7902.1586304660390%40Atlassian.JIRA.
[JIRA] (JENKINS-61409) Websocket connections crash if message size is greater than 64Kb
Title: Message Title Jeff Thompson commented on JENKINS-61409 Re: Websocket connections crash if message size is greater than 64Kb Should I create that intermediate version of Remoting, without those minor cleanup 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.205063.1583801943000.6293.1585938840338%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-48865) JNLP Agents/Slaves Disconnecting Unpredictably
Title: Message Title Jeff Thompson commented on JENKINS-48865 Re: JNLP Agents/Slaves Disconnecting Unpredictably As I mentioned previously, these sorts of issues are almost always caused by some problem in the local environment. Something to do with system, network, or environment configuration. Sometimes it results from a conflict between plugins or job execution errors, which mistakenly appear as Remoting issues. All of these types of issues require troubleshooting in the local environment. Without providing a substantial amount of troubleshooting data, which usually ends up identifying the configuration issue anyway, there is nothing that anyone else can do. Frequently with these issues, when someone reports they have the same issue, it often turns out to be something quite different. Alfred's, earlier here, is an excellent example. On another similar ticket, there were multiple reports from different people as to how they resolved the issue, most of them different. If someone can provide sufficient diagnostics or reproduction steps, I'd be happy to take a look. Even better, submit a PR, as several people have done. 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.187658.1515512966000.11194.1584974640204%40Atlassian.JIRA.
[JIRA] (JENKINS-61051) Jobs are started on master instead of EC2 slaves randomly
Title: Message Title Jeff Thompson commented on JENKINS-61051 Re: Jobs are started on master instead of EC2 slaves randomly That sounds like it is an issue in the EC2 plugin. Possibly a timing problem. Presumably if the IP address isn't specified it runs the job on the master. 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.204531.158142564.4394.1583877180238%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 As WebSocket is a beta feature, there is no expectation that it would be backported from 2.217 to an earlier LTS. The first LTS to have WebSocket will be the one following 2.217. It looks like that is going to be based on 2.222 and should be out within the coming weeks. 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.2801.1583163060127%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 You need to upgrade to a later Jenkins version. The server side components went into Jenkins 2.217. 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.879.1582830420295%40Atlassian.JIRA.
[JIRA] (JENKINS-61253) Remoting using WebSocket fails with "Handshake response not received" Exception
Title: Message Title Jeff Thompson closed an issue as Not A Defect Jenkins / JENKINS-61253 Remoting using WebSocket fails with "Handshake response not received" Exception Change By: Jeff Thompson 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.204820.1582797002000.881.1582830420321%40Atlassian.JIRA.
[JIRA] (JENKINS-61224) "Monitors" terminology should not be used in GUI
Title: Message Title Jeff Thompson commented on JENKINS-61224 Re: "Monitors" terminology should not be used in GUI I've had the same concerns with naming on these things before. The API name isn't a good term for users, but it got picked up and used in UI a number of places. I think the best term is "alert". I don't have much of an opinion on Jesse's latter suggestion of removing the word entirely. I guess I would have a slight, soft preference for retaining text with better wording. 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.204778.158264254.21.1582739160227%40Atlassian.JIRA.
[JIRA] (JENKINS-61051) Jobs are started on master instead of EC2 slaves randomly
Title: Message Title Jeff Thompson commented on JENKINS-61051 Re: Jobs are started on master instead of EC2 slaves randomly I'm not familiar with the details of the ec2-plugin, but I know it does some complicated stuff, including with how it manages agents. When I've looked into the code there before, there was some complicated pieces. If you can reproduce the problems without the ec2-plugin then it probably is due to something in the Jenkins server. (Since I'm not familiar with any reports on that, it seems unlikely.) If it only occurs with the ec2-plugin, then it's probably something to do with the custom capabilities it provides. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204531.158142564.8250.1581533280157%40Atlassian.JIRA.
[JIRA] (JENKINS-61051) Jobs are started on master instead of EC2 slaves randomly
Title: Message Title Jeff Thompson assigned an issue to Unassigned Jenkins / JENKINS-61051 Jobs are started on master instead of EC2 slaves randomly Change By: Jeff Thompson Assignee: Jeff Thompson Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204531.158142564.7453.1581440280397%40Atlassian.JIRA.
[JIRA] (JENKINS-61051) Jobs are started on master instead of EC2 slaves randomly
Title: Message Title Jeff Thompson commented on JENKINS-61051 Re: Jobs are started on master instead of EC2 slaves randomly This probably doesn't have anything to do with Remoting. It's probably something about the ec2-plugin not launching the job in the right place or using the desired agent configuration. My guess is that it's going to require additional diagnostics in order to track this down. Anything you can do to collect better troubleshooting data or a reproducible scenario would likely be necessary to resolving this. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204531.158142564.7451.1581440220218%40Atlassian.JIRA.
[JIRA] (JENKINS-61023) Jenkins slave threads deadlock due to remoting.jar
Title: Message Title Jeff Thompson commented on JENKINS-61023 Re: Jenkins slave threads deadlock due to remoting.jar As described on the page you link to, you'll need to provide further information before anything can be done with this report. There is insufficient here for any action. Things you will need to investigate include: versions used, types of agents used, operations of the different threads, what the agents are doing, etc. Most of the time, issues like this are caused by something external to the Remoting library. These things can be system, network, or configuration. It might be a misbehaving plugin or interaction between multiple plugins. Issues like this usually cannot be addressed without providing a reproducible scenario or sufficient diagnostics. Best of luck in troubleshooting and isolating the problem. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204496.1581259936000.5590.1581359220118%40Atlassian.JIRA.
[JIRA] (JENKINS-60913) Remove network discovery services
Title: Message Title Jeff Thompson commented on JENKINS-60913 Re: Remove network discovery services Oleg Nenashev, I'm not sure what you're asking for. You wanted a reference to the ticket Jesse mentioned to also be included in the PR on GitHub? I noticed that you said you were going to do something like that, so I figured you would take care of what you thought was needed. And it was already mentioned here and at least one other place. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204304.158033844.5558.1581355440160%40Atlassian.JIRA.
[JIRA] (JENKINS-60926) Agent Windows service installation broken
Title: Message Title Jeff Thompson commented on JENKINS-60926 Re: Agent Windows service installation broken Fixed in Remoting 4.1. Jenkins PR to pull in the new Remoting version: https://github.com/jenkinsci/jenkins/pull/4464 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204323.1580417035000.9069.1580420820101%40Atlassian.JIRA.
[JIRA] (JENKINS-60926) Agent Windows service installation broken
Title: Message Title Jeff Thompson created an issue Jenkins / JENKINS-60926 Agent Windows service installation broken Issue Type: Bug Assignee: Jeff Thompson Components: remoting Created: 2020-01-30 20:43 Priority: Minor Reporter: Jeff Thompson A renaming clean up in Remoting 4.0 broke the complicated interaction with the master and the slave-installer-module that allows a user on a Windows machine to install the inbound agent as a Windows Service. With this bug, the "File" menu no longer appears, meaning the "Install as a service" menu item doesn't exist. The fix is simple, to rename one public field back to what it was. This change went into Jenkins 2.217 one week ago on 23 January 2020. Add Comment
[JIRA] (JENKINS-54496) Node monitoring should not log exceptions for disconnected nodes
Title: Message Title Jeff Thompson commented on JENKINS-54496 Re: Node monitoring should not log exceptions for disconnected nodes Argghh. Yes. I use the "g" version on a number of other places and mistyped it once I started. I got the PR. I'll review it today hopefully. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195266.1541524267000.8939.1580397780139%40Atlassian.JIRA.
[JIRA] (JENKINS-54496) Node monitoring should not log exceptions for disconnected nodes
Title: Message Title
Jeff Thompson edited a comment on JENKINS-54496
Re: Node monitoring should not log exceptions for disconnected nodes
This makes good sense. I'm glad you were able to dig into it further and isolate the spurious messages you've been seeing. It would be great if you can see if that eliminates the issue for you. Even if you can't verify it it's probably a reasonable check. If you want to submit a PR for it, mention me so I can be sure to review ("jeffret- g b " on GitHub). Or I could see about submitting the PR sometime.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195266.1541524267000.8937.1580397720114%40Atlassian.JIRA.
[JIRA] (JENKINS-60913) Remove network discovery services
Title: Message Title Jeff Thompson created an issue Jenkins / JENKINS-60913 Remove network discovery services Issue Type: Task Assignee: Jeff Thompson Components: core Created: 2020-01-29 22:54 Priority: Minor Reporter: Jeff Thompson Dating back many years, Jenkins has supported two network discovery services (UDP multicast/broadcast and DNS multicast). When this was first implemented this may have been a reasonable way to provide useful lookup services. With modern Jenkins capabilities, networks, and security considerations, this is no longer a good mechanism. There are now other ways to accomplish the real needs and concerns with doing it this way. With [Jenkins Security Advisory 2020-01-29|https://jenkins.io/security/advisory/2020-01-29/|https://jenkins.io/security/advisory/2020-01-29/] these services were disabled by default because of SECURITY-1641 / CVE-2020-2100. These should just be removed. Add Comment
[JIRA] (JENKINS-54496) Node monitoring should not log exceptions for disconnected nodes
Title: Message Title
Jeff Thompson commented on JENKINS-54496
Re: Node monitoring should not log exceptions for disconnected nodes
This makes good sense. I'm glad you were able to dig into it further and isolate the spurious messages you've been seeing. It would be great if you can see if that eliminates the issue for you. Even if you can't verify it it's probably a reasonable check. If you want to submit a PR for it, mention me so I can be sure to review ("jeffret-g" on GitHub). Or I could see about submitting the PR sometime.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195266.1541524267000.8466.1580332260127%40Atlassian.JIRA.
[JIRA] (JENKINS-60848) RSS feed titles inconsistent and messy
Title: Message Title Jeff Thompson created an issue Jenkins / JENKINS-60848 RSS feed titles inconsistent and messy Issue Type: Improvement Assignee: Jeff Thompson Components: core Created: 2020-01-23 21:24 Priority: Minor Reporter: Jeff Thompson The feed titles in the various RSS feeds around Jenkins are inconsistent, confusing, and weird. Some of them show "All all builds". Some have "Hudson log". These can be cleaned up with consistent naming and formatting. Add Comment This message was sent
[JIRA] (JENKINS-60563) Remove MD5
Title: Message Title Jeff Thompson commented on JENKINS-60563 Re: Remove MD5 I don't know what you intended with that PR Wadeck Follonier but it doesn't seem to be connected to his ticket. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203672.1576874352000.4455.1579792920107%40Atlassian.JIRA.
[JIRA] (JENKINS-56564) Jenkins CLI unable to create job - hudson.cli.DiagnosedStreamCorruptionException
Title: Message Title Jeff Thompson closed an issue as Cannot Reproduce Jenkins / JENKINS-56564 Jenkins CLI unable to create job - hudson.cli.DiagnosedStreamCorruptionException Change By: Jeff Thompson Status: Reopened Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198179.1552579984000.8924.1579120620395%40Atlassian.JIRA.
[JIRA] (JENKINS-56564) Jenkins CLI unable to create job - hudson.cli.DiagnosedStreamCorruptionException
Title: Message Title Jeff Thompson commented on JENKINS-56564 Re: Jenkins CLI unable to create job - hudson.cli.DiagnosedStreamCorruptionException a b your issue sounds different from the originally reported issue. You don't mention upgrade and the use of the Remoting transport for CLI. You may be getting a similar or even the same error message, though that isn't clear. You need to create your own ticket and provide better information instead of re-opening this one. Further, I'm able to get the CLI to work fine according to the documentation and don't see the error reported earlier. This suggests that you've probably got usage or configuration problems. Possibly network or system problems. You would need to provide a reproducible issue description. The Jenkins issue tracker is not a support forum. You may get better help from the Jenkins User email list or gitter channel. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198179.1552579984000.8916.1579116480217%40Atlassian.JIRA.
[JIRA] (JENKINS-60563) Remove MD5
Title: Message Title Jeff Thompson updated an issue Jenkins / JENKINS-60563 Remove MD5 Change By: Jeff Thompson Remove out-dated, problematic MD5 hash from Jenkins.Relates to core and possibly many other components and polugins plugins . Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203672.1576874352000.14327.1576874400229%40Atlassian.JIRA.
[JIRA] (JENKINS-60563) Remove MD5
Title: Message Title Jeff Thompson created an issue Jenkins / JENKINS-60563 Remove MD5 Issue Type: Improvement Assignee: Unassigned Components: core Created: 2019-12-20 20:39 Priority: Minor Reporter: Jeff Thompson Remove out-dated, problematic MD5 hash from Jenkins. Relates to core and possibly many other components and polugins. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60562) Remove deprecated classes
Title: Message Title Jeff Thompson commented on JENKINS-60562 Re: Remove deprecated classes See https://github.com/jenkinsci/jenkins/pull/4386 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203671.1576873969000.14325.1576874160052%40Atlassian.JIRA.
[JIRA] (JENKINS-60562) Remove deprecated classes
Title: Message Title Jeff Thompson moved an issue Jenkins / JENKINS-60562 Remove deprecated classes Change By: Jeff Thompson Project: Security Issues Jenkins Key: SECURITY JENKINS - 1701 60562 Workflow: Security v1.2 JNJira + In-Review Status: Untriaged Open Component/s: core Component/s: core Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60410) Suppress stack traces in core
Title: Message Title Jeff Thompson created an issue Jenkins / JENKINS-60410 Suppress stack traces in core Issue Type: Improvement Assignee: Jeff Thompson Components: core Created: 2019-12-09 18:53 Priority: Minor Reporter: Jeff Thompson I propose to move the capability from the Suppress Stack Trace Plugin into core and clean it up a little bit. The existing plugin behavior is to show the trace to administrators and to connect it to a specific log message for other users. I propose to retain this behavior. Jenkins has seen a significant rise in security-conscious use since this plugin was created. Jenkins should be more secure by default. While showing the stack trace isn't a security vulnerability, not showing the trace is standard, expected industry behavior. Add Comment
[JIRA] (JENKINS-58736) Accessing "/assets" without asset name throws a 500
Title: Message Title Jeff Thompson resolved as Fixed Jenkins / JENKINS-58736 Accessing "/assets" without asset name throws a 500 Change By: Jeff Thompson Status: Open Resolved Resolution: Fixed Released As: 2.190 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201037.1564557798000.1879.1575587340315%40Atlassian.JIRA.
[JIRA] (JENKINS-60381) Remove old, deprecated remoting protocols
Title: Message Title Jeff Thompson created an issue Jenkins / JENKINS-60381 Remove old, deprecated remoting protocols Issue Type: Improvement Assignee: Jeff Thompson Components: core, remoting Created: 2019-12-05 16:48 Priority: Minor Reporter: Jeff Thompson For historical reasons, Jenkins still ships with old, deprecated protocols, JNLP1-connect, JNLP2-connect, and JNLP3-connect. These all have fundamental issues and known bugs. They were all superseded by the JNLP4-connect protocol released in Jenkins 2.27 over three years ago (October 2016). They have all been deprecated and unsupported since Jenkins 2.75 over two years ago. Since then there have been UI messages and an administrative monitor strongly discouraging their use. (See more information about the protocols at https://github.com/jenkinsci/remoting/blob/master/docs/protocols.md ) These protocols should be removed as part of cleaning up technical debt. See the discussion at https://groups.google.com/forum/#!topic/jenkinsci-users/s90MVVdFDyU Add Comment
[JIRA] (JENKINS-57143) JNLP4 error: "Connection closed before acknowledgement sent"
Title: Message Title Jeff Thompson commented on JENKINS-57143 Re: JNLP4 error: "Connection closed before acknowledgement sent" It would be nice to get some time to see about getting some of that in. Better diagnosability would be a nice addition. Yeah, I wonder why it needs to reverse resolve. Would take some time to figure out what and why it's doing there. Thanks! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198893.1555967243000.195.1575483660206%40Atlassian.JIRA.
[JIRA] (JENKINS-57143) JNLP4 error: "Connection closed before acknowledgement sent"
Title: Message Title Jeff Thompson commented on JENKINS-57143 Re: JNLP4 error: "Connection closed before acknowledgement sent" Any ideas what we could do to better handle this situation? Or provide better diagnostics? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198893.1555967243000.183.1575483300304%40Atlassian.JIRA.
[JIRA] (JENKINS-57143) JNLP4 error: "Connection closed before acknowledgement sent"
Title: Message Title Jeff Thompson commented on JENKINS-57143 Re: JNLP4 error: "Connection closed before acknowledgement sent" Nathan Neulinger, thanks for sharing your experience. It may help give others some ideas on where to investigate if they see similar problems. Were you seeing similar log messages as originally reported? If not, it might be a somewhat different issue. DNS configuration issues can cause lots of weird, problems that don't appear related. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198893.1555967243000.175.1575482460314%40Atlassian.JIRA.
[JIRA] (JENKINS-60188) Windows JNLP Agent SSLException
Title: Message Title Jeff Thompson commented on JENKINS-60188 Re: Windows JNLP Agent SSLException Thanks for sharing. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203151.157383253.4561.1574267880131%40Atlassian.JIRA.
[JIRA] (JENKINS-60188) Windows JNLP Agent SSLException
Title: Message Title Jeff Thompson commented on JENKINS-60188 Re: Windows JNLP Agent SSLException Ram krish, did you figure out your problem here? If it's a configuration issue others may encounter it might help if you could describe the situation and resolution in case others run into it. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203151.157383253.3856.1574182920143%40Atlassian.JIRA.
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Jeff Thompson commented on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted It looks like people are seeing a number of different issues, generally involving the same error message. Some people report success by tracking down a different machine running the same agent. Some find that some cleanup corrects the problem, though it's not clear just what cleanup is required. In some cases it probably involves a connection timeout and the server thinks an old instance of the agent is still connected. As Oleg said earlier, to get anywhere with this will require clear reproduction documentation and both agent and master logs. Information on whether it is specific to a certain type of platform or environment would also be important. I see some mention of different versions of Windows OSes but it's not clear if it's just a Windows issue and if it only occurs in some Windows environments or versions. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164090.1437742638000.4780.1572375060875%40Atlassian.JIRA.
[JIRA] (JENKINS-59889) Cannot start new Jenkins with agent.jar file
Title: Message Title Jeff Thompson commented on JENKINS-59889 Re: Cannot start new Jenkins with agent.jar file I'm glad you were able to figure that out. Thanks for updating this – in case someone else sees a similar problem they could learn from this. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202634.1571753869000.18456.1571847780138%40Atlassian.JIRA.
[JIRA] (JENKINS-59889) Cannot start new Jenkins with agent.jar file
Title: Message Title Jeff Thompson commented on JENKINS-59889 Re: Cannot start new Jenkins with agent.jar file This is a weird one and I don't have any suggestions for you. There was a recent update to the jna library in Jenkins core, but that doesn't explain why you are seeing this behavior. Some discussion on the web about this error with JNA involves permissions or capacity on a temp dir, but that seems to be more focused on Unix OSes. You might try to reproduce this on other machines if you can and see if it's specific to just that one instance. Other people haven't reported this issue so it might just be a machine issue. You could try posting in the Jenkins user email list or gitter channel and see if anyone else has seen anything like this. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202634.1571753869000.13505.1571778660139%40Atlassian.JIRA.
[JIRA] (JENKINS-51191) hudson.remoting.Channel$CallSiteStackTrace: Remote call to
Title: Message Title Jeff Thompson commented on JENKINS-51191 Re: hudson.remoting.Channel$CallSiteStackTrace: Remote call to Interesting. I don't know what would have caused that change. I just scanned the Java changelog and didn't see any obvious causes. Thanks for sharing the info here! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190504.1525766236000.9708.1571323891074%40Atlassian.JIRA.
[JIRA] (JENKINS-59403) agent fails immediately when started in a docker-compose cluster
Title: Message Title Jeff Thompson commented on JENKINS-59403 Re: agent fails immediately when started in a docker-compose cluster We've had a couple of attempts to augment or change the startup process lately, some which were eventually successful and some which failed. The key to success has been a clearly defined use case and flow. If we can figure that out for this scenario, this could be a nice enhancement. I'm always a little concerned about approaches that just wait for some arbitrary amount of time, which may work but not always. Though, if the alternative is to just wait forever, a timeout may not be a bad idea. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201960.156870580.5189.1569430860118%40Atlassian.JIRA.
[JIRA] (JENKINS-56578) Jenkins 2.168 prevent HTML Publisher to copy html report from agent to master
Title: Message Title Jeff Thompson commented on JENKINS-56578 Re: Jenkins 2.168 prevent HTML Publisher to copy html report from agent to master This does look like something caused by a change in Jenkins 2.168. I don't think it has anything to do with htmlpublisher plugin, so I've removed it from the components field. Specifically it is highly likely that the change for JENKINS-56114 caused this. This is similar to JENKINS-56249. Though the exact manifestations and cause are different, they concern the same areas of code. I'll see if I can figure something out to make it work better. It may take a while to get that change put together. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198193.1552641703000.4494.1569362160267%40Atlassian.JIRA.
[JIRA] (JENKINS-56578) Jenkins 2.168 prevent HTML Publisher to copy html report from agent to master
Title: Message Title Jeff Thompson updated an issue Jenkins / JENKINS-56578 Jenkins 2.168 prevent HTML Publisher to copy html report from agent to master Change By: Jeff Thompson Component/s: htmlpublisher-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198193.1552641703000.4480.1569361680344%40Atlassian.JIRA.
[JIRA] (JENKINS-56578) Jenkins 2.168 prevent HTML Publisher to copy html report from agent to master
Title: Message Title Jeff Thompson edited a comment on JENKINS-56578 Re: Jenkins 2.168 prevent HTML Publisher to copy html report from agent to master ( I 'm trying to clarify the situations that lead to deleted this problem. It doesn't seem to be a general failure with htmlpublisher, as comment because it seems to work fine for me and there are relatively few people chiming in on this looks like I misread who was saying what . As [~rvangoethem] describes their experience, this issue involves junctions or symlinks further up the directory tree (somewhere in the job I ' s directory parentage) ll try again . By changing the configuration to not use symlinks, they no longer experienced these problems. Is that an accurate summary?[~r2b2_nz], is your configuration similar? Do you symlinks or junctions somewhere in the directory tree?I can see that 2.168 may have introduced changes that would cause problems in these sorts of configurations. ) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198193.1552641703000.4475.1569361620195%40Atlassian.JIRA.
[JIRA] (JENKINS-56578) Jenkins 2.168 prevent HTML Publisher to copy html report from agent to master
Title: Message Title Jeff Thompson commented on JENKINS-56578 Re: Jenkins 2.168 prevent HTML Publisher to copy html report from agent to master I'm trying to clarify the situations that lead to this problem. It doesn't seem to be a general failure with htmlpublisher, as it seems to work fine for me and there are relatively few people chiming in on this. As Remi Van Goethem describes their experience, this issue involves junctions or symlinks further up the directory tree (somewhere in the job's directory parentage). By changing the configuration to not use symlinks, they no longer experienced these problems. Is that an accurate summary? Richard Bywater, is your configuration similar? Do you symlinks or junctions somewhere in the directory tree? I can see that 2.168 may have introduced changes that would cause problems in these sorts of configurations. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198193.1552641703000.4470.1569361020209%40Atlassian.JIRA.
[JIRA] (JENKINS-56249) userContent *zip* (all files in zip) stopped working at 2.164
Title: Message Title Jeff Thompson commented on JENKINS-56249 Re: userContent *zip* (all files in zip) stopped working at 2.164 I'm able to reproduce Matt's simple test case on Unix and Windows. Hopefully it's a reasonably good representation of the other problems people are experiencing. Looks like the `allowSymlinkEscape` property isn't working the way it was intended. I'll see if I can figure something out to make it work better. It may take a while to get that change put together. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197816.1550852223000.3749.1569277980212%40Atlassian.JIRA.
[JIRA] (JENKINS-56249) userContent *zip* (all files in zip) stopped working at 2.164
Title: Message Title Jeff Thompson commented on JENKINS-56249 Re: userContent *zip* (all files in zip) stopped working at 2.164 Glenn Herbert and Arjo Poldervaart, thanks for your responses on describing your use models. That helps clarify some things. Have you read the security advisory from last year at https://jenkins.io/security/advisory/2018-12-05/ ? Have you tried disabling that fix via the system property described there? It sounds like your use cases are some of the rare situations where that might make sense. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197816.1550852223000.2101.1569017700193%40Atlassian.JIRA.
[JIRA] (JENKINS-56249) userContent *zip* (all files in zip) stopped working at 2.164
Title: Message Title Jeff Thompson commented on JENKINS-56249 Re: userContent *zip* (all files in zip) stopped working at 2.164 And which of those use cases involve userContent, as described in the OP? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197816.1550852223000.1444.1568928840198%40Atlassian.JIRA.
[JIRA] (JENKINS-56249) userContent *zip* (all files in zip) stopped working at 2.164
Title: Message Title Jeff Thompson commented on JENKINS-56249 Re: userContent *zip* (all files in zip) stopped working at 2.164 Arjo Poldervaart, could you clarify some of your use cases for symlinks? How do you use them? Where do they link from and to? Do they link from inside a workspace to somewhere else on the system? Anyone else, please respond also, about your need for symlink support. I'm especially interested in how your symlink use works with zip files, as featured in the OP. Zip files generated by Jenkins do not contain symlinks but may resolve the symlink to the target and include all of that. One scenario, described in JENKINS-56114, involves a master or agent which resides in a path containing a symlink at the root or somewhere else higher in the path. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197816.1550852223000.1431.1568927340340%40Atlassian.JIRA.
[JIRA] (JENKINS-59399) 404 when trying to connect Windows node to Linux Master
Title: Message Title Jeff Thompson commented on JENKINS-59399 Re: 404 when trying to connect Windows node to Linux Master I'm glad you got it working. Thanks for sharing your steps to resolve this and the results. In the future, posting to the Jenkins Users email list or the Gitter channel would probably be better places to get responses on issues like this. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201956.156824000.635.1568825940139%40Atlassian.JIRA.
[JIRA] (JENKINS-59094) Agent tunnel connection issues after ugrading Jenkins to 2.191
Title: Message Title Jeff Thompson commented on JENKINS-59094 Re: Agent tunnel connection issues after ugrading Jenkins to 2.191 Great! I'm glad that solved it for you. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201514.1566889039000.184.1568040720212%40Atlassian.JIRA.
[JIRA] (JENKINS-59094) Agent tunnel connection issues after ugrading Jenkins to 2.191
Title: Message Title Jeff Thompson resolved as Fixed Jenkins / JENKINS-59094 Agent tunnel connection issues after ugrading Jenkins to 2.191 Change By: Jeff Thompson Status: In Progress Resolved Resolution: Fixed Released As: Remoting 3.35 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201514.1566889039000.8433.1567793760465%40Atlassian.JIRA.
[JIRA] (JENKINS-59094) Agent tunnel connection issues after ugrading Jenkins to 2.191
Title: Message Title Jeff Thompson commented on JENKINS-59094 Re: Agent tunnel connection issues after ugrading Jenkins to 2.191 The problem turned out to be related to tunneling configurations, when the tunnel HOST:PORT is missing the HOST and / or PORT specification. In my change for Remoting 3.34, I had missed some magic whereby the values are filled in from prior sources. Remoting 3.3.5 restores these configuration paths / options and retains the new capabilities introduced in 3.34. I couldn't find any connection between this issue and the Windows platform, as the original title stated, so I've changed the title to better reflect the actual 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201514.1566889039000.8430.1567792800454%40Atlassian.JIRA.
[JIRA] (JENKINS-59094) Agent tunnel connection issues after ugrading Jenkins to 2.191
Title: Message Title Jeff Thompson commented on JENKINS-59094 Re: Agent tunnel connection issues after ugrading Jenkins to 2.191 Dzianis Mazuronak, I had planned to have an incrementals version published to the Jenkins Artifactory repository that you could consider testing. Unfortunately, it's not fully set up for that yet, but there are changes in the works to enable it. Without that, it is definitely harder to test. I'll see if anyone else is able to perform any reviews or tests. I hope to get Remoting released early next and included in the following Jenkins weekly. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201514.1566889039000.3439.1567193460196%40Atlassian.JIRA.
[JIRA] (JENKINS-55689) Not able to connect to jenkins master from windows slave
Title: Message Title Jeff Thompson commented on JENKINS-55689 Re: Not able to connect to jenkins master from windows slave Punith Shetty, thanks for responding with your success and describing the solution that worked for you. That helps others who might encounter a similar problem. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196875.1547848244000.2874.1567095240229%40Atlassian.JIRA.
[JIRA] (JENKINS-59094) Agent tunnel connection issues after ugrading Jenkins to 2.191
Title: Message Title Jeff Thompson commented on JENKINS-59094 Re: Agent tunnel connection issues after ugrading Jenkins to 2.191 I updated the title to something that I think is a little clearer and more accurate. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201514.1566889039000.2348.1567031220422%40Atlassian.JIRA.
[JIRA] (JENKINS-59094) Agent tunnel connection issues after ugrading Jenkins to 2.191
Title: Message Title Jeff Thompson updated an issue Jenkins / JENKINS-59094 Agent tunnel connection issues after ugrading Jenkins to 2.191 Change By: Jeff Thompson Summary: Windows Agent tunnel connection issues after ugrading Jenkins to 2.191 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201514.1566889039000.2346.1567031220390%40Atlassian.JIRA.
[JIRA] (JENKINS-59094) Windows Agent connection issues after ugrading Jenkins to 2.191
Title: Message Title Jeff Thompson commented on JENKINS-59094 Re: Windows Agent connection issues after ugrading Jenkins to 2.191 PR uploaded at https://github.com/jenkinsci/remoting/pull/345 . This PR restores the parsing behavior for empty port and for empty host. The separator character is still required. I haven't been able to reproduce or test these other scenarios. It would be great if someone else with those setups could give it a try. If we can get some more reviews or testing, I should be able to get a new version out quickly. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201514.1566889039000.2287.1567030080192%40Atlassian.JIRA.
[JIRA] (JENKINS-55689) Not able to connect to jenkins master from windows slave
Title: Message Title Jeff Thompson closed an issue as Incomplete Jenkins / JENKINS-55689 Not able to connect to jenkins master from windows slave Change By: Jeff Thompson Status: Reopened Closed Resolution: Incomplete 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196875.1547848244000.2129.1567003980919%40Atlassian.JIRA.
[JIRA] (JENKINS-55689) Not able to connect to jenkins master from windows slave
Title: Message Title Jeff Thompson commented on JENKINS-55689 Re: Not able to connect to jenkins master from windows slave Have you asked on the Jenkins users email list as suggested? Or the gitter channel? This looks like a usage or configuration question and not a specific defect. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196875.1547848244000.2124.1567003980800%40Atlassian.JIRA.
[JIRA] (JENKINS-59094) Windows Agent connection issues after ugrading Jenkins to 2.191
Title: Message Title Jeff Thompson commented on JENKINS-59094 Re: Windows Agent connection issues after ugrading Jenkins to 2.191 Hmmm Actually one of my test systems does use a random port. But none are set up for tunneling, proxy, etc. Can you find information on the command-line arguments used to launch the agent? Depending on how you have things configured on the agent, it might be in jenkins-slave.xml. Or in some other file where the agent is installed. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201514.1566889039000.1070.1566935520352%40Atlassian.JIRA.
[JIRA] (JENKINS-59094) Windows Agent connection issues after ugrading Jenkins to 2.191
Title: Message Title Jeff Thompson commented on JENKINS-59094 Re: Windows Agent connection issues after ugrading Jenkins to 2.191 Thanks a lot! I wondered if this might have something to do with the random port setting. I'll see if I can reproduce the problem setting up a system like that. If I create a PR for this, would you have any capability for trying it out before it's added into 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201514.1566889039000.1044.1566933960541%40Atlassian.JIRA.
[JIRA] (JENKINS-59094) Windows Agent connection issues after ugrading Jenkins to 2.191
Title: Message Title Jeff Thompson commented on JENKINS-59094 Re: Windows Agent connection issues after ugrading Jenkins to 2.191 Dzianis Mazuronak, could you clarify your configuration? The log messages indicate that you are using tunneling. Based upon the error messages, it looks like your tunnel parameter looks something like "myjenkins:", in other words, no port number is specified. Or it's specified in an unusual way I didn't account for. You could provide the parameters you use in your launch command, particularly anything relating to tunneling. You could also provide log messages from an agent connection sequence from a working Jenkins, before 2.191 that shows how the port is handled. I've got a change that might make it work like it did before but I want to make sure I'm addressing the problem before submitting. On my Windows test system I wasn't able to reproduce the problem with a basic installation. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201514.1566889039000.937.1566927480220%40Atlassian.JIRA.
[JIRA] (JENKINS-59094) Windows Agent connection issues after ugrading Jenkins to 2.191
Title: Message Title Jeff Thompson commented on JENKINS-59094 Re: Windows Agent connection issues after ugrading Jenkins to 2.191 I tested on Windows and Unix under a few configurations. Another contributor also tested a variety of other configurations. Somehow this one got missed. I'm looking into it. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201514.1566889039000.728.1566916021019%40Atlassian.JIRA.
[JIRA] (JENKINS-53461) Add support of Remoting connections to masters without Web UI
Title: Message Title Jeff Thompson resolved as Fixed Jenkins / JENKINS-53461 Add support of Remoting connections to masters without Web UI Change By: Jeff Thompson Status: In Progress Resolved Resolution: Fixed Released As: Remoting 3.34 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193928.1536315702000.8096.1566493320516%40Atlassian.JIRA.
[JIRA] (JENKINS-53461) Add support of Remoting connections to masters without Web UI
Title: Message Title Jeff Thompson commented on JENKINS-53461 Re: Add support of Remoting connections to masters without Web UI Enhancement released in Remoting 3.34, with the Remoting library released today 22 August 2019. See [change log](https://github.com/jenkinsci/remoting/releases/tag/remoting-3.34). Documentation on the new mode along with a few existing capabilities is now available at https://github.com/jenkinsci/remoting/blob/master/docs/tcpAgent.md . PR to upgrade the Remoting library in Jenkins at https://github.com/jenkinsci/jenkins/pull/4165 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193928.1536315702000.8092.1566493260671%40Atlassian.JIRA.
[JIRA] (JENKINS-53461) Add support of Remoting connections to masters without Web UI
Title: Message Title Jeff Thompson assigned an issue to Jeff Thompson Jenkins / JENKINS-53461 Add support of Remoting connections to masters without Web UI Change By: Jeff Thompson Assignee: Oleg Nenashev Jeff Thompson 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193928.1536315702000.8070.1566491880212%40Atlassian.JIRA.
[JIRA] (JENKINS-53322) Remove patched dom4j from Stapler
Title: Message Title Jeff Thompson commented on JENKINS-53322 Re: Remove patched dom4j from Stapler Stapler version 1.258 was released on 19 August 2019 containing changes to move to the standard dom4j library. Jenkins PR https://github.com/jenkinsci/jenkins/pull/4130 depends upon that version and removes dependency on the forked library. This PR is up for 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193404.153555107.6357.1566325440161%40Atlassian.JIRA.
[JIRA] (JENKINS-56217) allow to hide version number
Title: Message Title Jeff Thompson commented on JENKINS-56217 Re: allow to hide version number TcpSlaveAgentListener provides the version but I'm pretty confident it doesn't actually need to. That particular response, https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/TcpSlaveAgentListener.java#L306 , provides a little bit of troubleshooting info. Very little. We should have a flag to disable that whole response and make that the default. There is already a system property to disable UDPBroadcastThread. Auto-discovery of Jenkins on the network is hardly a necessary feature and should probably be disabled by anyone who is paranoid enough about security to hide the version elsewhere. We could ignore this one in favor of the existing property or we could include version suppression here. Inbound TCP agents use a different header here, https://github.com/jenkinsci/remoting/blob/master/src/main/java/org/jenkinsci/remoting/engine/JnlpAgentEndpointResolver.java#L208 , which contains the minimum supported Remoting version but not the Jenkins version. It may at times be possible to extract some Jenkins version info from this but we haven't updated that in well over two years so it's not very useful. I wouldn't bother with this one. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.19.1550676909000.3726.1565900220198%40Atlassian.JIRA.
[JIRA] (JENKINS-56581) org.jenkinsci.remoting.protocol.IOHub takes 100% CPU
Title: Message Title Jeff Thompson commented on JENKINS-56581 Re: org.jenkinsci.remoting.protocol.IOHub takes 100% CPU Jörg Sautter, so updating to Java 11 resolved this for you? That's great information. Any reason not to close this information, then? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198196.1552647394000.4290.1564509660231%40Atlassian.JIRA.
[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins
Title: Message Title Jeff Thompson commented on JENKINS-55945 Re: Got IllegalStateException while restart Jenkins Simon Tunnat, as I mentioned above, you can read about the LTS releases, including backports, at https://jenkins.io/download/lts/ 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197354.1549278137000.3008.1564416121041%40Atlassian.JIRA.
[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins
Title: Message Title Jeff Thompson commented on JENKINS-55945 Re: Got IllegalStateException while restart Jenkins Simon Tunnat, you are welcome to request this change be backported. Since supjac m, determined their continued failures were unrelated I no longer object to backporting. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197354.1549278137000.1291.1564087080466%40Atlassian.JIRA.
[JIRA] (JENKINS-56581) org.jenkinsci.remoting.protocol.IOHub takes 100% CPU
Title: Message Title Jeff Thompson commented on JENKINS-56581 Re: org.jenkinsci.remoting.protocol.IOHub takes 100% CPU Interesting. It would be great if this resolves the issues you are seeing. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198196.1552647394000.1288.1564086900172%40Atlassian.JIRA.
[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins
Title: Message Title Jeff Thompson commented on JENKINS-55945 Re: Got IllegalStateException while restart Jenkins That explains your observations, Guilherme Emiliano Zanella. The change went into the 2.185 weekly release. You've got the latest LTS release, which doesn't have this change. You could request this change be backported to the next incremental release of the LTS. I would be hesitant to backport this, given its experimental nature and we have a report of the change not fixing things for someone. You could switch from using the LTS line to the weekly. See [LTS Release Line](https://jenkins.io/download/lts/) for more information. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197354.1549278137000.19441.1563895384239%40Atlassian.JIRA.
[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins
Title: Message Title Jeff Thompson commented on JENKINS-55945 Re: Got IllegalStateException while restart Jenkins Guilherme Emiliano Zanella, I'm not sure what version that will give you. When you run Jenkins, which version does it say you have? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197354.1549278137000.18359.1563832140663%40Atlassian.JIRA.
[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins
Title: Message Title Jeff Thompson commented on JENKINS-55945 Re: Got IllegalStateException while restart Jenkins Guilherme Emiliano Zanella, double-check your versions and make sure you've got the version of Jenkins that contains the change. The line numbers of your stack trace don't line up with changed version. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197354.1549278137000.18311.1563827760511%40Atlassian.JIRA.
[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins
Title: Message Title Jeff Thompson commented on JENKINS-55945 Re: Got IllegalStateException while restart Jenkins supjac m, I was afraid the fix would shift the error around somehow. Since Pavel Roskin reported the fix worked for their scenarios, I decided to submit it to see if it helped some people. It's interesting that, in your case at least, that it seems to start immediately after the "Jenkins stopped" message. Maybe there's something going on right at the start of the init sequence. Or maybe even before it somehow. Unfortunately, as I've been unable to reproduce the problem I've gone as far as I can with it. If someone else can figure out how to get more information about it or come with a proposal that would be great. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197354.1549278137000.12461.1563292320514%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins
Title: Message Title Jeff Thompson commented on JENKINS-55945 Re: Got IllegalStateException while restart Jenkins Inspired by Pavel Roskin's patch, I submitted a PR about this issue: https://github.com/jenkinsci/jenkins/pull/4107 If anyone affected by this issue would like to review, comment, or especially test that proposal, please do. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197354.1549278137000.5908.1562703720467%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins
Title: Message Title Jeff Thompson commented on JENKINS-55945 Re: Got IllegalStateException while restart Jenkins Thanks Pavel Roskin. That's what I was thinking of trying. At least you can test that it works. Would you like to submit a PR for that? If you do, be sure to @mention me (@jeffret-b on GitHub). I'm looking into an ATH test that is supposed to duplicate this issue but I haven't been able to get it configured correctly yet. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197354.1549278137000.1452.1562192041244%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins
Title: Message Title Jeff Thompson commented on JENKINS-55945 Re: Got IllegalStateException while restart Jenkins I tried that same sequence several times and still couldn't reproduce it. Frustrating. One possible approach might be to catch the exception in `hasInvalidSessionSeed()` and return false. That might do the job, but it's hard to be confident without being able to reproduce the issue. One argument against that approach is that the exception is correct – it's in an invalid state. Ignoring it here may just allow it to continue on to other issues. This one, at least, doesn't seem too hazardous. Another possible approach might be to wait here until the system gets into a valid state. That sounds risky. What we really need to do is figure out how it got into the invalid state and handle that. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197354.1549278137000.13553.1562011380439%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins
Title: Message Title Jeff Thompson commented on JENKINS-55945 Re: Got IllegalStateException while restart Jenkins I'm taking a look at this to see if I can figure out what's going on. I haven't had any luck at reproducing it yet. There must be something about timing or configuration. There's probably something a little off about the Jenkins init sequence. If anyone could contribute additional logging, particularly showing init sequence progress, that might be helpful. It might be possible to catch the error here and do something, but without reproduction it's difficult to know if we'd be doing the right thing. Catching it and setting the security context to null would probably work. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197354.1549278137000.12000.1561753320468%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins
Title: Message Title Jeff Thompson assigned an issue to Jeff Thompson Jenkins / JENKINS-55945 Got IllegalStateException while restart Jenkins Change By: Jeff Thompson Assignee: Jeff Thompson 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197354.1549278137000.11876.1561743060477%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58018) High CPU load at slave with SSH-agent running freestyle project
Title: Message Title Jeff Thompson commented on JENKINS-58018 Re: High CPU load at slave with SSH-agent running freestyle project Hmmm ... So, it's not really a CPU load problem. sshd also shows heavy CPU load. That's good to know. That's a lot of data transfer. I didn't have anything like that with my jobs trying to duplicate the problem. My console output shows practically nothing. Do you get a large amount of stuff in your console output? A lot of times things that appear to be Remoting problems turn out to be caused by plugins. Sometimes it involves weird interactions between plugins. That could be what's going on here. Unfortunately, it can be complicated to isolate the problem and track it down. I don't have experience with the retainOrigin setting. Reading the code, it appears to reduce some of the resource consumption. However, if you're getting to the point where that makes a difference, there is probably something going on that is still keeping the consumption too high. Sometimes it's high server load. Network issues. Agent load. VM host issues or load. These links have some related info: JENKINS-49736, JENKINS-48810, and https://groups.google.com/forum/#!topic/jenkinsci-dev/zAkbD_NmnrM . Most of these point to resource issues. These can be really challenging to track down. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200038.1560499496000.11062.1561673580215%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53322) Remove patched dom4j from Stapler
Title: Message Title Jeff Thompson commented on JENKINS-53322 Re: Remove patched dom4j from Stapler PR in Stapler to change to standard dom4j: https://github.com/stapler/stapler/pull/164 Enablement PR in Jenkins to old or new to work fine: https://github.com/jenkinsci/jenkins/pull/4089 ec2-plugin PR to enable old or new to work fine: https://github.com/jenkinsci/ec2-plugin/pull/372 (Already merged) Additional PRs to come later to include the new versions. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193404.153555107.11040.1561669800262%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53322) Remove patched dom4j from Stapler
Title: Message Title Jeff Thompson commented on JENKINS-53322 Re: Remove patched dom4j from Stapler I've been working on this one for a while, compiling different libraries and plugins and running tests and checks. The specific tasks or conclusions I've found are a little different from those originally reported, but the overview remains the same. The forked dom4j version we use is ancient and really isn't necessary. We can get rid of it with a relatively few, independent tweaks. That will get us on a better footing. I'll start pushing a few PRs to various components to prepare them. Once we actually make the switch there are a few other places we can clean up. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193404.153555107.8946.1561500360184%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53322) Remove patched dom4j from Stapler
Title: Message Title Jeff Thompson assigned an issue to Jeff Thompson Jenkins / JENKINS-53322 Remove patched dom4j from Stapler Change By: Jeff Thompson Assignee: Jeff Thompson 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193404.153555107.7740.1561413660261%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57713) Cloud agent provisioning errors due to Remoting behaviour change
Title: Message Title Jeff Thompson updated JENKINS-57713 Removed the problematic change from Remoting in version 3.31. Jenkins / JENKINS-57713 Cloud agent provisioning errors due to Remoting behaviour change Change By: Jeff Thompson Status: In Progress Fixed but Unreleased Resolution: Fixed Released As: Remoting 3.33 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199655.1559046575000.4790.1561059600723%40
[JIRA] (JENKINS-57831) Remoting susceptible to race between HTTP availability and JNLP availability during master initialization
Title: Message Title Jeff Thompson closed an issue as Incomplete Jenkins / JENKINS-57831 Remoting susceptible to race between HTTP availability and JNLP availability during master initialization Change By: Jeff Thompson Status: Open Closed Resolution: Incomplete 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199788.1559625798000.4756.1561055280319%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57831) Remoting susceptible to race between HTTP availability and JNLP availability during master initialization
Title: Message Title Jeff Thompson commented on JENKINS-57831 Re: Remoting susceptible to race between HTTP availability and JNLP availability during master initialization Great. It looks like the possible value of making any changes at this time has declined. I'll go ahead and close this issue and the related PR. We'll see if another scenario comes up that could be the driver for some init sequence changes. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199788.1559625798000.4754.1561055220092%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57831) Remoting susceptible to race between HTTP availability and JNLP availability during master initialization
Title: Message Title Jeff Thompson commented on JENKINS-57831 Re: Remoting susceptible to race between HTTP availability and JNLP availability during master initialization Basil Crow, haven't you gotten any further in validating your needs are met by existing functionality? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199788.1559625798000.4734.1561050180173%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57959) Upgrade past args4j 2.32
Title: Message Title Jeff Thompson commented on JENKINS-57959 Re: Upgrade past args4j 2.32 The Remoting side of this change was released in version 3.33 of Remoting, where it upgraded to args4j version 2.33. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199940.1560260408000.4730.1561049160101%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50095) Remoting should check the "Remoting-Minimum-Version" header when connecting to the master
Title: Message Title Jeff Thompson updated JENKINS-50095 Released in Remoting 3.32. Not yet integrated into Jenkins. Jenkins / JENKINS-50095 Remoting should check the "Remoting-Minimum-Version" header when connecting to the master Change By: Jeff Thompson Status: In Review Fixed but Unreleased Resolution: Fixed Released As: Remoting 3.32 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189103.1520712598000.
[JIRA] (JENKINS-57959) Upgrade past args4j 2.32
Title: Message Title Jeff Thompson updated an issue Jenkins / JENKINS-57959 Upgrade past args4j 2.32 Change By: Jeff Thompson Comment: Remoting side is released in 3.32. Not yet included into master. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199940.1560260408000.4019.1560984420110%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57959) Upgrade past args4j 2.32
Title: Message Title Jeff Thompson resolved as Fixed Jenkins / JENKINS-57959 Upgrade past args4j 2.32 Change By: Jeff Thompson Status: In Progress Resolved Resolution: Fixed Released As: Remoting 3.32 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199940.1560260408000.4013.1560984360388%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57959) Upgrade past args4j 2.32
Title: Message Title Jeff Thompson commented on JENKINS-57959 Re: Upgrade past args4j 2.32 Remoting side is released in 3.32. Not yet included into master. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199940.1560260408000.4017.1560984360470%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57959) Upgrade past args4j 2.32
Title: Message Title Jeff Thompson reopened an issue Jenkins / JENKINS-57959 Upgrade past args4j 2.32 Change By: Jeff Thompson Resolution: Fixed Status: Resolved Reopened 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199940.1560260408000.4015.1560984360421%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58018) High CPU load at slave with SSH-agent running freestyle project
Title: Message Title Jeff Thompson commented on JENKINS-58018 Re: High CPU load at slave with SSH-agent running freestyle project I don't have your configuration, but I've tried a couple of different configurations to see if I can reproduce anything similar. No luck. Do you think the gmake and Makefile approach you use has any significance? I tried that on one of my configurations but I wouldn't think that would be meaningful. I'm not certain what your profiler session is showing (they can be difficult to read and this one appears to be cutoff or in a different layout than I've used before). It looks like it shows that the agent is spending quite a while blocked waiting to read, which is expected behavior. Especially if the job isn't doing anything, these threads will spend most of their time blocked waiting for input. That wouldn't cause high CPU load. You might see if you can catch the number of times the thread performs this operation, which could possibly affect CPU load. I've tried it with 2 cores and not seen any problems with CPU load. The only setup I currently have with 2 cores uses a different platform, but the code is the same. I'm sure lots of people run agents on machines with two cores. And the SSH-agent launcher is very popular. If it's a general problem we would expect to see more problem reports or others adding on here. We have seen, though, that VMs can be susceptible to weird problems, including odd load and I/O problems. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200038.1560499496000.4010.1560983940131%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
