[JIRA] [ec2-plugin] (JENKINS-35196) EC2-plugin not spooling up stopped nodes - job is in queue, node is offline
Title: Message Title Gleb Zverinskiy closed an issue as Not A Defect Jenkins / JENKINS-35196 EC2-plugin not spooling up stopped nodes - job is in queue, node is offline Change By: Gleb Zverinskiy Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [workflow-plugin] (JENKINS-34901) Continue parallel branch even if previous branch failed
Title: Message Title Ashudeep Budhiraja commented on JENKINS-34901 Re: Continue parallel branch even if previous branch failed Hi Sam, Thanks. Can you also describe a way to gracefully exit from the catch block. return doesn't work and System.exit(1) causes Jenkins to go dow. Regards, Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-35199) Scripts not permitted to use method java.lang.String isEmpty
Title: Message Title Ashudeep Budhiraja created an issue Jenkins / JENKINS-35199 Scripts not permitted to use method java.lang.String isEmpty Issue Type: Bug Assignee: vjuranek Components: groovy-plugin, pipeline-view-plugin, workflow-plugin Created: 2016/May/28 11:40 PM Priority: Major Reporter: Ashudeep Budhiraja Getting Exception: Scripts not permitted to use method java.lang.String isEmpty Also not getting under JENKINSURL/scriptApproval Add Comment
[JIRA] [warnings-plugin] (JENKINS-32191) workflow plugin does not provide console to warnings plugin, sleep required
Title: Message Title Ulli Hafner edited a comment on JENKINS-32191 Re: workflow plugin does not provide console to warnings plugin, sleep required Craid Craig , I just committed a test case with your build step. The test currently passes on my machine, lets see how it runs in https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness-stable/. Can you still reproduce it on your machine? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [warnings-plugin] (JENKINS-32191) workflow plugin does not provide console to warnings plugin, sleep required
Title: Message Title Ulli Hafner commented on JENKINS-32191 Re: workflow plugin does not provide console to warnings plugin, sleep required Craid, I just committed a test case with your build step. The test currently passes on my machine, lets see how it runs in https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness-stable/. Can you still reproduce it on your machine? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [warnings-plugin] (JENKINS-32191) workflow plugin does not provide console to warnings plugin, sleep required
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32191 Re: workflow plugin does not provide console to warnings plugin, sleep required Code changed in jenkins User: Ulli Hafner Path: src/test/java/plugins/WarningsPluginTest.java http://jenkins-ci.org/commit/acceptance-test-harness/d01a8c1546e1a4b2aac6dea692529da83e117bf3 Log: JENKINS-32191 Added testcase in order to try to expose the bug. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [blueocean-plugin] (JENKINS-35181) Docker image for Blue Ocean plugin
Title: Message Title Baptiste Mathus commented on JENKINS-35181 Re: Docker image for Blue Ocean plugin As discussed today on Twitter, I think that image should have pipeline plugins preinstalled and the upgrade wizard disabled, so that users can play with it all ready after pull. I've started working on it (though my network bandwidth is currently killing me). But should we also make it clear this is a demo image that shouldn't be used for prod use and so on? I think so. Users should be directed to the official image to build what they possibly need. Only possibly later would there ever be an official image ready for prod use with blueocean preinstalled and all. WDYT? James Dumay Michael Neale Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [git-client-plugin] (JENKINS-34309) git-client-plugin: StringIndexOutOfBoundsException when parsing branches
Title: Message Title Calvin Bascom commented on JENKINS-34309 Re: git-client-plugin: StringIndexOutOfBoundsException when parsing branches Just hit this as well, the DOS line ending in a commit message was the root cause for me as well. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [ant-plugin] (JENKINS-26056) Workflow build step for Ant
Title: Message Title Thomas Goeppel commented on JENKINS-26056 Re: Workflow build step for Ant I've used AntBuilder with the Groovy plugin, Of couse, that only works on the master, and one has to find the path of the workspace, and attach a logger. While coding build logic is really easy after that, the preparation is rather awkward, and it won't work in Jenkins Pipeline. Of course, one can also use Gradle's 'ant' object, but an AntBuilder step instead of "bat" on Windows would make many things much easier to read, and much simpler to maintain. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [github-oauth-plugin] (JENKINS-34896) Not retrieving teams
Title: Message Title Sam Gleske commented on JENKINS-34896 Re: Not retrieving teams There is a known issue where teams don't show up in the user details page for normal users (but they do for admins). However, the user still has those teams. I'm not sure where the root cause of that issue lies. It should not affect normal user authorization. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [github-oauth-plugin] (JENKINS-34775) Broken jobs after upgrade to 1.651.2 security update
Title: Message Title Sam Gleske commented on JENKINS-34775 Re: Broken jobs after upgrade to 1.651.2 security update Andrei Kovrov According to your screenshot it looks like you're in the plugin updates section of the configuration. Meaning you're running 0.22.2. i.e. you haven't upgraded yet. I also confirm that the casting exception occurs in line 644 of github-oauth-0.22.2. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-35198) DelegatingComputerLauncher allowing to use other DelegatingComputerLauncher as delegate
Title: Message Title Giuseppe Landolfi created an issue Jenkins / JENKINS-35198 DelegatingComputerLauncher allowing to use other DelegatingComputerLauncher as delegate Issue Type: Bug Assignee: Giuseppe Landolfi Components: core Created: 2016/May/28 4:48 PM Priority: Minor Reporter: Giuseppe Landolfi The utility base class DelegatingComputerLauncher comes with a descriptor implementation that advertises (primarily for the UI) which other launchers are accepted as delegated launchers. Specific code has been implemented for filtering out other DelegatingComputerLauncher instances from the possible delegate list in order to avoid multiple level ComputerLauncher recursions. The reported issue is that this filtering is not working, and the descriptor's "getApplicableDescriptors()" method returns also the descriptors of DelegatingComputerLauncher instances. Add Comment
[JIRA] [valgrind-plugin] (JENKINS-35156) valgrind plugin crashes
Title: Message Title Johannes Ohlemacher commented on JENKINS-35156 Re: valgrind plugin crashes I will look into it. Can you give details about your configuration and environment? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [git-plugin] (JENKINS-34165) Null pointer exception polling from git job to bitbucket repo
Title: Message Title Mark Waite commented on JENKINS-34165 Re: Null pointer exception polling from git job to bitbucket repo Meng Xin Zhu I wasn't able to see this stack trace with a job which was marked as "This build is parameterized" without defining a parameter. Can you describe the specific steps you took to see the problem. Steps I tried: Define a freestyle project Add Git as the SCM system with a valid private bitbucket repository (hosted on bitbucket.org, not publicly visible) Enable "Poll SCM" Poll the SCM Confirm that the git polling log does not contain a stack trace Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [build-timeout-plugin] (JENKINS-34846) Upgrade build-timeout-plugin to new parent pom
Title: Message Title ikedam commented on JENKINS-34846 Re: Upgrade build-timeout-plugin to new parent pom A few additional changes: https://github.com/jenkinsci/build-timeout-plugin/pull/55 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [git-plugin] (JENKINS-35105) Issue with git credentials InvalidObjectIdException
Title: Message Title Mark Waite resolved as Cannot Reproduce I'm closing this bug report because I cannot duplicate it. It contains insufficient information. If the original author provides more information, it can be reopened (if it can be duplicated). Things that I was able to guess from the stack trace (and which the submitter should have provided with the original submission, rather than just cutting and pasting a stack trace): Master is running on Windows, running git client plugin 1.19.6 (likely), and git plugin 2.4.4 (possibly). Command line git is the implementation used in this stack trace. User created a new job User entered the URL to the repository in the URL field of the job User probably did not enter any credentials for the repository (unclear, but hinted by code) When the user tabbed out of the field, the InvalidObjectIdException was thrown when the git plugin asked the git client plugin to report the most recent revision on the repository Some crucial questions that aren't answered by the stack trace include: Is command line git installed on the Windows machine? Are any other git commands working on the Windows machine? Is the Jenkins process on the Windows machine running as a service or as a user? What is the URL of the repository? Does the repository require credentials, and were they provided by the user? Where is the repository hosted (github, bitbucket, internal by user, etc.) and what version of the hosting software is being used? What other steps had the user taken when the problem appeared? Does the problem happen repeatedly on that Jenkins machine? Does the problem happen repeatedly on other Jenkins machines? Can the user clone the repository to that Jenkins machine from the command line?
[JIRA] [weblogic-deployer-plugin] (JENKINS-26992) WebLogic deployer does not expand variables
Title: Message Title Raphael CHAUMIER updated an issue Jenkins / JENKINS-26992 WebLogic deployer does not expand variables Change By: Raphael CHAUMIER Labels: weblogic-deployer-plugin-3.0 weblogic-deployer-plugin-3.3 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [weblogic-deployer-plugin] (JENKINS-26992) WebLogic deployer does not expand variables
Title: Message Title Raphael CHAUMIER updated an issue Jenkins / JENKINS-26992 WebLogic deployer does not expand variables Change By: Raphael CHAUMIER Labels: weblogic-deployer-plugin-3.0 weblogic-deployer-plugin-3.3 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [weblogic-deployer-plugin] (JENKINS-32392) Support ssl protocol like t3s or https for configuration
Title: Message Title Raphael CHAUMIER updated an issue Jenkins / JENKINS-32392 Support ssl protocol like t3s or https for configuration Change By: Raphael CHAUMIER Labels: weblogic-deployer-plugin-3. 3 5 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-35131) Clicking on Configure in the job crashes the application
Title: Message Title Sree Sankara commented on JENKINS-35131 Re: Clicking on Configure in the job crashes the application Mine was maven style jobs that got impacted Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-35131) Clicking on Configure in the job crashes the application
Title: Message Title Sree Sankara commented on JENKINS-35131 Re: Clicking on Configure in the job crashes the application Yes but that didn't help. I had to uninstall CVS plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [script-security-plugin] (JENKINS-33024) XmlSlurper.parseText() not whitelisted
Title: Message Title Flávio Augusto Valones commented on JENKINS-33024 Re: XmlSlurper.parseText() not whitelisted I use XmlSlurper.parseText() to read some information from pom.xml file, but in the sandbox I do not even have the option to approve it or not. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [blueocean-plugin] (JENKINS-35195) Unable to run Blue Ocean within tomcat
Title: Message Title
Adrian Fedoreanu edited a comment on JENKINS-35195
Re: Unable to run Blue Ocean within tomcat
It seems you're missing `blueocean-plugin.jpi`{code: bash none }root:~ jenkins$ find /usr/local/opt/jenkins/plugins/ -name "blue*.jpi"/usr/local/opt/jenkins/plugins/blueocean-commons.jpi/usr/local/opt/jenkins/plugins/blueocean-dashboard.jpi/usr/local/opt/jenkins/plugins/blueocean-plugin.jpi/usr/local/opt/jenkins/plugins/blueocean-rest.jpi/usr/local/opt/jenkins/plugins/blueocean-web.jpi{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [blueocean-plugin] (JENKINS-35195) Unable to run Blue Ocean within tomcat
Title: Message Title Adrian Fedoreanu commented on JENKINS-35195 Re: Unable to run Blue Ocean within tomcat It seems you're missing `blueocean-plugin.jpi` Unable to find source-code formatter for language: bash. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml root:~ jenkins$ find /usr/local/opt/jenkins/plugins/ -name "blue*.jpi" /usr/local/opt/jenkins/plugins/blueocean-commons.jpi /usr/local/opt/jenkins/plugins/blueocean-dashboard.jpi /usr/local/opt/jenkins/plugins/blueocean-plugin.jpi /usr/local/opt/jenkins/plugins/blueocean-rest.jpi /usr/local/opt/jenkins/plugins/blueocean-web.jpi Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-35129) After upgrade of 1.650 to 2.6 - unable to configure jobs
Title: Message Title Alex Carr commented on JENKINS-35129 Re: After upgrade of 1.650 to 2.6 - unable to configure jobs Yes, the Ant plugin is installed and activated. The downgrade and then upgrade of the Ant plugin resolved that problem (e.g. I no longer get an exception). The only reason I linked this issue to JENKINS-35122 is that it describes the problem that I am now dealing with. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [nested-view-plugin] (JENKINS-17524) NPE when renaming job in My Views
Title: Message Title Salman Awan resolved as Duplicate Jenkins / JENKINS-17524 NPE when renaming job in My Views Change By: Salman Awan Status: Open Resolved Assignee: Salman Awan Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [nested-view-plugin] (JENKINS-17524) NPE when renaming job in My Views
Title: Message Title Salman Awan commented on JENKINS-17524 Re: NPE when renaming job in My Views looks like a duplicate of JENKINS-17447 and unrelated to Nested View Plugin. Tried with Nested View Plugin v 1.14 with both jenkins 2.6 and 1.526, no exceptions. It is a minor one so we can resolve it as duplicate for now. Can be re-opened later. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [nested-view-plugin] (JENKINS-17524) NPE when renaming job in My Views
Title: Message Title Salman Awan assigned an issue to Unassigned Jenkins / JENKINS-17524 NPE when renaming job in My Views Change By: Salman Awan Assignee: Salman Awan Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [nested-view-plugin] (JENKINS-17524) NPE when renaming job in My Views
Title: Message Title Salman Awan assigned an issue to Salman Awan Jenkins / JENKINS-17524 NPE when renaming job in My Views Change By: Salman Awan Assignee: Salman Awan Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [maven-plugin] (JENKINS-34743) 2.2 Maven Installations - System Configuration Missing
Title: Message Title Chris Buechler commented on JENKINS-34743 Re: 2.2 Maven Installations - System Configuration Missing The section changed to Global Tool Configuration. That confused me as well initially. I submitted a pull request to update the link accordingly. https://github.com/jenkinsci/maven-plugin/pull/70 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-34438) Activate JSHint during the build process
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34438 Re: Activate JSHint during the build process Code changed in jenkins User: Manuel Recena Path: war/gulpfile.js war/package.json war/pom.xml http://jenkins-ci.org/commit/jenkins/2001154a3a9130b77cfb0334fcffb26935327ada Log: JENKINS-34438 - Activate JSHint through js-builder (#2367) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-35193) Cannot check connection status of the update site with ID='default'
Title: Message Title Oleg Nenashev commented on JENKINS-35193 Re: Cannot check connection status of the update site with ID='default' Thanks for the reply! Please let us know if you experience any other issues with update centers Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-25046) Cookie header too long, causing a 413 HTTP error
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-25046 Cookie header too long, causing a 413 HTTP error Change By: Daniel Beck Labels: 2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-25046) Cookie header too long, causing a 413 HTTP error
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-25046 Cookie header too long, causing a 413 HTTP error Nothing critical about this. It's both rare (only affecting those restarting Jenkins like crazy) and trivial to fix (remove the cookie). Change By: Daniel Beck Priority: Critical Minor Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-35193) Cannot check connection status of the update site with ID='default'
Title: Message Title Sergii Snig closed an issue as Fixed Jenkins / JENKINS-35193 Cannot check connection status of the update site with ID='default' Change By: Sergii Snig Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-35193) Cannot check connection status of the update site with ID='default'
Title: Message Title Sergii Snig resolved as Fixed Jenkins / JENKINS-35193 Cannot check connection status of the update site with ID='default' Change By: Sergii Snig Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-35193) Cannot check connection status of the update site with ID='default'
Title: Message Title Sergii Snig commented on JENKINS-35193 Re: Cannot check connection status of the update site with ID='default' Dear Oleg, Thank you, it pointed me on logs and I found the issue... By my commented details there is the link to config in ticket. company-default https://update-center.company.com/update-center.json default http://updates.jenkins-ci.org/stable/update-center.json it simply missed for in second line. that way the config /var/lib/jenkins/hudson.model.UpdateCenter.xml completely wrong It fixed and now ir works. Happy resolved Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-34751) StackOverflowError in Groovy scripts
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34751 Re: StackOverflowError in Groovy scripts Code changed in jenkins User: Daniel Spilker Path: core/pom.xml http://jenkins-ci.org/commit/jenkins/a3ddc89afe27a52554a79ff9e6d1b2ec714f96cd Log: JENKINS-34751 use patched version of Groovy 2.4.6 (#2369) contains fixes for GROOVY-7761 and GROOVY-7826 [FIXES JENKINS-34751] Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-33718) Release Jenkins Docker image along the normal release
Title: Message Title Oleg Nenashev commented on JENKINS-33718 Re: Release Jenkins Docker image along the normal release At least 2.6 is there Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-25046) Cookie header too long, causing a 413 HTTP error
Title: Message Title Oleg Nenashev commented on JENKINS-25046 Re: Cookie header too long, causing a 413 HTTP error Seems to be the issue, but I doubt it's 2.0-specific. CC Daniel Beck Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [git-plugin] (JENKINS-35105) Issue with git credentials InvalidObjectIdException
Title: Message Title Oleg Nenashev commented on JENKINS-35105 Re: Issue with git credentials InvalidObjectIdException Most likely it's about Git Plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [git-plugin] (JENKINS-35105) Issue with git credentials InvalidObjectIdException
Title: Message Title Oleg Nenashev assigned an issue to Mark Waite Jenkins / JENKINS-35105 Issue with git credentials InvalidObjectIdException Change By: Oleg Nenashev Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [git-plugin] (JENKINS-35105) Issue with git credentials InvalidObjectIdException
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-35105 Issue with git credentials InvalidObjectIdException Change By: Oleg Nenashev Component/s: git-plugin Component/s: core Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [other] (JENKINS-35094) unable to use grunt commands
Title: Message Title Oleg Nenashev commented on JENKINS-35094 Re: unable to use grunt commands 1) Is your Jenkins installed as a service? 2) If yes, does your windows service account has the same environment as your local user? (Most commonly "no") My guess is that your Windows service system environment does not define PATH and other vars required for grunt/bower. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [other] (JENKINS-35094) unable to use grunt commands
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-35094 unable to use grunt commands Change By: Oleg Nenashev Component/s: other Component/s: core Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [other] (JENKINS-35094) unable to use grunt commands
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-35094 unable to use grunt commands Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-35129) After upgrade of 1.650 to 2.6 - unable to configure jobs
Title: Message Title Oleg Nenashev commented on JENKINS-35129 Re: After upgrade of 1.650 to 2.6 - unable to configure jobs It's not related to JENKINS-35122 . Could you please check if you have the Ant plugin installed? Maybe it has not been activated on 2.6 due to the whatever reason Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-35160) Unable to delete project. File descriptor leak in build folder
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-35160 Unable to delete project. File descriptor leak in build folder Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-35160) Unable to delete project. File descriptor leak in build folder
Title: Message Title Oleg Nenashev commented on JENKINS-35160 Re: Unable to delete project. File descriptor leak in build folder It's a file descriptor leak somewhere in the build folder. Could you please create a dump of open file descriptors? E.g. it can be done via https://wiki.jenkins-ci.org/display/JENKINS/Support+Core+Plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-35160) Unable to delete project. File descriptor leak in build folder
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-35160 Unable to delete project. File descriptor leak in build folder Change By: Oleg Nenashev Summary: Unable to delete project . File descriptor leak in build folder Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-35167) Add ability to export XMLs with recursive job/folder configs
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-35167 Add ability to export XMLs with recursive job/folder configs Change By: Oleg Nenashev Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-35167) Add ability to export XMLs with recursive job/folder configs
Title: Message Title Oleg Nenashev commented on JENKINS-35167 Re: Add ability to export XMLs with recursive job/folder configs IMHO it's a new feature request, not a bug Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-35167) Add ability to export XMLs with recursive job/folder configs
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-35167 Add ability to export XMLs with recursive job/folder configs Change By: Oleg Nenashev Component/s: github-organization-folder-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-35167) Add ability to export XMLs with recursive job/folder configs
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-35167 Add ability to export XMLs with recursive job/folder configs Change By: Oleg Nenashev Summary: cc.xml does not include include jobs Add ability to export XMLs with recursive (folders) job/folder configs Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [cloudbees-folder-plugin] (JENKINS-35158) Searchbox must support Folders
Title: Message Title Oleg Nenashev commented on JENKINS-35158 Re: Searchbox must support Folders I confirm the functionality is still unsupported. Moreover, the extension engine for Search Factories is not designed well for such nested searches Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [workflow-multibranch-plugin] (JENKINS-35144) Disable Multibranch sub projects
Title: Message Title Oleg Nenashev commented on JENKINS-35144 Re: Disable Multibranch sub projects Since it's related to JENKINS-35143, I presume the issue is about Pipeline multibranch Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [workflow-multibranch-plugin] (JENKINS-35144) Disable Multibranch sub projects
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-35144 Disable Multibranch sub projects Change By: Oleg Nenashev Component/s: workflow-multibranch-plugin Component/s: core Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [workflow-multibranch-plugin] (JENKINS-35144) Disable Multibranch sub projects
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-35144 Disable Multibranch sub projects Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [workflow-multibranch-plugin] (JENKINS-35143) Delete Pipeline Multibranch sub projects
Title: Message Title Oleg Nenashev assigned an issue to Manuel Recena Soto Jenkins / JENKINS-35143 Delete Pipeline Multibranch sub projects Change By: Oleg Nenashev Assignee: Manuel Recena Soto Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [workflow-multibranch-plugin] (JENKINS-35144) Disable Multibranch sub projects
Title: Message Title Oleg Nenashev assigned an issue to Manuel Recena Soto Jenkins / JENKINS-35144 Disable Multibranch sub projects Change By: Oleg Nenashev Assignee: Oleg Nenashev Manuel Recena Soto Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [workflow-multibranch-plugin] (JENKINS-35144) Disable Pipeline Multibranch sub projects
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-35144 Disable Pipeline Multibranch sub projects Change By: Oleg Nenashev Summary: Disable Pipeline Multibranch sub projects Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [workflow-multibranch-plugin] (JENKINS-35143) Delete Pipeline Multibranch sub projects
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-35143 Delete Pipeline Multibranch sub projects Change By: Oleg Nenashev Component/s: workflow-multibranch-plugin Component/s: core Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [workflow-multibranch-plugin] (JENKINS-35143) Delete Pipeline Multibranch sub projects
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-35143 Delete Pipeline Multibranch sub projects Change By: Oleg Nenashev Summary: Delete Pipeline Multibranch sub projects Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-35143) Delete Multibranch sub projects
Title: Message Title Oleg Nenashev commented on JENKINS-35143 Re: Delete Multibranch sub projects It's not related to the core Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-35131) Clicking on Configure in the job crashes the application
Title: Message Title Oleg Nenashev commented on JENKINS-35131 Re: Clicking on Configure in the job crashes the application Do you have the Gradle plugin installed? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-35184) Failed to load jenkins.util.SystemProperties on slaves due to ServletContext
Title: Message Title Oleg Nenashev started work on JENKINS-35184 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-35193) Cannot check connection status of the update site with ID='default'
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-35193 Cannot check connection status of the update site with ID='default' Change By: Oleg Nenashev Component/s: core Component/s: _unsorted Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-35193) Cannot check connection status of the update site with ID='default'
Title: Message Title Oleg Nenashev commented on JENKINS-35193 Re: Cannot check connection status of the update site with ID='default' Sergii Snig Is it an offline installation? Which update site do you use as a default one? E.g. which one was configured in Manage Jenkins/Plugin Manager/Advanced/Update Site? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [cli] (JENKINS-35197) unable to use jenkins-cli: java.io.StreamCorruptedException
Title: Message Title
Atul Patel updated an issue
Jenkins / JENKINS-35197
unable to use jenkins-cli: java.io.StreamCorruptedException
Change By:
Atul Patel
using a brand new install on a new serverexecuted {{java -jar /opt/jenkins-cli.jar -s http://localhost:8080 help{}}Got the following stack trace:SEVERE: I/O error in channel Chunked connection to http://localhost:8080/clijava.io.StreamCorruptedException: invalid stream header: 0A0A0A0A at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:807) at java.io.ObjectInputStream.(ObjectInputStream.java:302) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)hudson.remoting.RequestAbortedException: java.io.StreamCorruptedException: invalid stream header: 0A0A0A0A at hudson.remoting.Request.abort(Request.java:303) at hudson.remoting.Channel.terminate(Channel.java:847) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) at ..remote call to Chunked connection to http://localhost:8080/cli(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416) at hudson.remoting.Request.call(Request.java:172) at hudson.remoting.Channel.call(Channel.java:780) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:249) at hudson.remoting.$Proxy1.waitForProperty(Unknown Source) at hudson.remoting.Channel.waitForRemoteProperty(Channel.java:1258) at hudson.cli.CLI.(CLI.java:141) at hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:72) at hudson.cli.CLI._main(CLI.java:473) at hudson.cli.CLI.main(CLI.java:384)Caused by: java.io.StreamCorruptedException: invalid stream header: 0A0A0A0A at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:807) at java.io.ObjectInputStream.(ObjectInputStream.java:302) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)Found an old issue that suggested making the following change that worked for me. Not sure if this is a bug or a configuration issue, but thought it would be helpful to anyone else who runs into this problem. I tried the follow solution that worked: edited edit /etc/default/jenkins and changed JAVA_ARGS="-Djava.awt.headless=true"toJAVA_ARGS="-Djava.awt.headless=true -Dhudson.diyChunking=false" and then restarted jenkins (sudo service jenkins restart) PS. Love jenkins. thank you!
[JIRA] [cli] (JENKINS-35197) unable to use jenkins-cli: java.io.StreamCorruptedException
Title: Message Title
Atul Patel updated an issue
Jenkins / JENKINS-35197
unable to use jenkins-cli: java.io.StreamCorruptedException
Change By:
Atul Patel
using a brand new install on a new serverexecuted {{java -jar /opt/jenkins-cli.jar -s http://localhost:8080 help{}}Got the following stack trace:SEVERE: I/O error in channel Chunked connection to http://localhost:8080/clijava.io.StreamCorruptedException: invalid stream header: 0A0A0A0A at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:807) at java.io.ObjectInputStream.(ObjectInputStream.java:302) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)hudson.remoting.RequestAbortedException: java.io.StreamCorruptedException: invalid stream header: 0A0A0A0A at hudson.remoting.Request.abort(Request.java:303) at hudson.remoting.Channel.terminate(Channel.java:847) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) at ..remote call to Chunked connection to http://localhost:8080/cli(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416) at hudson.remoting.Request.call(Request.java:172) at hudson.remoting.Channel.call(Channel.java:780) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:249) at hudson.remoting.$Proxy1.waitForProperty(Unknown Source) at hudson.remoting.Channel.waitForRemoteProperty(Channel.java:1258) at hudson.cli.CLI.(CLI.java:141) at hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:72) at hudson.cli.CLI._main(CLI.java:473) at hudson.cli.CLI.main(CLI.java:384)Caused by: java.io.StreamCorruptedException: invalid stream header: 0A0A0A0A at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:807) at java.io.ObjectInputStream.(ObjectInputStream.java:302) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)Found an old issue that suggested making the following change that worked for me. Not sure if this is a bug or a configuration issue, but thought it would be helpful to anyone else who runs into this problem. I tried the follow solution that worked:edited /etc/default/jenkins and changed {{ JAVA_ARGS="-Djava.awt.headless=true" }} to {{ JAVA_ARGS="-Djava.awt.headless=true -Dhudson.diyChunking=false" }} PS. Love jenkins. thank you!
[JIRA] [cli] (JENKINS-35197) unable to use jenkins-cli: java.io.StreamCorruptedException
Title: Message Title
Atul Patel updated an issue
Jenkins / JENKINS-35197
unable to use jenkins-cli: java.io.StreamCorruptedException
Change By:
Atul Patel
using a brand new install on a new serverexecuted {{java -jar /opt/jenkins-cli.jar -s http://localhost:8080 help{}}Got the following stack trace:SEVERE: I/O error in channel Chunked connection to http://localhost:8080/clijava.io.StreamCorruptedException: invalid stream header: 0A0A0A0A at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:807) at java.io.ObjectInputStream.(ObjectInputStream.java:302) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)hudson.remoting.RequestAbortedException: java.io.StreamCorruptedException: invalid stream header: 0A0A0A0A at hudson.remoting.Request.abort(Request.java:303) at hudson.remoting.Channel.terminate(Channel.java:847) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) at ..remote call to Chunked connection to http://localhost:8080/cli(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416) at hudson.remoting.Request.call(Request.java:172) at hudson.remoting.Channel.call(Channel.java:780) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:249) at hudson.remoting.$Proxy1.waitForProperty(Unknown Source) at hudson.remoting.Channel.waitForRemoteProperty(Channel.java:1258) at hudson.cli.CLI.(CLI.java:141) at hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:72) at hudson.cli.CLI._main(CLI.java:473) at hudson.cli.CLI.main(CLI.java:384)Caused by: java.io.StreamCorruptedException: invalid stream header: 0A0A0A0A at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:807) at java.io.ObjectInputStream.(ObjectInputStream.java:302) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)Found an old issue that suggested making the following change that worked for me. Not sure if this is a bug or a configuration issue, but thought it would be helpful to anyone else who runs into this problem. I tried the follow solution that worked:edited /etc/default/jenkins and changed {{JAVA_ARGS="-Djava.awt.headless=true" }} to{{JAVA_ARGS="-Djava.awt.headless=true -Dhudson.diyChunking=false" }}PS. Love jenkins. thank you!
[JIRA] [cli] (JENKINS-35197) unable to use jenkins-cli: java.io.StreamCorruptedException
Title: Message Title
Atul Patel updated an issue
Jenkins / JENKINS-35197
unable to use jenkins-cli: java.io.StreamCorruptedException
Change By:
Atul Patel
using a brand new install on a new serverexecuted {{java -jar /opt/jenkins-cli.jar -s http://localhost:8080 help{}}Got the following stack trace:SEVERE: I/O error in channel Chunked connection to http://localhost:8080/clijava.io.StreamCorruptedException: invalid stream header: 0A0A0A0A at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:807) at java.io.ObjectInputStream.(ObjectInputStream.java:302) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)hudson.remoting.RequestAbortedException: java.io.StreamCorruptedException: invalid stream header: 0A0A0A0A at hudson.remoting.Request.abort(Request.java:303) at hudson.remoting.Channel.terminate(Channel.java:847) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) at ..remote call to Chunked connection to http://localhost:8080/cli(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416) at hudson.remoting.Request.call(Request.java:172) at hudson.remoting.Channel.call(Channel.java:780) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:249) at hudson.remoting.$Proxy1.waitForProperty(Unknown Source) at hudson.remoting.Channel.waitForRemoteProperty(Channel.java:1258) at hudson.cli.CLI.(CLI.java:141) at hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:72) at hudson.cli.CLI._main(CLI.java:473) at hudson.cli.CLI.main(CLI.java:384)Caused by: java.io.StreamCorruptedException: invalid stream header: 0A0A0A0A at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:807) at java.io.ObjectInputStream.(ObjectInputStream.java:302) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)Found an old issue that suggested making the following change that worked for me. Not sure if this is a bug or a configuration issue, but thought it would be helpful to anyone else who runs into this problem. I tried the follow solution that worked:edited /etc/default/jenkins and changed * {{ JAVA_ARGS="-Djava.awt.headless=true" * }} to * {{ JAVA_ARGS="-Djava.awt.headless=true -Dhudson.diyChunking=false" * }} PS. Love jenkins. thank you!
[JIRA] [cli] (JENKINS-35197) unable to use jenkins-cli: java.io.StreamCorruptedException
Title: Message Title
Atul Patel updated an issue
Jenkins / JENKINS-35197
unable to use jenkins-cli: java.io.StreamCorruptedException
Change By:
Atul Patel
using a brand new install on a new serverexecuted {{java -jar /opt/jenkins-cli.jar -s http://localhost:8080 help{}}Got the following stack trace:SEVERE: I/O error in channel Chunked connection to http://localhost:8080/clijava.io.StreamCorruptedException: invalid stream header: 0A0A0A0A at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:807) at java.io.ObjectInputStream.(ObjectInputStream.java:302) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)hudson.remoting.RequestAbortedException: java.io.StreamCorruptedException: invalid stream header: 0A0A0A0A at hudson.remoting.Request.abort(Request.java:303) at hudson.remoting.Channel.terminate(Channel.java:847) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) at ..remote call to Chunked connection to http://localhost:8080/cli(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416) at hudson.remoting.Request.call(Request.java:172) at hudson.remoting.Channel.call(Channel.java:780) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:249) at hudson.remoting.$Proxy1.waitForProperty(Unknown Source) at hudson.remoting.Channel.waitForRemoteProperty(Channel.java:1258) at hudson.cli.CLI.(CLI.java:141) at hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:72) at hudson.cli.CLI._main(CLI.java:473) at hudson.cli.CLI.main(CLI.java:384)Caused by: java.io.StreamCorruptedException: invalid stream header: 0A0A0A0A at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:807) at java.io.ObjectInputStream.(ObjectInputStream.java:302) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)Found an old issue that suggested making the following change that worked for me. Not sure if this is a bug or a configuration issue, but thought it would be helpful to anyone else who runs into this problem. I tried the follow solution that worked:edited /etc/default/jenkins and changed * JAVA_ARGS="-Djava.awt.headless=true" * to * JAVA_ARGS="-Djava.awt.headless=true -Dhudson.diyChunking=false" * PS. Love jenkins. thank you!
[JIRA] [cli] (JENKINS-35197) unable to use jenkins-cli: java.io.StreamCorruptedException
Title: Message Title
Atul Patel created an issue
Jenkins / JENKINS-35197
unable to use jenkins-cli: java.io.StreamCorruptedException
Issue Type:
Bug
Assignee:
Unassigned
Components:
cli
Created:
2016/May/28 6:33 AM
Environment:
debian/jessie Jenkins 2.06
Labels:
2.0 cli
Priority:
Minor
Reporter:
Atul Patel
using a brand new install on a new server executed java -jar /opt/jenkins-cli.jar -s http://localhost:8080 help{
Got the following stack trace: SEVERE: I/O error in channel Chunked connection to http://localhost:8080/cli java.io.StreamCorruptedException: invalid stream header: 0A0A0A0A at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:807) at java.io.ObjectInputStream.(ObjectInputStream.java:302) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at
[JIRA] [nodejs-plugin] (JENKINS-19227) NodeJS plugin not showing in configuration
Title: Message Title Eslam ElHusseiny closed an issue as Not A Defect Jenkins / JENKINS-19227 NodeJS plugin not showing in configuration Change By: Eslam ElHusseiny Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [nodejs-plugin] (JENKINS-19227) NodeJS plugin not showing in configuration
Title: Message Title Eslam ElHusseiny commented on JENKINS-19227 Re: NodeJS plugin not showing in configuration I confirm too that NodeJs view has been moved to Jenkins-> Global Tool Configuration. Thanks Bill Warner for the clarity. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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.
