[JIRA] (JENKINS-50412) Fingerprints logs should be less verbose
Title: Message Title Devin Nusbaum updated JENKINS-50412 Fixed in Jenkins 2.120. Jenkins / JENKINS-50412 Fingerprints logs should be less verbose Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13128) Artifacts Permissions Stripped
Title: Message Title Devin Nusbaum updated JENKINS-13128 Fixed in Jenkins 2.120. Jenkins / JENKINS-13128 Artifacts Permissions Stripped Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50412) Fingerprints logs should be less verbose
Title: Message Title Devin Nusbaum updated JENKINS-50412 Jenkins / JENKINS-50412 Fingerprints logs should be less verbose Change By: Devin Nusbaum Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51064) Lenient URL validator for Root URL
Title: Message Title Devin Nusbaum resolved as Fixed Fixed in version 2.120, but there is a followup ticket JENKINS-51158 to address some further problems. Jenkins / JENKINS-51064 Lenient URL validator for Root URL Change By: Devin Nusbaum Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options,
[JIRA] (JENKINS-51242) Jenkins doesn't take configured JDK
Title: Message Title Devin Nusbaum commented on JENKINS-51242 Re: Jenkins doesn't take configured JDK Softbless Solutions What kind of Jenkins job are you seeing this error with (e.g., a FreeStyle Project, a Pipeline, a Maven Project, etc.)? Can you post the full stack trace of the error? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51322) Update jackson2-api to jackson-databind 2.9+
Title: Message Title Devin Nusbaum commented on JENKINS-51322 Re: Update jackson2-api to jackson-databind 2.9+ I'd like to update the API plugin to 2.9.x, but want to do some testing to make sure there are no significant compatibility changes that will break plugins using the current API plugin and 2.8.x line, and I don't know when I will have time to do that. If you need 2.9.x urgently, you could shade the jackson dependencies in your plugin or copy them into your plugin sources using a different package name and then use that version in the plugin. (Not ideal, but it works) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51322) Update jackson2-api to jackson-databind 2.9+
Title: Message Title Devin Nusbaum commented on JENKINS-51322 Re: Update jackson2-api to jackson-databind 2.9+ If you are trying to use Jackson as part of a pipeline, you should not do that and instead create a standalone Java program that you call in a shell step in the pipeline, which can have whatever dependencies you want. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51483) Erroneous entry in split-plugin-cycles.txt for jdk-tool and apache-httpcomponents-client-4-api
Title: Message Title
Devin Nusbaum updated an issue
Jenkins / JENKINS-51483
Erroneous entry in split-plugin-cycles.txt for jdk-tool and apache-httpcomponents-client-4-api
Change By:
Devin Nusbaum
Problem: If apache-httpcomponents-client-4-api is tested with a core dependency of 2.112 or higher it will fail with ClassNotFoundException for hudson.tools.JDKInstaller.In JENKINS-22367 I detached {{JDKInstaller}} from core into the jdk-tool plugin. At one point the work-in-progress jdk-tool build depended on apache-httpcomponents-client-4-api so that JDKInstaller could be updated to use httpcomponents-client version 4 instead of version 3, so I added an [entry to split-plugins.txt|https://github.com/jenkinsci/jenkins/blob/9966c5d479a7ef35b6e4171cf5f351121d66b097/core/src/main/resources/jenkins/split-plugin-cycles.txt#L14] to break the cycle between these plugins. Later, I decided to wait to refactor the httpcomponents-client code until the plugin was detached, and removed the dependency on apache-httpcomponents-client-4-api, but did not remove the entry in split-plugin-cycles.txt.In practice, this means that apache-httpcomponents-client-4-api does not have an implied dependency on jdk-tool even though it should. This is not an issue in standard usage of the plugin, but apache-httpcomponents-client-4-api has a (broken) test that uses JDKInstaller: [Client4JDKInstallerTest|https://github.com/jenkinsci/apache-httpcomponents-client-4-api-plugin/blob/master/src/test/java/org/jenkinsci/plugins/apachehttpclient4api/Client4JDKInstallerTest.java].This issue was discovered by testing the plugin using the PCT with a new core version. We can fix it by removing the split-plugin-cycles.txt entry.
Add Comment
[JIRA] (JENKINS-51483) Erroneous entry in split-plugin-cycles.txt for jdk-tool and apache-httpcomponents-client-4-api
Title: Message Title Devin Nusbaum created an issue Jenkins / JENKINS-51483 Erroneous entry in split-plugin-cycles.txt for jdk-tool and apache-httpcomponents-client-4-api Issue Type: Bug Assignee: Devin Nusbaum Components: core Created: 2018-05-22 14:19 Priority: Minor Reporter: Devin Nusbaum Problem: If apache-httpcomponents-client-4-api is tested with a core dependency of 2.112 or higher it will fail with ClassNotFoundException for hudson.tools.JDKInstaller. In JENKINS-22367 I detached JDKInstaller from core into the jdk-tool plugin. At one point jdk-tool depended on apache-httpcomponents-client-4-api so that JDKInstaller could be updated to use httpcomponents-client version 4 instead of version 3, so I added an entry to split-plugins.txt to break the cycle between these plugins. Later, I decided to wait to refactor the httpcomponents-client code until the plugin was detached, and removed the dependency on apache-httpcomponents-client-4-api, but did not remove the entry in split-plugin-cycles.txt. In practice, this means that apache-httpcomponents-client-4-api does not have an implied dependency on jdk-tool even though it should. This is not an issue in standard usage of the plugin, but apache-httpcomponents-client-4-api has a (broken) test that uses JDKInstaller: Client4JDKInstallerTest. This issue was discovered by testing the plugin using the PCT with a new core version. We can fix it by removing the split-plugin-cycles.txt entry.
[JIRA] (JENKINS-51483) Erroneous entry in split-plugin-cycles.txt for jdk-tool and apache-httpcomponents-client-4-api
Title: Message Title Devin Nusbaum updated JENKINS-51483 Jenkins / JENKINS-51483 Erroneous entry in split-plugin-cycles.txt for jdk-tool and apache-httpcomponents-client-4-api Change By: Devin Nusbaum Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51483) Erroneous entry in split-plugin-cycles.txt for jdk-tool and apache-httpcomponents-client-4-api
Title: Message Title Devin Nusbaum started work on JENKINS-51483 Change By: Devin Nusbaum Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23697) IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)
Title: Message Title Devin Nusbaum commented on JENKINS-23697 Re: IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276) I recently saw this error on an instance where the credentials-binding plugin was masking a password that occurred naturally in the logs because it was a common word. The log had a ModelHyperlinkNote whose annotated text shrunk after the masking, which caused the stored length to no longer match the actual length, resulting in the IOOBE. I don't know if we could reorder the link creation in relation to the credentials masking to prevent that error, but the workaround of choosing a better password worked well enough in my case. Does anyone else getting this error see a lot of in the logs of the failing build? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51483) Erroneous entry in split-plugin-cycles.txt for jdk-tool and apache-httpcomponents-client-4-api
Title: Message Title
Devin Nusbaum updated an issue
Jenkins / JENKINS-51483
Erroneous entry in split-plugin-cycles.txt for jdk-tool and apache-httpcomponents-client-4-api
Change By:
Devin Nusbaum
Problem: If apache-httpcomponents-client-4-api is tested with a core dependency of 2.112 or higher it will fail with ClassNotFoundException for hudson.tools.JDKInstaller.In - JENKINS-22367 - I detached {{JDKInstaller}} from core into the jdk-tool plugin. At one point the work-in-progress jdk-tool build depended on apache-httpcomponents-client-4-api so that JDKInstaller could be updated to use httpcomponents-client version 4 instead of version 3, so I added an [entry to split-plugins.txt|https://github.com/jenkinsci/jenkins/blob/9966c5d479a7ef35b6e4171cf5f351121d66b097/core/src/main/resources/jenkins/split-plugin-cycles.txt#L14] to break the cycle between these plugins. Later, I decided to wait to refactor the httpcomponents-client code until the plugin was detached, and removed the dependency on apache-httpcomponents-client-4-api, but did not remove the entry in split-plugin-cycles.txt. EDIT: Adding that dependency would have required a circular dependency. I should never have tried to make jdk-tool depend on apache-httpcomponents-client-4-api with first changing apache-httpcomponents-client-4-api's tests that used JDKInstaller. In practice, this means that apache-httpcomponents-client-4-api does not have an implied dependency on jdk-tool even though it should. This is not an issue in standard usage of the plugin, but apache-httpcomponents-client-4-api has a (broken) test that uses JDKInstaller: [Client4JDKInstallerTest|https://github.com/jenkinsci/apache-httpcomponents-client-4-api-plugin/blob/master/src/test/java/org/jenkinsci/plugins/apachehttpclient4api/Client4JDKInstallerTest.java].This issue was discovered by testing the plugin using the PCT with a new core version. We can fix it by removing the split-plugin-cycles.txt entry.
Add Comment
[JIRA] (JENKINS-51158) Allow trailing dot in Root URL
Title: Message Title Devin Nusbaum updated JENKINS-51158 Released in Jenkins 2.124 (rerelease of 2.123). See the changelog. Jenkins / JENKINS-51158 Allow trailing dot in Root URL Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-51430) Systemd jenkins.service script does not protect spaces in JENKINS_JAVA_OPTIONS
Title: Message Title Devin Nusbaum commented on JENKINS-51430 Re: Systemd jenkins.service script does not protect spaces in JENKINS_JAVA_OPTIONS On IRC we discussed that the /usr/lib/jenkins/jenkins-run file appears to be coming from voxpupuli/puppet-jenkins, which is not part of the jenkinsci organization. You'll want to open an issue or file a PR on that repo directly. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51430) Systemd jenkins.service script does not protect spaces in JENKINS_JAVA_OPTIONS
Title: Message Title Devin Nusbaum edited a comment on JENKINS-51430 Re: Systemd jenkins.service script does not protect spaces in JENKINS_JAVA_OPTIONS On IRC we discussed that the /usr/lib/jenkins/jenkins-run file appears to be coming from [voxpupuli/puppet-jenkins|https://github.com/voxpupuli/puppet-jenkins/blob/master/templates/jenkins-run.erb], which is not part of the jenkinsci organization. You'll want to open an issue or file a PR on that repo directly.(EDIT: Did not see previous comment when this was made) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51049) Folders Plugin GitHub Scanning Time not being copied into the Jobs
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-51049
Re: Folders Plugin GitHub Scanning Time not being copied into the Jobs
Ok, it looks like your parent job is an organization folder and the sub jobs are multibranch projects. I am not familiar with the plugins and APIs that provide those features, but I see what appears to be related discussion in JENKINS-47077. In particular [~stephenconnolly] notes in a [comment|https://issues.jenkins-ci.org/browse/JENKINS-47077?focusedCommentId=331178=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-331178] something that makes me think this never worked.{quote}(ignore that you cannot configure the multibranch's period at present) {quote}Maybe the configuration of the folder properties has never worked, but you are only noticing it now that you are experiencing JENKINS-47077?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51049) Folders Plugin GitHub Scanning Time not being copied into the Jobs
Title: Message Title Devin Nusbaum commented on JENKINS-51049 Re: Folders Plugin GitHub Scanning Time not being copied into the Jobs Ok, it looks like your parent job is an organization folder and the sub jobs are multibranch projects. I am not familiar with the plugins and APIs that provide those features, but I see what appears to be related discussion in JENKINS-47077. In particular Stephen Connolly notes in a comment something that makes me think this never worked. (ignore that you cannot configure the multibranch's period at present) Maybe the configuration has never worked, but you are only noticing it now that you are experiencing JENKINS-47077? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51049) Folders Plugin GitHub Scanning Time not being copied into the Jobs
Title: Message Title Devin Nusbaum commented on JENKINS-51049 Re: Folders Plugin GitHub Scanning Time not being copied into the Jobs Thanks for reporting the issue. To help figure out where things are going wrong, could you attach the config.xml of the parent folder that you are having issues with? You can get it from the UI by navigating the folder and then adding config.xml to the URL. You'll want to make sure to remove any sensitive content (I only want to see the general structure). Also, since you marked this ticket as a regression, can you list the environment in which things were previously working? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22936) Move rename infrastructure from Job to AbstractItem
Title: Message Title Devin Nusbaum commented on JENKINS-22936 Re: Move rename infrastructure from Job to AbstractItem See PR 3289 for my proposal on how to fix this. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34712) "master is offline" preventing Pipeline from executing
Title: Message Title Devin Nusbaum assigned an issue to Devin Nusbaum Jenkins / JENKINS-34712 "master is offline" preventing Pipeline from executing Change By: Devin Nusbaum Assignee: Devin Nusbaum Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34712) "master is offline" preventing Pipeline from executing
Title: Message Title Devin Nusbaum started work on JENKINS-34712 Change By: Devin Nusbaum Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41182) Nodes disappear if "# of executors" is set to 0
Title: Message Title Devin Nusbaum edited a comment on JENKINS-41182 Re: Nodes disappear if "# of executors" is set to 0 After JENKINS-47793 ([PR 3141|https://github.com/jenkinsci/jenkins/pull/3141]), and the followup fix in [PR 3292|https://github.com/jenkinsci/jenkins/pull/3292], nodes are no longer able to be configured to have 0 executors, so I think this can be closed as resolved.The second PR was merged into 2.108 as [5c8cc45|https://github.com/jenkinsci/jenkins/commit/5c8cc45]. Screenshot Here is a screenshot of the error I get when attempting to configure a node with 0 executors : !Screen Shot 2018-02-20 at 11.15.35.png|thumbnail! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41182) Nodes disappear if "# of executors" is set to 0
Title: Message Title Devin Nusbaum commented on JENKINS-41182 Re: Nodes disappear if "# of executors" is set to 0 After JENKINS-47793 (PR 3141), and the followup fix in PR 3292, nodes are no longer able to be configured to have 0 executors, so I think this can be closed as resolved. The second PR was merged into 2.108 as 5c8cc45. Screenshot: Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41182) Nodes disappear if "# of executors" is set to 0
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-41182 Nodes disappear if "# of executors" is set to 0 Change By: Devin Nusbaum Attachment: Screen Shot 2018-02-20 at 11.15.35.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22936) Move rename infrastructure from Job to AbstractItem
Title: Message Title Devin Nusbaum updated JENKINS-22936 Jenkins / JENKINS-22936 Move rename infrastructure from Job to AbstractItem Change By: Devin Nusbaum Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49596) User session memory leak
Title: Message Title Devin Nusbaum commented on JENKINS-49596 Re: User session memory leak olamy Yes it is a JavaMelody class, here is the source code. I am not super familiar with JavaMelody, but it looks like it provides monitoring of various information, including http sessions, and allows http sessions to be invalidated manually. There is a JavaMelody Jenkins plugin with some details here. Thanks for preparing the winstone-4.1.x branch with so the fix can be backported! Is there anything I can do to help you get that branch released? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49596) User session memory leak
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-49596
Re: User session memory leak
[~olamy] Yes it is a JavaMelody class, [here|https://github.com/javamelody/javamelody/blob/master/javamelody-core/src/main/java/net/bull/javamelody/SessionListener.java] is the source code. I am not super familiar with JavaMelody, but it looks like it provides monitoring of various information, including http sessions, and allows http sessions to be invalidated manually. There is a JavaMelody Jenkins plugin with some details [here|https://wiki.jenkins.io/display/JENKINS/Monitoring].Thanks for preparing the {{winstone-4.1.x}} branch with so the fix can be backported! Is there anything I can do to help you get that branch released?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52847) durable-task plugin v1.23 misbehaves on BusyBox agents
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-52847 durable-task plugin v1.23 misbehaves on BusyBox agents Change By: Devin Nusbaum Labels: regression Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32510) SSHD relying on NativePRNG
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-32510
Re: SSHD relying on NativePRNG
SSHD's BouncyCastleRandom class only uses the SecureRandom instance to [generate an 8-byte seed|https://github.com/apache/mina-sshd/blob/83925cb70551c2b5e49f5044efa0d2e74d3180e4/sshd-core/src/main/java/org/apache/sshd/common/util/security/bouncycastle/BouncyCastleRandom.java#L44] using {{SecureRandom#generateSeed}} for a pure-Java PRNG from BouncyCastle, and the constructed BouncyCastleRandom instance is used as a singleton in SSHD, so that call should only block once. The most likely explanation is that it is using {{/dev/random}}, which is blocking occasionally when running tests.We could change the SecureRandom instance to use the NativePRNGNonBlocking provider, which will use {{/dev/urandom}} for engineGenerateSeed. Notably, it looks like SHA1PRNG's [generateSeed|http://hg.openjdk.java.net/jdk8u/jdk8u/jdk/file/dddb1b026323/src/share/classes/sun/security/provider/SecureRandom.java#l139] and [nextBytes|http://hg.openjdk.java.net/jdk8u/jdk8u/jdk/file/dddb1b026323/src/share/classes/sun/security/provider/SecureRandom.java#l214] methods use either {{/dev/random}} or {{/dev/urandom}} as their source based on the values of {{java.security.egd}} and {{securerandom.source}}, which we don't want to modify, so SHA1PRNG seems like a bad choice here. We could still use SHA1PRNG's engineNextBytes method, since the seed that it uses to initialize the state is [computed statically|http://hg.openjdk.java.net/jdk8u/jdk8u/jdk/file/dddb1b026323/src/share/classes/sun/security/provider/SecureRandom.java#l192], and so may already be ready by the time we want to use if if someone else initialized it . , but we can't guarantee that it won't block Since NativePRNGNonBlocking always uses {{/dev/urandom}}, and unlike in JENKINS-20108 we don't care about SHA1PRNG's increased throughput, I think switching to NativePRNGNonBlocking is the best option.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
[JIRA] (JENKINS-32510) SSHD relying on NativePRNG
Title: Message Title Devin Nusbaum assigned an issue to Devin Nusbaum Jenkins / JENKINS-32510 SSHD relying on NativePRNG Change By: Devin Nusbaum Assignee: Devin Nusbaum Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32510) SSHD relying on NativePRNG
Title: Message Title Devin Nusbaum commented on JENKINS-32510 Re: SSHD relying on NativePRNG SSHD's BouncyCastleRandom class only uses the SecureRandom instance to generate an 8-byte seed using SecureRandom#generateSeed for a pure-Java PRNG from BouncyCastle, and the constructed BouncyCastleRandom instance is used as a singleton in SSHD, so that call should only block once. The most likely explanation is that it is using /dev/random, which is blocking occasionally when running tests. We could change the SecureRandom instance to use the NativePRNGNonBlocking provider, which will use /dev/urandom for engineGenerateSeed. Notably, it looks like SHA1PRNG's generateSeed and nextBytes methods use either /dev/random or /dev/urandom as their source based on the values of java.security.egd and securerandom.source, which we don't want to modify, so SHA1PRNG seems like a bad choice here. We could still use SHA1PRNG's engineNextBytes method, since the seed that it uses to initialize the state is computed statically, and so may already be ready by the time we want to use if if someone else initialized it. Since NativePRNGNonBlocking always uses /dev/urandom, and unlike in JENKINS-20108 we don't care about SHA1PRNG's increased throughput, I think switching to NativePRNGNonBlocking is the best option. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52847) durable-task plugin v1.23 misbehaves on BusyBox agents
Title: Message Title Devin Nusbaum commented on JENKINS-52847 Re: durable-task plugin v1.23 misbehaves on BusyBox agents We could also make durable-task support more basic ps implementations with something like https://github.com/jenkinsci/durable-task-plugin/pull/77. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23697) IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)
Title: Message Title Devin Nusbaum commented on JENKINS-23697 Re: IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276) Another way I recent saw this issue was with a ModelHyperlinkNote where the model object's display name contained newlines. When the log was being annotated, only the text up to the first newline was considered, so the lengths did not match. I am going to file a change to ModelHyperlinkNote to replace newlines with spaces to prevent that class of errors. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52847) durable-task plugin v1.23 misbehaves on BusyBox agents
Title: Message Title Devin Nusbaum updated JENKINS-52847 This should be fixed in durable-task 1.24. Jenkins / JENKINS-52847 durable-task plugin v1.23 misbehaves on BusyBox agents Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Released As: durable-task 1.24 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34433) Pipeline locks not signalled on manual unreserving of resources
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-34433 Pipeline locks not signalled on manual unreserving of resources Change By: Devin Nusbaum Released As: lockable-resources 2.3 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41127) Multiple pipeline instances running concurrently when concurrent execution disabled
Title: Message Title Devin Nusbaum commented on JENKINS-41127 Re: Multiple pipeline instances running concurrently when concurrent execution disabled Fixed in Jenkins 2.136. I am marking this as an LTS candidate given the impact and simplicity of the fix, although we will have to give it some time to make sure there are no regressions. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30231) Build creates second workspace@2 for non-concurrent build configuration
Title: Message Title Devin Nusbaum commented on JENKINS-30231 Re: Build creates second workspace@2 for non-concurrent build configuration JENKINS-41127, which may have been the root cause of this issue, was just fixed in Jenkins 2.136. Does anyone have a test environment in which they can consistently reproduce this issue? If so, it would be great if you could test whether this problem still occurs in Jenkins 2.136 or newer. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41127) Multiple pipeline instances running concurrently when concurrent execution disabled
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-41127 Multiple pipeline instances running concurrently when concurrent execution disabled Change By: Devin Nusbaum Labels: concurrent lts-candidate Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53016) IndexOutOfBoundsException in MarkupText caused by (Model)HyperlinkNote
Title: Message Title Devin Nusbaum created an issue Jenkins / JENKINS-53016 IndexOutOfBoundsException in MarkupText caused by (Model)HyperlinkNote Issue Type: Bug Assignee: Devin Nusbaum Components: core Created: 2018-08-13 14:44 Priority: Minor Reporter: Devin Nusbaum Very similar to JENKINS-23697, but caused by creating a hyperlink note where the link text contains newline characters. When the note is encoded, the newlines count towards the length, but when the note is being read back via ConsoleAnnotationOutputStream, the data is split at each newline, so the length encoded in the note does not match what the stream sees, causing the IndexOutOfBoundsException. One way this could happen is if a build's display name is edited by a user to contain newlines, and then that build is passed to ModelHyperlinkNote#encodeTo. Here is an example stack trace of the problem: java.lang.IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276) at hudson.MarkupText.addMarkup(MarkupText.java:259) at hudson.console.HyperlinkNote.annotate(HyperlinkNote.java:69) at hudson.console.ConsoleAnnotationOutputStream$1.annotate(ConsoleAnnotationOutputStream.java:115) at hudson.console.ConsoleAnnotationOutputStream.eol(ConsoleAnnotationOutputStream.java:145) at hudson.console.LineTransformationOutputStream.eol(LineTransformationOutputStream.java:60) at hudson.console.LineTransformationOutputStream.write(LineTransformationOutputStream.java:56) at hudson.console.LineTransformationOutputStream.write(LineTransformationOutputStream.java:74)
[JIRA] (JENKINS-23697) IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)
Title: Message Title Devin Nusbaum edited a comment on JENKINS-23697 Re: IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276) Another way I recent saw this issue was with a ModelHyperlinkNote where the model object's display name contained newlines. When the log was being annotated, only the text up to the first newline was considered, so the lengths did not match. I am going to file a change to ModelHyperlinkNote to replace newlines with spaces to prevent that class of errors. EDIT: I opened JENKINS-53016 for that issue since it has nothing to do with Maven3MojoNote. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53016) IndexOutOfBoundsException in MarkupText caused by (Model)HyperlinkNote
Title: Message Title Devin Nusbaum started work on JENKINS-53016 Change By: Devin Nusbaum Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53016) IndexOutOfBoundsException in MarkupText caused by (Model)HyperlinkNote
Title: Message Title Devin Nusbaum updated JENKINS-53016 Jenkins / JENKINS-53016 IndexOutOfBoundsException in MarkupText caused by (Model)HyperlinkNote Change By: Devin Nusbaum Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53016) IndexOutOfBoundsException in MarkupText caused by (Model)HyperlinkNote
Title: Message Title
Devin Nusbaum updated an issue
Jenkins / JENKINS-53016
IndexOutOfBoundsException in MarkupText caused by (Model)HyperlinkNote
Change By:
Devin Nusbaum
Very similar to JENKINS-23697, but caused by creating a hyperlink note where the link text contains newline characters. When the note is encoded, the newlines count towards the length, but when the note is being read back via ConsoleAnnotationOutputStream, the data is split at each newline, so the length encoded in the note does not match what the stream sees, causing the IndexOutOfBoundsException.One way this could happen is if a build's display name is edited by a user to contain newlines, and then that build is passed to {{ModelHyperlinkNote#encodeTo}}. A workaround in that case would be to remove the newlines from the build's display name.Here is an example stack trace of the problem:{noformat}java.lang.IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276) at hudson.MarkupText.addMarkup(MarkupText.java:259) at hudson.console.HyperlinkNote.annotate(HyperlinkNote.java:69) at hudson.console.ConsoleAnnotationOutputStream$1.annotate(ConsoleAnnotationOutputStream.java:115) at hudson.console.ConsoleAnnotationOutputStream.eol(ConsoleAnnotationOutputStream.java:145) at hudson.console.LineTransformationOutputStream.eol(LineTransformationOutputStream.java:60) at hudson.console.LineTransformationOutputStream.write(LineTransformationOutputStream.java:56) at hudson.console.LineTransformationOutputStream.write(LineTransformationOutputStream.java:74) ... {noformat}
Add Comment
[JIRA] (JENKINS-53016) IndexOutOfBoundsException in MarkupText caused by (Model)HyperlinkNote
Title: Message Title
Devin Nusbaum updated an issue
Jenkins / JENKINS-53016
IndexOutOfBoundsException in MarkupText caused by (Model)HyperlinkNote
Change By:
Devin Nusbaum
Very similar to JENKINS-23697, but caused by creating a hyperlink note where the link text contains newline characters. When the note is encoded, the newlines count towards the length, but when the note is being read back via ConsoleAnnotationOutputStream, the data is split at each newline, so the length encoded in the note does not match what the stream sees, causing the IndexOutOfBoundsException.One way this could happen is if a build's display name is edited by a user to contain newlines, and then that build is passed to {{ModelHyperlinkNote#encodeTo}}. A workaround in that case would be to remove the newlines from the build's display name. Here is an example stack trace of the problem:{noformat}java.lang.IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276) at hudson.MarkupText.addMarkup(MarkupText.java:259) at hudson.console.HyperlinkNote.annotate(HyperlinkNote.java:69) at hudson.console.ConsoleAnnotationOutputStream$1.annotate(ConsoleAnnotationOutputStream.java:115) at hudson.console.ConsoleAnnotationOutputStream.eol(ConsoleAnnotationOutputStream.java:145) at hudson.console.LineTransformationOutputStream.eol(LineTransformationOutputStream.java:60) at hudson.console.LineTransformationOutputStream.write(LineTransformationOutputStream.java:56) at hudson.console.LineTransformationOutputStream.write(LineTransformationOutputStream.java:74){noformat}
Add Comment
[JIRA] (JENKINS-45575) Multiple assignment in pipeline fails with LHS Error
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-45575 Multiple assignment in pipeline fails with LHS Error Change By: Devin Nusbaum Released As: workflow-cps 2.46 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51928) Timeout is caught by the most internal try-catch, but should be caught by the try-catch that surrounds the timeout step
Title: Message Title Devin Nusbaum commented on JENKINS-51928 Re: Timeout is caught by the most internal try-catch, but should be caught by the try-catch that surrounds the timeout step This looks like the same class of problem as JENKINS-34973. It's unclear to me if we could do something out-of-band as Jesse suggests in that issue to change the behavior here. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52847) durable-task plugin v1.23 misbehaves on BusyBox agents
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-52847
Re: durable-task plugin v1.23 misbehaves on BusyBox agents
[~newms87] What OS/Shell are your build agents running? [~rpionke] [~newms87] Can you post the full logs of a build of a trivial pipeline Pipeline like the following?{noformat}node { sh ('''echo "Testing JENKINS-52847" && sleep 60''')}{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52847) durable-task plugin v1.23 misbehaves on BusyBox agents
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-52847
Re: durable-task plugin v1.23 misbehaves on BusyBox agents
[~newms87] What OS/Shell are your build agents running? [~rpionke] [~newms87] Can you post the full logs of a trivial pipeline like the following?{noformat}node { sh (' '' echo "Testing JENKINS-52847" && sleep 60' '' )}{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52847) durable-task plugin v1.23 misbehaves on BusyBox agents
Title: Message Title
Devin Nusbaum commented on JENKINS-52847
Re: durable-task plugin v1.23 misbehaves on BusyBox agents
Dan Newman What OS/Shell are your build agents running? Raphael Pionke Dan Newman Can you post the full logs of a trivial pipeline like the following?
node {
sh ('echo "Testing JENKINS-52847" && sleep 60')
}
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52881) durable-task plugin v1.23 kills jobs on Cygwin/MSys agents
Title: Message Title Devin Nusbaum updated JENKINS-52881 Should be fixed in durable-task 1.25. Jenkins / JENKINS-52881 durable-task plugin v1.23 kills jobs on Cygwin/MSys agents Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Released As: durable-task 1.25 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53134) Git checkout fails when using an SSH key with a passphrase
Title: Message Title Devin Nusbaum commented on JENKINS-53134 Re: Git checkout fails when using an SSH key with a passphrase Alex Taylor What is the error message you are seeing, and what credentials type are you using in Jenkins (username/password, ssh username w/ private key, etc.)? I was able to get things working on a Linux machine, and can try again on Windows shortly. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53134) Git checkout fails when using an SSH key with a passphrase
Title: Message Title Devin Nusbaum commented on JENKINS-53134 Re: Git checkout fails when using an SSH key with a passphrase Mark Waite Thanks for the pointer, I used https://github.com/jerrykuch/ersatz-setsid to run a JNLP agent on macOS using setsid and am no longer seeing errors on macOS using a credential of type 'SSH Username w/ Private Key' in Jenkins. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53134) Git checkout fails when using an SSH key with a passphrase
Title: Message Title Devin Nusbaum commented on JENKINS-53134 Re: Git checkout fails when using an SSH key with a passphrase Alex Taylor On my macOS master, it doesn't work for the reasons that Mark explained (the terminal is interactive, so it prompts for the key at the command line, which doesn't work). Once I used setsid and a local JNLP agent it worked fine. Are you getting a timeout, or a public key error? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53134) Git checkout fails when using an SSH key with a passphrase
Title: Message Title Devin Nusbaum commented on JENKINS-53134 Re: Git checkout fails when using an SSH key with a passphrase Alex Taylor There is no setsid shell command on macOS, so you have to compile https://github.com/jerrykuch/ersatz-setsid locally (make setsid), but once you do that I would expect that you could just run `/path/to/setsid java -jar jenkins.war` and then run a build on on the master. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53134) Git checkout fails when using an SSH key with a passphrase
Title: Message Title Devin Nusbaum commented on JENKINS-53134 Re: Git checkout fails when using an SSH key with a passphrase Alex Taylor There is no setsid shell command on macOS, so you have to compile https://github.com/jerrykuch/ersatz-setsid locally (make setsid), but once you do that I would expect that you could just run `/path/to/setsid java -jar jenkins.war` and then run a build on on the master. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49050) I can view my sequential declarative pipeline stages in the pipeline visualization plugin
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-49050 I can view my sequential declarative pipeline stages in the pipeline visualization plugin Change By: Devin Nusbaum Released As: Blue Ocean 1.8.0 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Devin Nusbaum edited a comment on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume [~johnar] Are you able to upload the build.xml for one of the stuck builds so that we can see all of its persisted state? (Please redact any sensitive information if you do upload it.) Also, can you please confirm what versions of the Pipeline Groovy Plugin and the Pipeline Job Plugin plugin you are using? Thanks! Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45571) "likely stuck" job is not actually stuck.
Title: Message Title Devin Nusbaum commented on JENKINS-45571 Re: "likely stuck" job is not actually stuck. Anna Tikhonova The fact that you are seeing the issue without restarting Jenkins is very interesting. Do you have a pipeline which is able to reproduce the problem consistently? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37589) Replay link does not show up if Jenkinsfile had a syntax error
Title: Message Title Devin Nusbaum commented on JENKINS-37589 Re: Replay link does not show up if Jenkinsfile had a syntax error It looks like the main script portion does not show up because ReplayAction#isReplayableSandboxTest returns false because loading the execution fails with the following: Aug 23, 2018 2:16:33 PM org.jenkinsci.plugins.workflow.cps.replay.ReplayAction getExecutionBlocking WARNING: Error fetching execution for replay java.io.IOException: Syntax #1 did not yet start at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.get(WorkflowRun.java:1125) at org.jenkinsci.plugins.workflow.cps.replay.ReplayAction.getExecutionBlocking(ReplayAction.java:126) at org.jenkinsci.plugins.workflow.cps.replay.ReplayAction.isReplayableSandboxTest(ReplayAction.java:166) ... the rest of the stack is not relevant (tested via script console) Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46642) Logs can grow without bound when using ansiColor plugin
Title: Message Title Devin Nusbaum closed an issue as Duplicate I spent some time today trying to reproduce this issue with the latest Pipeline plugins (notably durable-task 1.25 which has the JENKINS-37575 fix) and was unable to do so. For now I am closing as a duplicate of JENKINS-37575, but if anyone is able to reproduce with durable-task 1.23 or newer, feel free to reopen the issue. Jenkins / JENKINS-46642 Logs can grow without bound when using ansiColor plugin Change By: Devin Nusbaum Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37575) Delays in FileMonitoringTask.WriteLog can cause process output to be resent indefinitely
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-37575 Delays in FileMonitoringTask.WriteLog can cause process output to be resent indefinitely Change By: Devin Nusbaum Released As: durable-task 1.23 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41214) bitbucket branch source plugin notifies wrong repository
Title: Message Title Devin Nusbaum commented on JENKINS-41214 Re: bitbucket branch source plugin notifies wrong repository Is this a duplicate of JENKINS-41996? Is anyone still seeing the issue? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Devin Nusbaum commented on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume Sam Van Oort I have been looking at the issue. Like I commented here I don't think that case is actually a reproduction, because it does complete if you increase the timeout, although I might be misunderstanding the test case. I have been trying to find a way to reproduce the problem, but have been unsuccessful so far. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Devin Nusbaum commented on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume John Arnold Could you upload the whole build folder for one of the zombie builds? I'm most interested in the workflow directory adjacent to build.xml to see if the serialized flow nodes tell us anything interesting, but any exceptions/warnings in the various log files would be interesting as well. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title
Devin Nusbaum commented on JENKINS-50199
Re: Failed pipeline jobs stuck running after incorrect resume
Sam Van Oort Any thoughts on adding something like the following patch as a temporary fix in workflow-job to prevent these pipelines from resuming while we continue investigating?
diff --git a/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java b/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java
index 38e6ac1..70d9474 100644
--- a/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java
+++ b/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java
@@ -752,2 +752,8 @@ public final class WorkflowRun extends Run implements F
if (!completed == Boolean.TRUE) {
+if (execution.isComplete()) {
+LOGGER.log(Level.WARNING, "JENKINS-50199: Run completion inconsistent with execution, defaulting to failure for {0}", this);
+setResult(Result.FAILURE);
+completed = Boolean.TRUE;
+needsToPersist = true;
+} else {
// we've been restarted while we were running. let's get the execution going again.
@@ -757,2 +763,3 @@ public final class WorkflowRun extends Run implements F
Timer.get().submit(() -> Queue.getInstance().schedule(new AfterRestartTask(WorkflowRun.this), 0)); // JENKINS-31614
+}
}
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google
[JIRA] (JENKINS-52313) Storing binary file in shared library resources folder
Title: Message Title Devin Nusbaum updated JENKINS-52313 Support for Base64 encoding has been added to Pipeline: Shared Groovy Libraries 2.10 and Pipeline: Basic Steps 2.8.1 (or 2.10 if you are on Jenkins 2.121). Jenkins / JENKINS-52313 Storing binary file in shared library resources folder Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Released As: workflow-cps-global-lib 2.10, workflow-basic-steps 2.8.1, workflow-basic-steps 2.10 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-52313) Storing binary file in shared library resources folder
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-52313
Re: Storing binary file in shared library resources folder
[~quas] The problem is that {{UTF-8}} is a variable length encoding so any byte starting with a 1 whose highest bit is set will not round-trip correctly. You might be able to use a fixed-length encoding like {{Windows-1252}} in your most recent snippet to get things working, but {{libraryResource}} currently doesn't take an encoding parameter so you would have to change your system default to use that as a workaround. It seems better to explicitly support this use case.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38442) View sequential stages in the pipeline visualization graph
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-38442 View sequential stages in the pipeline visualization graph Change By: Devin Nusbaum Released As: Blue Ocean 1.8.0 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38442) View sequential stages in the pipeline visualization graph
Title: Message Title Devin Nusbaum closed an issue as Duplicate Blue Ocean 1.8.x adds support for visualizing sequential stages, so I am closing this as a dupe of JENKINS-49050. Jenkins / JENKINS-38442 View sequential stages in the pipeline visualization graph Change By: Devin Nusbaum Status: In Progress Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38442) View sequential stages in the pipeline visualization graph
Title: Message Title Devin Nusbaum edited a comment on JENKINS-38442 Re: View sequential stages in the pipeline visualization graph [Blue Ocean 1.8.x|https://plugins.jenkins.io/blueocean] adds support for visualizing sequential stages, so I am closing this as a dupe of JENKINS-49050 (although note that I believe that issue is specific to declarative pipeline) . Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38442) View sequential stages in the pipeline visualization graph
Title: Message Title Devin Nusbaum commented on JENKINS-38442 Re: View sequential stages in the pipeline visualization graph Joerg Schwaerzler I don't think there are any open feature requests specific to nested stages in scripted pipelines. We could reopen this issue and modify the title to be a little more specific, or we could open a new issue (probably better to have a more focused issue, assuming some of the people here are satisfied with the nested stage support for declarative in blue ocean 1.8), but I think either would be fine. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38442) View sequential stages in the pipeline visualization graph
Title: Message Title Devin Nusbaum commented on JENKINS-38442 Re: View sequential stages in the pipeline visualization graph Daniel Kurzynski Yes, this issue has multiple feature requests in the comments, so it seems to me like it would make more sense to open individual issues so each request can be discussed separately, but we could also just reopen this issue. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53262) Folder URL forward slashes are double encoded for Outlook notifications
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-53262
Re: Folder URL forward slashes are double encoded for Outlook notifications
I'm not sure why I am the default assignee here. It looks like [~outconn] is the maintainer of office-365-connector-plugin, so I am assigning it to him. It should be easy enough to check whether the bug is in that plugin or if the URL it gets from [ https://github.com/jenkinsci/blueocean-display-url-plugin ] has already been double-escaped in which case that plugin would need to be fixed. Also note: the problem is not 2 slashes (which would be {{%2f%2f}}), but that {{/}} was encoded twice: Once into {{%2f}}, and then the {{%}} was encoded again resulting in {{%252f}}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53262) Folder URL forward slashes are double encoded for Outlook notifications
Title: Message Title Devin Nusbaum assigned an issue to Out conn Jenkins / JENKINS-53262 Folder URL forward slashes are double encoded for Outlook notifications Change By: Devin Nusbaum Assignee: Devin Nusbaum Out conn Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53262) Folder URL forward slashes are double encoded for Outlook notifications
Title: Message Title Devin Nusbaum commented on JENKINS-53262 Re: Folder URL forward slashes are double encoded for Outlook notifications I'm not sure why I am the default assignee here. It looks like Out conn is the maintainer of office-365-connector-plugin, so I am assigning it to him. It should be easy enough to check whether the bug is in that plugin or if the URL it gets from https://github.com/jenkinsci/blueocean-display-url-plugin has already been double-escaped in which case that plugin would need to be fixed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Devin Nusbaum commented on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume John Arnold Are you able to upload the build.xml for one of the stuck builds so that we can see all of its persisted state? (Please redact any sensitive information if you do upload it.) Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53134) Git checkout fails when using an SSH key with a passphrase
Title: Message Title Devin Nusbaum commented on JENKINS-53134 Re: Git checkout fails when using an SSH key with a passphrase Alex Taylor What operating system(s) are you testing on? Are you sure this isn't just a quirk of your local ssh setup? For example, on macOS, by default it looks like the git plugin is trying to read my ssh passphrase from stdin, rather than using the credentials in Jenkins, but I think that is an macOS-specific quirk (and I have not yet found a way to make it work). Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49868) Disable tool installers entirely
Title: Message Title Devin Nusbaum commented on JENKINS-49868 Re: Disable tool installers entirely jdk-tool should anyway be amended to use anonymous OpenJDK downloads by default. CC Devin Nusbaum Yes, I think it would make sense to update https://github.com/jenkins-infra/crawler and jdk-tool to use anonymous downloads from http://jdk.java.net/archive/ for Java 9 and newer, and once Java 8 is officially EOL'd by Oracle (currently planned for January 2019) then I think we could totally remove the code that works with Oracle's website and requires an Oracle account to downloads old versions. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53016) IndexOutOfBoundsException in MarkupText caused by (Model)HyperlinkNote
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-53016 IndexOutOfBoundsException in MarkupText caused by (Model)HyperlinkNote Change By: Devin Nusbaum Released As: https://jenkins.io/changelog/#v2.139 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53016) IndexOutOfBoundsException in MarkupText caused by (Model)HyperlinkNote
Title: Message Title Devin Nusbaum updated JENKINS-53016 Fix released in Jenkins Core 2.139, see https://jenkins.io/changelog/#v2.139. Jenkins / JENKINS-53016 IndexOutOfBoundsException in MarkupText caused by (Model)HyperlinkNote Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45571) "likely stuck" job is not actually stuck.
Title: Message Title Devin Nusbaum commented on JENKINS-45571 Re: "likely stuck" job is not actually stuck. Anna Tikhonova Are you able upload the build directory of the build matching the stuck executor? Specifically, it would be helpful to see build.xml and the xml file(s) in the workflow directory. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45571) "likely stuck" job is not actually stuck.
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-45571
Re: "likely stuck" job is not actually stuck.
[~atikhonova] Are you able upload the build directory of the build matching the stuck executor? Specifically, it would be helpful to see \ {{build.xml}} and the xml file(s) in the \ {{workflow}} directory. EDIT: I see now that you can't easily tell which are stuck and which are good. If you can find an executor with {{likelyStuck: true}}, and whose build looks like it has otherwise completed or is suck, that would be a great candidate.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45571) "likely stuck" job is not actually stuck.
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-45571
Re: "likely stuck" job is not actually stuck.
[~atikhonova] Are you able upload the build directory of the build matching the stuck executor? Specifically, it would be helpful to see {{build.xml}} and the xml file(s) in the {{workflow}} directory. EDIT: I see now that you can't easily tell which are stuck and which are good. If you can find an executor with {{likelyStuck: true}}, and whose build looks like it has otherwise completed or is suck, that would be a great candidate. Another note: JENKINS-52165 will change the control flow here significantly.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Devin Nusbaum updated JENKINS-50199 Jenkins / JENKINS-50199 Failed pipeline jobs stuck running after incorrect resume Change By: Devin Nusbaum Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Devin Nusbaum started work on JENKINS-50199 Change By: Devin Nusbaum Status: Reopened In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53223) Finished pipeline jobs appear to occupy executor slots long after completion
Title: Message Title Devin Nusbaum commented on JENKINS-53223 Re: Finished pipeline jobs appear to occupy executor slots long after completion Maybe a dupe of JENKINS-45571 and/or JENKINS-51568? Thanks for including the thread dumps Elliot Babchick, I will take a look and see if anything gives us an idea of the cause. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53223) Finished pipeline jobs appear to occupy executor slots long after completion
Title: Message Title Devin Nusbaum assigned an issue to Devin Nusbaum Jenkins / JENKINS-53223 Finished pipeline jobs appear to occupy executor slots long after completion Change By: Devin Nusbaum Assignee: Devin Nusbaum Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Devin Nusbaum commented on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume Keith Ball There is often a slight time delay between when a new release is visible on the update center and when it is available on all mirrors, my guess is that was what happened for you. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Devin Nusbaum updated JENKINS-50199 I just released version 2.25 of the Pipeline Job plugin which should fix the issue where completed builds are resuming after restarting Jenkins. If anyone is still seeing the issue after upgrading the plugin, please comment with any additional information you can provide, such as the build folder of the build in question. Note that there are other issues that may appear similar but seem to have distinct causes. For anyone newly commenting on this issue, if you are seeing stuck executors without ever restarting Jenkins, please check if JENKINS-45571, JENKINS-53223, or JENKINS-51568 are closer to your situation and if so, comment there instead. Thanks! Jenkins / JENKINS-50199 Failed pipeline jobs stuck running after incorrect resume Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Released As: Pipeline Job 2.25 Add Comment This
[JIRA] (JENKINS-53223) Finished pipeline jobs appear to occupy executor slots long after completion
Title: Message Title Devin Nusbaum commented on JENKINS-53223 Re: Finished pipeline jobs appear to occupy executor slots long after completion I just took a quick look, and the thread dumps on the agent show that there is a thread pool on the agent waiting for a task to execute and there doesn't seem to be anything else of interest, so it seems that any problems here are likely on the master side. If you see the issue again, could you try to get thread dumps from the master instead? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51568) Pipeline jobs hanging in Build Executor even if it is finished
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-51568
Re: Pipeline jobs hanging in Build Executor even if it is finished
[~brainsam] I thought this might be a dupe of JENKINS-45571, but in your case it looks like the stuck executors are full Executors running on build agents rather than the flyweight executors that run on the master, so it seems like it might be something else.What versions of the Pipeline Groovy Plugin, Pipeline Job Plugin, Durable Task Plugin, and the Pipeline Nodes and Processes Plugin are you running? EDIT: Also, how is the {{Linux_default}} agent configured inside of Jenkins (i.e. SSH, EC2, JNLP, etc.)?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53223) Finished pipeline jobs appear to occupy executor slots long after completion
Title: Message Title Devin Nusbaum edited a comment on JENKINS-53223 Re: Finished pipeline jobs appear to occupy executor slots long after completion I just took a quick look, and the thread dumps on the agent show that there is a thread pool on the agent waiting for a task to execute and there doesn't seem to be anything else of interest, so it seems that any problems here are likely on the master side. If you see the issue again, could you try to get thread dumps from the master instead? EDIT: One other piece of info that would be helpful would be the build directory of one of the jobs that appears to be hanging, especially if you can obtain it both before and after it hangs. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53223) Finished pipeline jobs appear to occupy executor slots long after completion
Title: Message Title Devin Nusbaum commented on JENKINS-53223 Re: Finished pipeline jobs appear to occupy executor slots long after completion Sam Van Oort Still in my queue, have not had time to investigate. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53223) Finished pipeline jobs appear to occupy executor slots long after completion
Title: Message Title Devin Nusbaum edited a comment on JENKINS-53223 Re: Finished pipeline jobs appear to occupy executor slots long after completion I just took a quick look, and the thread dumps on the agent show that there is a thread pool on the agent waiting for a task to execute and there doesn't seem to be anything else of interest, so it seems that any problems here are likely on the master side. If you see the issue again, could you try to get thread dumps from the master instead? EDIT: One other piece of info that would be helpful would be the contents of the build directory of one of the builds that appears to be hanging, especially if you can obtain the directory both while the build is holding onto the executor and once it has released the executor. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53223) Finished pipeline jobs appear to occupy executor slots long after completion
Title: Message Title Devin Nusbaum edited a comment on JENKINS-53223 Re: Finished pipeline jobs appear to occupy executor slots long after completion I just took a quick look, and the thread dumps on the agent show that there is a thread pool on the agent waiting for a task to execute and there doesn't seem to be anything else of interest, so it seems that any problems here are likely on the master side. If you see the issue again, could you try to get thread dumps from the master instead? EDIT: One other piece of info that would be helpful would be the build directory of one of the jobs builds that appears to be hanging, especially if you can obtain it the directory both before while the build is holding onto the executor and after once it hangs has released the executor . Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53333) Provide a way to run pipeline steps with ambiguous step names
Title: Message Title
Devin Nusbaum updated JENKINS-5
This change was just released in workflow-cps 2.55. Steps can be invoked unambiguously as follows:
steps.'org.jenkinsci.plugins.workflow.steps.EchoStep'('Message')
'org.jenkinsci.plugins.workflow.steps.EchoStep'('Message')
// Both are equivalent to the following assuming `echo` is unambiguous
echo('Message')
Jenkins / JENKINS-5
Provide a way to run pipeline steps with ambiguous step names
Change By:
Devin Nusbaum
Status:
In Review Resolved
Resolution:
Fixed
Released As:
workflow-cps 2.55
Add Comment
This message was sent by Atlassian Jira
[JIRA] (JENKINS-53333) Provide a way to run pipeline steps with ambiguous step names
Title: Message Title
Devin Nusbaum created an issue
Jenkins / JENKINS-5
Provide a way to run pipeline steps with ambiguous step names
Issue Type:
Improvement
Assignee:
Devin Nusbaum
Components:
workflow-cps-plugin
Created:
2018-08-29 19:52
Priority:
Minor
Reporter:
Devin Nusbaum
Currently, if there are multiple Step}}s with the same function name in Jenkins (e.g. 3 plugins defining distinct Steps whose function names are all {{echo), any Jenkinsfiles that use echo will always use the first implementation (based on Extension ordering in Jenkins), and there is no way for the user to specify that they want to use a different implementation. Usually, it makes sense for the developers who created the steps to just rename them so they are distinct to prevent this problem entirely. Developers of new Pipeline steps are able to use the Step extension listing to browse all open source step implementations to ensure they are not reusing an existing step name, but there is no equivalent for proprietary plugins, so this could happen even if developers do their best to not use existing step names. To work around this issue, we should provide a way to execute a step unambiguously. For example:
echo "Hello, world!" // Normal echo step
'org.jenkinsci.plugins.workflow.steps.EchoStep'('Hello, world!') // Same as above, but refers to echo by the full class name
For now, this appears to be a very rare case, so it this basic workaround seems ok, but if it becomes more common maybe we could provide a more sophisticated way to bind step names as used in a Jenkinsfile to the desired Step implementations.
[JIRA] (JENKINS-53333) Provide a way to run pipeline steps with ambiguous step names
Title: Message Title
Devin Nusbaum updated an issue
Jenkins / JENKINS-5
Provide a way to run pipeline steps with ambiguous step names
Change By:
Devin Nusbaum
Currently, if there are multiple {{Step}}s Pipeline steps with the same function name in a Jenkins instance (e.g. 3 plugins defining distinct Steps whose function names are all {{echo}} are installed at the same time ), any Jenkinsfiles that use {{echo}} will always use the first implementation (based on Extension ordering in Jenkins of the step's descriptors ), and there is no way for the user to specify that they want to use a different implementation.Usually, it makes sense for the developers who created the steps to just rename them so they are distinct to prevent this problem entirely. Developers of new Pipeline steps are able to use the [Step extension listing|https://jenkins.io/doc/developer/extensions/workflow-step-api/#step] to browse all open source step implementations to ensure they are not reusing an existing step name, but there is no equivalent for proprietary plugins, so this could happen even if developers do their best to not use existing step names.To work around this issue, we should provide a way to execute a step unambiguously. For example:{code}echo "Hello, world!" // Normal echo step'org.jenkinsci.plugins.workflow.steps.EchoStep'('Hello, world!') // Same as above, but refers to echo by the full class name{code}For now, this appears to be a very rare case, so it this basic workaround seems ok, but if it becomes more common maybe we could provide a more sophisticated way to bind step names as used in a Jenkinsfile to the desired Step implementations.
Add Comment
[JIRA] (JENKINS-53333) Provide a way to run pipeline steps with ambiguous step names
Title: Message Title Devin Nusbaum updated JENKINS-5 Jenkins / JENKINS-5 Provide a way to run pipeline steps with ambiguous step names Change By: Devin Nusbaum Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
