[JIRA] [core] (JENKINS-32371) Excessive wait times to clear build/node assocation after job completes

[mmit...@microsoft.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew Mitchell commented on  JENKINS-32371 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Excessive wait times to clear build/node assocation after job completes  
 
 
 
 
 
 
 
 
 
 
This seems to have mostly been resolved, though i still see it occasionally under heavy load, even when a GC is not happening. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32818) Jenkins stops responding to web HTTP requests

[mmit...@microsoft.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew Mitchell created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32818 
 
 
 
  Jenkins stops responding to web HTTP requests  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 jenkins-hang.txt 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 05/Feb/16 10:18 PM 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Matthew Mitchell 
 
 
 
 
 
 
 
 
 
 
Seen twice now, Jenkins stops responding to web HTTP requests. Oddly enough,the pull request builder and build build nodes still appear to be doing thing in the background, Github gets status updates, etc. However the webiste cannot be accessed. See stack trace. 
GC does not appear to be an issue. Only using about 40% of available heap space not over the max perm gen. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 

[JIRA] [build-pipeline-plugin] (JENKINS-14591) Add the ability to choose which parameters build will be displayed

[alv...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Alvizu commented on  JENKINS-14591 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add the ability to choose which parameters build will be displayed  
 
 
 
 
 
 
 
 
 
 
PR:  
https://github.com/jenkinsci/build-pipeline-plugin/pull/96 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-pipeline-plugin] (JENKINS-14591) Add the ability to choose which parameters build will be displayed

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-14591 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add the ability to choose which parameters build will be displayed  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Dan Alvizu Path: pom.xml src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildForm.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/PipelineBuild.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/AbstractNameValueHeader.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/BuildVariablesHeader.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/NullColumnHeader.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/ParametersActionHeader.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/PipelineHeaderExtension.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/SimpleColumnHeader.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/SimpleRowHeader.java src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView/bpp.jelly src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView/configure-entries.jelly src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView/help-headerBoxParameterProvider.html src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView/help-revisionBoxParameterProvider.html src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView/help-showPipelineParameters.html src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView/help-showPipelineParametersInHeaders.html src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/DownstreamProjectGridBuilder/config.jelly src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/AbstractNameValueHeader/projectCardTemplate.jelly src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/AbstractNameValueHeader/rowHeader.jelly src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/BuildVariablesHeader/config.jelly src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/NullColumnHeader/columnHeader.jelly src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/NullColumnHeader/config.jelly src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/NullColumnHeader/projectCardTemplate.jelly src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/ParametersActionHeader/config.jelly src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/PipelineHeaderExtension/columnHeader.jelly src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/SimpleColumnHeader/config.jelly src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/SimpleColumnHeader/projectCardTemplate.jelly src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/SimpleRowHeader/config.jelly src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/SimpleRowHeader/rowHeader.jelly src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineViewConstructorTest.java src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineViewTest.java src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/BuildVariablesHeaderTest.java src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/NullColumnHeaderTest.java src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/ParametersActionHeaderTest.java src/test/java/au/com/centrumsyst

[JIRA] [stashnotifier-plugin] (JENKINS-32817) stashnotifier-plugin credentials are broken

[phil.john...@infinitecampus.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Phillips commented on  JENKINS-32817 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: stashnotifier-plugin credentials are broken  
 
 
 
 
 
 
 
 
 
 
Should I be documenting this on the plugin page instead?  https://github.com/jenkinsci/stashnotifier-plugin/issues 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [vmware-vrealize-automation-plugin] (JENKINS-32810) Return environment environment name

[kris.thie...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kris Thieler started work on  JENKINS-32810 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Kris Thieler 
 
 
 

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] [vmware-vrealize-automation-plugin] (JENKINS-32810) Return environment environment name

[kris.thie...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kris Thieler updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32810 
 
 
 
  Return environment environment name  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kris Thieler 
 
 
 

Labels:
 
 1.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [vmware-vrealize-automation-plugin] (JENKINS-32261) Exclude bcprov dependencies

[kris.thie...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kris Thieler updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32261 
 
 
 
  Exclude bcprov dependencies  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kris Thieler 
 
 
 

Labels:
 
 1.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [stashnotifier-plugin] (JENKINS-32817) stashnotifier-plugin credentials are broken

[phil.john...@infinitecampus.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Phillips created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32817 
 
 
 
  stashnotifier-plugin credentials are broken  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 Issue.png 
 
 
 

Components:
 

 stashnotifier-plugin 
 
 
 

Created:
 

 05/Feb/16 9:54 PM 
 
 
 

Environment:
 

 Windows, Java7 or Java8 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 John Phillips 
 
 
 
 
 
 
 
 
 
 
With basic system credential information set in Jenkins the stashnotifier-plugin does not allow me to select or create a new credential in the "Credentials" section.  
 
 
 
 
 
 
 
 
 
 
 
 

   

[JIRA] [vmware-vrealize-automation-plugin] (JENKINS-32816) Blueprint as code

[kris.thie...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kris Thieler created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32816 
 
 
 
  Blueprint as code  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Kris Thieler 
 
 
 

Components:
 

 vmware-vrealize-automation-plugin 
 
 
 

Created:
 

 05/Feb/16 9:52 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Kris Thieler 
 
 
 
 
 
 
 
 
 
 
The Jenkins plugin should be able to import a blueprint into vRA. The blueprint will be stored in a source repository like GIT and referenced by relative path to the project, similar to other files with Jenkins. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

  

[JIRA] [managed-scripts-plugin] (JENKINS-32815) managed shell scripts should call trim() on shebang path

[jenk...@duigou.org (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mike Duigou created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32815 
 
 
 
  managed shell scripts should call trim() on shebang path  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Dominik Bartholdi 
 
 
 

Components:
 

 managed-scripts-plugin 
 
 
 

Created:
 

 05/Feb/16 9:48 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Mike Duigou 
 
 
 
 
 
 
 
 
 
 
The shebang "#! /bin/bash -eux" currently fails because there is a space between the shebang and the path. Spaces are permitted per: https://en.wikipedia.org/wiki/Shebang_%28Unix%29#Magic_number  
This is common enough that the plugin should support it. Please call trim() on the path or remove initial whitespace 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 

[JIRA] [p4-plugin] (JENKINS-32814) Add "Only poll using master" option

[p...@adobe.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jim Poje created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32814 
 
 
 
  Add "Only poll using master" option  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 p4-plugin 
 
 
 

Created:
 

 05/Feb/16 9:44 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Jim Poje 
 
 
 
 
 
 
 
 
 
 
Request the ability to force SCM polling on the master. It is presently delegated to slaves, and these require a workspace to poll, which implicitly causes a build to occur if the workspace does not exist. In environments where the slaves are short lived, this causes many extra builds. 
This is identical to 

JENKINS-9067
 which was for the older predecessor perforce plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
  

[JIRA] [managed-scripts-plugin] (JENKINS-32813) managed shell scripts are run without -eu

[jenk...@duigou.org (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mike Duigou created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32813 
 
 
 
  managed shell scripts are run without -eu  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Dominik Bartholdi 
 
 
 

Components:
 

 managed-scripts-plugin 
 
 
 

Created:
 

 05/Feb/16 9:41 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Mike Duigou 
 
 
 
 
 
 
 
 
 
 
Unmanaged shell scripts are run with the -e and -u options to exit on errors and exit on undefined. Managed scripts should follow the same excellent practice. 
workaround: #!/bin/sh -eu 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 
 

[JIRA] [config-file-provider-plugin] (JENKINS-16706) Configure provided settings.xml at the Maven plugin level, not at the Maven job level

[jenk...@duigou.org (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mike Duigou commented on  JENKINS-16706 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Configure provided settings.xml at the Maven plugin level, not at the Maven job level  
 
 
 
 
 
 
 
 
 
 
The maven plugin "Maven Configuration" of settings.xml seems to be entirely ignored by projects and by scripts which try to run mvn executable directly. The project level "Use default maven settings" should respect the plugin level setting. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [vmware-vrealize-automation-plugin] (JENKINS-32812) Blueprint paramemters

[kris.thie...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kris Thieler created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32812 
 
 
 
  Blueprint paramemters  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Kris Thieler 
 
 
 

Components:
 

 vmware-vrealize-automation-plugin 
 
 
 

Created:
 

 05/Feb/16 9:21 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Kris Thieler 
 
 
 
 
 
 
 
 
 
 
The vRA Jenkins plugin must allow parameters to be passed during the request of a blueprint. Example parameters would be CPU or memory. Parameters can vary based on the blueprint being requested 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

   

[JIRA] [vmware-vrealize-automation-plugin] (JENKINS-32811) Expire environment

[kris.thie...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kris Thieler created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32811 
 
 
 
  Expire environment  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Kris Thieler 
 
 
 

Components:
 

 vmware-vrealize-automation-plugin 
 
 
 

Created:
 

 05/Feb/16 9:12 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Kris Thieler 
 
 
 
 
 
 
 
 
 
 
The vRA jenkins plugin must have the ability to expire environments. The ability to expire an environment will be added as a post build action. This improvement is dependent on https://issues.jenkins-ci.org/browse/JENKINS-32810 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 
  

[JIRA] [core] (JENKINS-32806) "Failed to run task: 'gulp bundle test --no-color'" while building

[tom.fenne...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tom FENNELLY commented on  JENKINS-32806 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "Failed to run task: 'gulp bundle test --no-color'" while building  
 
 
 
 
 
 
 
 
 
 
Hey Oliver (Oliver Gondža), the fact that the PR builds ran okay might suggest that something local has gone wrong. Would you be able to delete war/node_modules (or run mvn clean -cleanNode) and try building again. 
Otherwise ... hmmm... what OS, node version etc are running on your local machine ? (the local node version shouldn't matter actually) etc  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [vmware-vrealize-automation-plugin] (JENKINS-32810) Return environment environment name

[kris.thie...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kris Thieler updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32810 
 
 
 
  Return environment environment name  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kris Thieler 
 
 
 

Priority:
 
 Minor Major 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [vmware-vrealize-automation-plugin] (JENKINS-32810) Return environment environment name

[kris.thie...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kris Thieler created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32810 
 
 
 
  Return environment environment name  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Kris Thieler 
 
 
 

Components:
 

 vmware-vrealize-automation-plugin 
 
 
 

Created:
 

 05/Feb/16 9:07 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Kris Thieler 
 
 
 
 
 
 
 
 
 
 
As a devops hero, I want the vRA Jenkins plugin to know the resulting environment details from the blueprint request. 
The environment name must be returned to Jenkins so that post build activities can be added. For example, a post build activity to expire the environment. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 

[JIRA] [vmware-vrealize-automation-plugin] (JENKINS-32261) Exclude bcprov dependencies

[kris.thie...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kris Thieler started work on  JENKINS-32261 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Kris Thieler 
 
 
 

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] [matrix-project-plugin] (JENKINS-32809) SCM workspace being flushed to 0 when old builds are discarded in Matrix Builds

[david.yonghsiang....@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Kuo created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32809 
 
 
 
  SCM workspace being flushed to 0 when old builds are discarded in Matrix Builds  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Kohsuke Kawaguchi 
 
 
 

Components:
 

 matrix-project-plugin, perforce-plugin 
 
 
 

Created:
 

 05/Feb/16 8:05 PM 
 
 
 

Environment:
 

 Ubuntu 14.04 LTS x64  Jenkins 1.642.1 LTS  Perforce Plugin 1.3.35 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 David Kuo 
 
 
 
 
 
 
 
 
 
 
It looks like when matrix jobs try to discard old builds, it also flushes my perforce workspaces to 0. 
 
Feb 04, 2016 3:34:40 AM hudson.plugins.perforce.PerforceSCM processWorkspaceBeforeDeletion INFO: Workspace 'c:\jenkins\workspace\matrix_job' is being deleted; flushing workspace to revision 0. Feb 04, 2016 3:34:40 AM hudson.plugins.perforce.PerforceSCM processWorkspaceBeforeDeletion INFO: Using remote perforce client: buildmachine01 Feb 04, 2016 3:34:40 AM hudson.plugins.perforce.PerforceSCM processWorkspaceBeforeDeletion INFO: [matrix_job] $ p4 workspace -o buildmachine01 Feb 04, 2016 3:34:40 AM hudson.plugins.perforce.PerforceSCM processWorkspaceBeforeDeletion INFO: 'Don't update client' is set. Not saving the client changes. Feb 04, 2016 3:34:40 AM hudson.plugins.perforce.PerforceSCM processWorkspaceBeforeDeletion INFO: [matrix_job] $ p4 sync -k //buildmachine01/...#0 Feb 04, 2016 3:34:59 AM hudson.model.

[JIRA] [htmlpublisher-plugin] (JENKINS-32757) Problem with htmlpublisher plugin when upgraded jenkins from 1.634 to 1.646

[da...@ascnet.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Darin Bailey closed an issue as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Thanks... Found the configuration issue just before you updated this bug. I have made the suggested changes and the html npow displays successfully. Thanks for your help. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32757 
 
 
 
  Problem with htmlpublisher plugin when upgraded jenkins from 1.634 to 1.646  
 
 
 
 
 
 
 
 
 

Change By:
 
 Darin Bailey 
 
 
 

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-32806) "Failed to run task: 'gulp bundle test --no-color'" while building

[ogon...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oliver Gondža commented on  JENKINS-32806 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "Failed to run task: 'gulp bundle test --no-color'" while building  
 
 
 
 
 
 
 
 
 
 
Broken since 036a8e94ed37cf851f0cafb9cb12c21e3496ed7c. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32808) windows 7 slaves intermittent disconnect

[d...@cypress.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Donald Duncan created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32808 
 
 
 
  windows 7 slaves intermittent disconnect  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 installed_plugins.htm 
 
 
 

Components:
 

 core, remoting 
 
 
 

Created:
 

 05/Feb/16 7:06 PM 
 
 
 

Environment:
 

 Jenkins master 1.642.1 under centos 6.6, open jdk7u75. Jenkins master is a vm under ESXi 5.5. slave is windows 7 pro sp1, 64bit, jre8u71. slave.jar is v2.47. Master is located in Tigard, OR. Slave is in Ukraine. WAN is Sprint MPLS. See attachment installed_plugins.htm for a list of installed plugins. 
 
 
 

Labels:
 

 jenkins exception windows slave 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Donald Duncan 
 
 
 
 
 
 
 
 
 
 
Chronic intermittent slave disconnect issues with many wi

[JIRA] [htmlpublisher-plugin] (JENKINS-29679) Back link doesnt work after job renaming

[mcroo...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 mcrooney resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Thanks for the hint Daniel and thanks so much for all your bug triaging, you are an HTML Publisher hero  Tested and looks good to me. I'll update the wiki as well. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-29679 
 
 
 
  Back link doesnt work after job renaming  
 
 
 
 
 
 
 
 
 

Change By:
 
 mcrooney 
 
 
 

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] [htmlpublisher-plugin] (JENKINS-32281) HTML report shows "Checksum mismatch"

[anthony.mastr...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anthony Mastrean commented on  JENKINS-32281 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: HTML report shows "Checksum mismatch"  
 
 
 
 
 
 
 
 
 
 
I converted all of my custom reports to plugin-based-reports! If no one else can repro the fix, I'll try to spin up one of my older configurations. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ec2-plugin] (JENKINS-32779) Spot instance hit cap when sharing a AMI

[ja...@lab-y.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 James Judd edited a comment on  JENKINS-32779 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Spot instance hit cap when sharing a AMI  
 
 
 
 
 
 
 
 
 
 Also seeing this since 1.312 ec2 configs in the same cloud sharing the same AMI. First config with limit 4. Second config with limit 2.2 instances of config 1 are launched -> cannot launch any of config 2Change instance limit of config 2 to 3+ -> config 2 launchesMy guess is that the limits are read per config but the total when launching an instance from a config is calculated  using  from  all instances using that AMI. Note: If it makes any difference, the instances above were all spot instances. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [claim-plugin] (JENKINS-27206) Enable claim support from workflow

[mpapo....@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Pailloncy commented on  JENKINS-27206 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Enable claim support from workflow  
 
 
 
 
 
 
 
 
 
 
Hi, not sure to understand how to use it. I get the same NPE as Baptiste Mathus (ClaimPublisher:62).  
The only way I've found for now is to do something like this :  

 

try {
  echo "boum"  
  sh "mvn is-not-in-PATH"
} catch (err) {
  currentBuild.result = hudson.model.Result.FAILURE
  step([$class: 'ClaimPublisher'])   
}
 

 
is there another way ? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ec2-plugin] (JENKINS-32779) Spot instance hit cap when sharing a AMI

[ja...@lab-y.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 James Judd edited a comment on  JENKINS-32779 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Spot instance hit cap when sharing a AMI  
 
 
 
 
 
 
 
 
 
 Also seeing this since 1.31 2 ec2 configs in the same cloud sharing the same AMI. First config with limit 4. Second config with limit 2.2 instances of config 1 are launched -> cannot launch any of config 2Change instance limit of config 2 to 3+ -> config 2 launchesMy guess is that the limits are read per config but the total when launching an instance from a config is calculated using all instances using that AMI. Note: If it makes any difference, the instances above were all spot instances. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32805) Poll SCM Schedule form validation is wrong for @hourly, @daily

[russell.gal...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Gallop commented on  JENKINS-32805 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Poll SCM Schedule form validation is wrong for @hourly, @daily  
 
 
 
 
 
 
 
 
 
 
In TimerTrigger.java the check is implemented by: 

 

public FormValidation doCheckSpec(@QueryParameter String value, @AncestorInPath Item item) {
try {
CronTabList ctl = CronTabList.create(fixNull(value), item != null ? Hash.from(item.getFullName()) : null);
 

 
which I guess is finding the name of the item in the URL for the hash. 
It looks like "Build Periodically" is using the checkUrl:  {http:///job/TestCron/descriptorByName/hudson.triggers.TimerTrigger/checkSpec?value=%40daily} 
 but "Poll SCM" is using  {http:///trigger/TimerTrigger/check?value=%40daily} 
. 
So Poll SCM is probably unable to find the item name in the URL so initialises the hash with null and generates the previous and next times for that. This matches up with the fact that changing the job name affects the periodic schedule but not the SCM schedule (which is 0 apart from the seconds). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32805) Poll SCM Schedule form validation is wrong for @hourly, @daily

[russell.gal...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Gallop edited a comment on  JENKINS-32805 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Poll SCM Schedule form validation is wrong for @hourly, @daily  
 
 
 
 
 
 
 
 
 
 In TimerTrigger.java the check is implemented by:{code}public FormValidation doCheckSpec(@QueryParameter String value, @AncestorInPath Item item) {try {CronTabList ctl = CronTabList.create(fixNull(value), item != null ? Hash.from(item.getFullName()) : null);{code}which I guess is finding the name of the item in the URL for the hash.It looks like "Build Periodically" is using the checkUrl: { { http:///job/TestCron/descriptorByName/hudson.triggers.TimerTrigger/checkSpec?value=%40daily} }  but "Poll SCM" is using { { http:///trigger/TimerTrigger/check?value=%40daily} } .So Poll SCM is probably unable to find the item name in the URL so initialises the hash with null and generates the previous and next times for that. This matches up with the fact that changing the job name affects the periodic schedule but not the SCM schedule (which is 0 apart from the seconds). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ec2-plugin] (JENKINS-32779) Spot instance hit cap when sharing a AMI

[ja...@lab-y.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 James Judd commented on  JENKINS-32779 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Spot instance hit cap when sharing a AMI  
 
 
 
 
 
 
 
 
 
 
Also seeing this since 1.31 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32567) Downgrade “termination trace” warnings in Jenkins logs

[yoann.dubre...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Yoann Dubreuil commented on  JENKINS-32567 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Downgrade “termination trace” warnings in Jenkins logs  
 
 
 
 
 
 
 
 
 
 
Thanks a lot Oliver Gondža for the explanation and for backporting. Much appreciated. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ec2-plugin] (JENKINS-32690) Cannot manually provision new slave if one already exists

[luigi.tagliamont...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Luigi Tagliamonte commented on  JENKINS-32690 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cannot manually provision new slave if one already exists  
 
 
 
 
 
 
 
 
 
 
i'm also hitting the same problem. I need to have a fleet of slaves already configured, since it took more than 10min at the first boot to initialise all the dependencies that i need. Can we add a + button that overrides this new behaviour? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [openshift-deployer-plugin] (JENKINS-32807) Jenkins openshift plugin not working

[rakesh_krishnaku...@hotmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 rakesh krishnakumar created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32807 
 
 
 
  Jenkins openshift plugin not working  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Siamak Sadeghianfar 
 
 
 

Components:
 

 openshift-deployer-plugin 
 
 
 

Created:
 

 05/Feb/16 4:12 PM 
 
 
 

Environment:
 

 Linux on z system - mainframe 
 
 
 

Priority:
 
  Trivial 
 
 
 

Reporter:
 
 rakesh krishnakumar 
 
 
 
 
 
 
 
 
 
 
ERROR 
A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace 
javax.servlet.ServletException: com.openshift.client.OpenShiftEndpointException: Could not request https://129.40.45.13:8443/broker/rest/api:  at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler

[JIRA] [_unsorted] (JENKINS-32796) Can't update plugins: incorrect checksum

[db...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck resolved as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Probably a misconfigured internet connection, a (temporarily?) bad mirror, or an MITM attack. Not a bug in Jenkins (the bug was that checksums weren't verified for a long time). 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32796 
 
 
 
  Can't update plugins: incorrect checksum  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Status:
 
 Open Resolved 
 
 
 

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] [core] (JENKINS-26813) Missing configuration sections in freestyle multibranch projects

[db...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-26813 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Missing configuration sections in freestyle multibranch projects  
 
 
 
 
 
 
 
 
 
 

The problem is still present, and is in a Jenkins plugin that is being tracked in Jira
 
I was referring to this comment by Jesse: https://issues.jenkins-ci.org/browse/JENKINS-26815?focusedCommentId=221248&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-221248 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32806) "Failed to run task: 'gulp bundle test --no-color'" while building

[ogon...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oliver Gondža commented on  JENKINS-32806 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "Failed to run task: 'gulp bundle test --no-color'" while building  
 
 
 
 
 
 
 
 
 
 
Speculatively assignig to Tom. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32806) "Failed to run task: 'gulp bundle test --no-color'" while building

[ogon...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oliver Gondža created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32806 
 
 
 
  "Failed to run task: 'gulp bundle test --no-color'" while building  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Tom FENNELLY 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 05/Feb/16 3:31 PM 
 
 
 

Labels:
 

 2.0 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Oliver Gondža 
 
 
 
 
 
 
 
 
 
 
I am unable to build Jenkins 2.0 because of the gulp error: 

 
[INFO] --- frontend-maven-plugin:0.0.23:gulp (gulp test) @ jenkins-war ---
[INFO] Running 'gulp bundle test --no-color' in /home/ogondza/code/jenkins/jenkins/war
[INFO] [15:54:27] Maven project
[INFO] [15:54:27]  - src: src/main/js,src/main/less
[INFO] [15:54:27]  - test: src/test/js
[INFO] [15:54:27] Setting defaults
[INFO] [15:54:27] Bundle will be generated in directory 'src/main/webapp/jsbundles' as 'pluginSetupWizard.js'.
[INFO] [15:54:27] Using gulpfile ~/code/jenkins/jenkins/war/gulpfile.js
[INFO] [15:54:27] Starting 'bundle_pluginSetupWizard'...
[INFO] [15:54:27] LESS CSS pre-processing completed.
[INFO] [15:54:27] Finished 'bundle_pluginSetupWizard' after 895 ms
[INFO] [15:54:27] Starting 'bundle'...
[INFO] [15:54:27] Finished 'bundle' after 22 μs
[INFO] [15:54:27] Starting 'test'...
[INFO] [15:54:27] Test specs: src/test/js/**/*-spec.js
[INFO] [15:54:27] Testing web server started on port 18999 (h

[JIRA] [active-directory-plugin] (JENKINS-32623) Incorrect user URL for users with backslashes in name

[russell.gal...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Gallop commented on  JENKINS-32623 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Incorrect user URL for users with backslashes in name  
 
 
 
 
 
 
 
 
 
 
The "Started by user" message on the build page is not correctly escaped. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32805) Poll SCM Schedule form validation is wrong for @hourly, @daily

[russell.gal...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Gallop created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32805 
 
 
 
  Poll SCM Schedule form validation is wrong for @hourly, @daily  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 PollSCMScheduleValidation.PNG 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 05/Feb/16 3:18 PM 
 
 
 

Environment:
 

 jenkins 1.642.1 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Russell Gallop 
 
 
 
 
 
 
 
 
 
 
After entering a schedule such as @hourly or @daily in the "Poll SCM" (SCMTrigger) field the form validation reports when it would have last run and will next run. The times that it reports however appear to be different from the times that the SCM is actually polled. The times for "Build Periodically" (TimerTrigger) appear to be correct. 
I have created a job called "TestCron" and that shows different times for Poll SCM and Build Periodically (see screenshot). It appears to me that these should both be the same as they are based on the hash of the item name. 
 
 

[JIRA] [core] (JENKINS-24764) Tabs are wrapping on narrow screens

[median...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Jones resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
This is resolved in the latest builds; on Jenkins 1.642.1 LTS I no longer observe this problem, and it was resolved at least several LTS releases prior to that. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-24764 
 
 
 
  Tabs are wrapping on narrow screens  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nick Jones 
 
 
 

Status:
 
 Reopened 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] [cucumber-plugin] (JENKINS-32804) Cucumber 'pretty' reports are not displayed

[ty...@monkeypox.org (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 R. Tyler Croy moved an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32804 
 
 
 
  Cucumber 'pretty' reports are not displayed  
 
 
 
 
 
 
 
 
 

Change By:
 
 R. Tyler Croy 
 
 
 

Project:
 
 Infrastructure Jenkins 
 
 
 

Key:
 
 INFRA JENKINS - 556 32804 
 
 
 

Workflow:
 
 classic default workflow JNJira 
 
 
 

Component/s:
 
 cucumber-plugin 
 
 
 

Component/s:
 
 ci 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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

[JIRA] [core] (JENKINS-32802) Can't load Update Center from FTP mirror

[gerard.choi...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Gerard Choinka commented on  JENKINS-32802 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Can't load Update Center from FTP mirror  
 
 
 
 
 
 
 
 
 
 
Same for me, i event can't apt-get install jenkins without an 302 

 

root@jenkins-front:/var/lib/jenkins# sudo apt-get download jenkins
Err http://pkg.jenkins-ci.org/debian/ binary/ jenkins 1.647
  302  Found
E: Failed to fetch http://pkg.jenkins-ci.org/debian/binary/jenkins_1.647_all.deb  302  Found

root@jenkins-front:/var/lib/jenkins# wget http://pkg.jenkins-ci.org/debian/binary/jenkins_1.647_all.deb
--2016-02-05 14:54:55--  http://pkg.jenkins-ci.org/debian/binary/jenkins_1.647_all.deb
Resolving pkg.jenkins-ci.org (pkg.jenkins-ci.org)... 199.193.196.24
Connecting to pkg.jenkins-ci.org (pkg.jenkins-ci.org)|199.193.196.24|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://mirrors.jenkins-ci.org/debian/jenkins_1.647_all.deb [following]
--2016-02-05 14:54:56--  http://mirrors.jenkins-ci.org/debian/jenkins_1.647_all.deb
Resolving mirrors.jenkins-ci.org (mirrors.jenkins-ci.org)... 199.193.196.24
Connecting to mirrors.jenkins-ci.org (mirrors.jenkins-ci.org)|199.193.196.24|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: ftp://ftp.halifax.rwth-aachen.de/jenkins/debian/jenkins_1.647_all.deb [following]
--2016-02-05 14:54:56--  ftp://ftp.halifax.rwth-aachen.de/jenkins/debian/jenkins_1.647_all.deb
   => ‘jenkins_1.647_all.deb’
Resolving ftp.halifax.rwth-aachen.de (ftp.halifax.rwth-aachen.de)... 137.226.34.46, 2a00:8a60:e012:a00::21
Connecting to ftp.halifax.rwth-aachen.de (ftp.halifax.rwth-aachen.de)|137.226.34.46|:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done.==> PWD ... done.
==> TYPE I ... done.  ==> CWD (1) /jenkins/debian ... done.
==> SIZE jenkins_1.647_all.deb ... 63034990
==> PASV ... done.==> RETR jenkins_1.647_all.deb ... done.
Length: 63034990 (60M) (unauthoritative)

100%[==>] 63,034,990  5.42MB/s   in 11s

2016-02-05 14:55:08 (5.39 MB/s) - ‘jenkins_1.647_all.deb’ saved [63034990]

root@jenkins-front:/var/lib/jenkins# cat /etc/apt/sources.list.d/jenkins.list 
deb http://pkg.jenkins-ci.org/debian binary/
 

 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

  

[JIRA] [core] (JENKINS-23366) jdk8u5 installation fails on windows slaves

[j9...@verizon.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 JP Marple commented on  JENKINS-23366 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: jdk8u5 installation fails on windows slaves  
 
 
 
 
 
 
 
 
 
 
Any plan to resolve this issue? 
The error is indeed due to spaces in the quoted path after the switch for the log file. If the path to the log file doesnt contain spaces, the command works fine. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [bitbucket-plugin] (JENKINS-31185) Bitbucket Plugin: add scm hg

[jens.scho...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jens Schoedt reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
I get the following in my log but the items are never started even though they are set up with the "Build when a change is pushed to BitBucket" option: 
Jenkins ver. 1.647 
 
Processing new Webhooks payload Feb 05, 2016 3:45:01 PM INFO com.cloudbees.jenkins.plugins.BitbucketPayloadProcessor processWebhookPayload Received commit hook notification for {"website":"","is_private":true,"links":{"html": 

Unknown macro: {"href"} 
 
,"avatar": 

Unknown macro: {"href"} 
 
,"self":{"href":"https://api.bitbucket.org/2.0/repositories/schodt/labbird"}},"owner":{"type":"user","uuid":" 

Unknown macro: {6b9bcc04-7fb7-4c5b-ab21-ba1cb855b02e} 
 
","username":"schodt","links":{"html": 

Unknown macro: {"href"} 
 
,"avatar": 

Unknown macro: {"href"} 
 
,"self":{"href":"https://api.bitbucket.org/2.0/users/schodt"}},"display_name":"Jens Schoedt"},"name":"labbird","full_name":"schodt/labbird","scm":"hg","uuid":" 

Unknown macro: {99d0a520-55e0-423a-acd7-2c4fe6d07dd0} 
 
","type":"repository"}
 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-31185 
 
 
 
  Bitbucket Plugin: add scm hg  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jens Schoedt 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Resolved Reopened 
 
 
 
 
 
 

[JIRA] [git-client-plugin] (JENKINS-30045) Git client plugin does not work with new Git for Windows 2.5.0

[mark.earl.wa...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite assigned an issue to Mark Waite 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30045 
 
 
 
  Git client plugin does not work with new Git for Windows 2.5.0  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mark Waite 
 
 
 

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-client-plugin] (JENKINS-30045) Git client plugin does not work with new Git for Windows 2.5.0

[mark.earl.wa...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite commented on  JENKINS-30045 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Git client plugin does not work with new Git for Windows 2.5.0  
 
 
 
 
 
 
 
 
 
 
I now have a machine which shows the problem. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [_unsorted] (JENKINS-32798) apt-get: Failed to fetch http://pkg.jenkins-ci.org

[m...@adrian-kirchner.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adrian Kirchner commented on  JENKINS-32798 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: apt-get: Failed to fetch http://pkg.jenkins-ci.org  
 
 
 
 
 
 
 
 
 
 
Same problem here. Further informations: 
I did: 

 
$ apt-get clean

$ apt-get update

$ apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
  jenkins
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 63.0 MB of archives.
After this operation, 7168 B of additional disk space will be used.
Do you want to continue [Y/n]? Y
Err http://pkg.jenkins-ci.org/debian/ binary/ jenkins 1.647
  302  Found
Failed to fetch http://pkg.jenkins-ci.org/debian/binary/jenkins_1.647_all.deb  302  Found
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
 



 

$ uname -a
Linux butch 3.2.0-4-amd64 #1 SMP Debian 3.2.73-2+deb7u2 x86_64 GNU/Linux
 



 

$ cat /etc/debian_version
7.9
 



 

$ apt-get --version
apt 0.9.7.9 for amd64 compiled on Oct 17 2014 09:15:56
Supported modules:
*Ver: Standard .deb
*Pkg:  Debian dpkg interface (Priority 30)
 Pkg:  Debian APT solver interface (Priority -1000)
 S.L: 'deb' Standard Debian binary tree
 S.L: 'deb-src' Standard Debian source tree
 Idx: Debian Source Index
 Idx: Debian Package Index
 Idx: Debian Translation Index
 Idx: Debian dpkg status file
 Idx: EDSP scenario file
 

 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
 

[JIRA] [selenium-plugin] (JENKINS-25583) Unexpected error in launching a slave. This is probably a bug in Jenkins.

[nagmani.pra...@synerzip.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nagmani Prasad edited a comment on  JENKINS-25583 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unexpected error in launching a slave. This is probably a bug in Jenkins.  
 
 
 
 
 
 
 
 
 
 I have faced similar issue, to  resolved  resolve  this issue, uncheck the 'Selenium Plugin' from installed manage plugin screen (i.e./pluginManager/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] [selenium-plugin] (JENKINS-25583) Unexpected error in launching a slave. This is probably a bug in Jenkins.

[nagmani.pra...@synerzip.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nagmani Prasad commented on  JENKINS-25583 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unexpected error in launching a slave. This is probably a bug in Jenkins.  
 
 
 
 
 
 
 
 
 
 
I have faced similar issue, to resolved this issue, uncheck the 'Selenium Plugin' from installed manage plugin screen (i.e./pluginManager/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] [authorize-project-plugin] (JENKINS-32770) Provide a mechanism to run specific projects as ACL.SYSTEM

[jgl...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick started work on  JENKINS-32770 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

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] [github-branch-source-plugin] (JENKINS-32155) Recognize new repositories automatically

[rec...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto edited a comment on  JENKINS-32155 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Recognize new repositories automatically  
 
 
 
 
 
 
 
 
 
 [~jglick] and  @stephe  [~stephenconnolly]  have the same opinion. The [verdict|https://github.com/jenkinsci/github-branch-source-plugin/pull/13#issuecomment-180348711] is taken. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-branch-source-plugin] (JENKINS-32155) Recognize new repositories automatically

[rec...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto commented on  JENKINS-32155 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Recognize new repositories automatically  
 
 
 
 
 
 
 
 
 
 
Jesse Glick and @stephe have the same opinion. The verdict is taken. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-30354) Cannot retrieve plugins in any browser

[gther...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Guillaume Théraud commented on  JENKINS-30354 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cannot retrieve plugins in any browser  
 
 
 
 
 
 
 
 
 
 
Same issue when jenkins is connecting to FTP mirror. Fixed using another location mirror, which in this case is HTTP. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-26813) Missing configuration sections in freestyle multibranch projects

[john.mel...@esentire.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Mellor reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
I do not understand the previous comment and reason for incorrectly closing this issue. The problem is still present, and is in a Jenkins plugin that is being tracked in Jira. If the issue is not in the multi-branch plugin, then where is it? I assume that this is in Core. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-26813 
 
 
 
  Missing configuration sections in freestyle multibranch projects  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Mellor 
 
 
 

Resolution:
 
 Not A Defect 
 
 
 

Status:
 
 Resolved Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [zephyr-for-jira-test-management-plugin] (JENKINS-32801) Pipeline build step for Zephyr for Jira

[ifernandezca...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ivan Fernandez Calvo commented on  JENKINS-32801 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Pipeline build step for Zephyr for Jira  
 
 
 
 
 
 
 
 
 
 
I think so, It is enough 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [credentials-plugin] (JENKINS-32803) Clone user Credentials only takes uername/password. Need ssh-key

[thewiseout...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Babumoses created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32803 
 
 
 
  Clone user Credentials only takes uername/password. Need ssh-key  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 stephenconnolly 
 
 
 

Components:
 

 credentials-plugin 
 
 
 

Created:
 

 05/Feb/16 1:51 PM 
 
 
 

Environment:
 

 vsphere plugin 2.9 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Mark Babumoses 
 
 
 
 
 
 
 
 
 
 
The clone user only takes a username+password combination. We lock down our slaves to ssh-keys for more security. It would be good to have this option as well. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
   

[JIRA] [scriptler-plugin] (JENKINS-31973) When using the scriptler plugin the server is responding very slow

[esc...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Emilio Escobar  commented on  JENKINS-31973 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: When using the scriptler plugin the server is responding very slow  
 
 
 
 
 
 
 
 
 
 
Hi Dominik, this is not an issue of scriptler. This behaviour only appears if you combines: 
 

project-inheritance:1.5.3 (not reproduced in 1.5.1 as is said at https://issues.jenkins-ci.org/browse/JENKINS-23993 )
 

uno-choice:1.2 (scriptler:2.7 is required by uno-choice)
 
 
project-inheritance ask for the default value of each parameter and in the case of uno-choice (don't know if scriptler too) runs the groovy script (with a lack of performance of the system). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [zephyr-for-jira-test-management-plugin] (JENKINS-32801) Pipeline build step for Zephyr for Jira

[jgl...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick commented on  JENKINS-32801 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Pipeline build step for Zephyr for Jira  
 
 
 
 
 
 
 
 
 
 
Presumably you mean to make ZfjReporter a SimpleBuildStep? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [scriptler-plugin] (JENKINS-31973) When using the scriptler plugin the server is responding very slow

[d...@fortysix.ch (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dominik Bartholdi commented on  JENKINS-31973 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: When using the scriptler plugin the server is responding very slow  
 
 
 
 
 
 
 
 
 
 
so far i was not able to reproduce this - can you reproduce it on a minimal new installation? 
could you please also get a thread dump while seeing this issue and make it available somewhere? https://wiki.jenkins-ci.org/display/JENKINS/Obtaining+a+thread+dump 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-27944) Auto-installer list not populating on Ubuntu Server

[franzw...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Franz Wong commented on  JENKINS-27944 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Auto-installer list not populating on Ubuntu Server  
 
 
 
 
 
 
 
 
 
 
ickersep This is the way I tried and worked. Get the json file from http://updates.jenkins-ci.org/updates/hudson.plugins.nodejs.tools.NodeJSInstaller.json [1] Create a file "/var/lib/jenkins/updates/hudson.plugins.nodejs.tools.NodeJSInstaller" [2] Copy the second parameter json object inside file [1] to the new file [2] created 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-18687) Intermittent failure whilst recording test results caused by java.util.MissingResourceException

[lvoty...@redhat.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lucie Votypkova edited a comment on  JENKINS-18687 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Intermittent failure whilst recording test results caused by java.util.MissingResourceException  
 
 
 
 
 
 
 
 
 
 I did a more investigation - I finally got the problem when it occurs - usually slave was restarted and fine when I received the ticket about this problem.I even find exact place where it is. To more explanation there is a difference in obtaining property.  for example my code on affected slave:{{PropertyResourceBundle.getBundle("com.sun.org.apache.xerces.internal.impl.msg.SAXMessages", Locale.US)}} this return right bundle without problems. but calling (as it is done in by in SAXReader used by this plugin) {{SecuritySupport.getResourceBundle("com.sun.org.apache.xerces.internal.impl.msg.SAXMessages", new Locale("en", "US"));}}this throws exception MissingResourceException.It is very strange because SecuritySupport.getResourceBundle() calls the same code (PropertyResourceBundle.getBundle("com.sun.org.apache.xerces.internal.impl.msg.SAXMessages", Locale.US) ) bud under AccessController.doPrivileged(): {{public static ResourceBundle getResourceBundle(final String bundle, final Locale locale) {}}{{return AccessController http://grepcode . doPrivileged(new PrivilegedAction() {}}public ResourceBundle run() {try {return PropertyResourceBundle com/file/repository . getBundle(bundle, locale);} catch (MissingResourceException e) {try {return PropertyResourceBundle grepcode . getBundle(bundle, new Locale("en", "US")); com/java/root/jdk/openjdk/8-b132/com/sun/org/apache/xerces/internal/utils/SecuritySupport.java#165  } catch (MissingResourceException e2) {  throw new MissingResourceException("Could not load any resource bundle by " + bundle, bundle, "");}}}});} It seems that there is some difference in execution this code (despite it is the same). I will try to investigate what is different. That could be a way how to realized what is wrong. I think that it maybe will not be problem in plugin itself (bug in jdk or remoting or leaking some classes for master).Have any of us idea? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
   

[JIRA] [core] (JENKINS-18687) Intermittent failure whilst recording test results caused by java.util.MissingResourceException

[lvoty...@redhat.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lucie Votypkova edited a comment on  JENKINS-18687 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Intermittent failure whilst recording test results caused by java.util.MissingResourceException  
 
 
 
 
 
 
 
 
 
 I did a more investigation - I finally got the problem when it occurs - usually slave was restarted and fine when I received the ticket about this problem.I even find exact place where it is. To more explanation there is a difference in obtaining property.  for example my code on affected slave:{{PropertyResourceBundle.getBundle("com.sun.org.apache.xerces.internal.impl.msg.SAXMessages", Locale.US)}} this return right bundle without problems. but calling (as it is done in by in SAXReader used by this plugin) {{SecuritySupport.getResourceBundle("com.sun.org.apache.xerces.internal.impl.msg.SAXMessages", new Locale("en", "US"));}}this throws exception MissingResourceException.It is very strange because SecuritySupport.getResourceBundle() calls the same code (PropertyResourceBundle.getBundle("com.sun.org.apache.xerces.internal.impl.msg.SAXMessages", Locale.US) ) bud under AccessController.doPrivileged():{{public static ResourceBundle getResourceBundle(final String bundle, final Locale locale) {}} {{ return AccessController.doPrivileged(new PrivilegedAction() { }} public ResourceBundle run() {try {return PropertyResourceBundle.getBundle(bundle, locale);} catch (MissingResourceException e) {try {return PropertyResourceBundle.getBundle(bundle, new Locale("en", "US"));} catch (MissingResourceException e2) {throw new MissingResourceException("Could not load any resource bundle by " + bundle, bundle, "");}}}});}It seems that there is some difference in execution this code (despite it is the same). I will try to investigate what is different. That could be a way how to realized what is wrong. I think that it maybe will not be problem in plugin itself (bug in jdk or remoting or leaking some classes for master).Have any of us idea? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
   

[JIRA] [core] (JENKINS-18687) Intermittent failure whilst recording test results caused by java.util.MissingResourceException

[lvoty...@redhat.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lucie Votypkova edited a comment on  JENKINS-18687 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Intermittent failure whilst recording test results caused by java.util.MissingResourceException  
 
 
 
 
 
 
 
 
 
 I did a more investigation - I finally got the problem when it occurs - usually slave was restarted and fine when I received the ticket about this problem.I even find exact place where it is. To more explanation there is a difference in obtaining property.  for example my code on affected slave:{{PropertyResourceBundle.getBundle("com.sun.org.apache.xerces.internal.impl.msg.SAXMessages", Locale.US)}} this return right bundle without problems. but calling (as it is done in by in SAXReader used by this plugin) {{SecuritySupport.getResourceBundle("com.sun.org.apache.xerces.internal.impl.msg.SAXMessages", new Locale("en", "US"));}}this throws exception MissingResourceException.It is very strange because SecuritySupport.getResourceBundle() calls the same code (PropertyResourceBundle.getBundle("com.sun.org.apache.xerces.internal.impl.msg.SAXMessages", Locale.US) ) bud under AccessController.doPrivileged():{{public static ResourceBundle getResourceBundle(final String bundle, final Locale locale) { }} return AccessController.doPrivileged(new PrivilegedAction() {public ResourceBundle run() {try {return PropertyResourceBundle.getBundle(bundle, locale);} catch (MissingResourceException e) {try {return PropertyResourceBundle.getBundle(bundle, new Locale("en", "US"));} catch (MissingResourceException e2) {throw new MissingResourceException("Could not load any resource bundle by " + bundle, bundle, "");}}}});} }} It seems that there is some difference in execution this code (despite it is the same). I will try to investigate what is different. That could be a way how to realized what is wrong. I think that it maybe will not be problem in plugin itself (bug in jdk or remoting or leaking some classes for master).Have any of us idea? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 

[JIRA] [core] (JENKINS-18687) Intermittent failure whilst recording test results caused by java.util.MissingResourceException

[lvoty...@redhat.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lucie Votypkova edited a comment on  JENKINS-18687 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Intermittent failure whilst recording test results caused by java.util.MissingResourceException  
 
 
 
 
 
 
 
 
 
 I did a more investigation - I finally got the problem when it occurs - usually slave was restarted and fine when I received the ticket about this problem.I even find exact place where it is. To more explanation there is a difference in obtaining property.  for example my code on affected slave:{{PropertyResourceBundle.getBundle("com.sun.org.apache.xerces.internal.impl.msg.SAXMessages", Locale.US)}} this return right bundle without problems. but calling (as it is done in by in SAXReader used by this plugin)  {{ SecuritySupport.getResourceBundle("com.sun.org.apache.xerces.internal.impl.msg.SAXMessages", new Locale("en", "US")); }} this throws exception MissingResourceException.It is very strange because SecuritySupport.getResourceBundle() calls the same code (PropertyResourceBundle.getBundle("com.sun.org.apache.xerces.internal.impl.msg.SAXMessages", Locale.US) ) bud under AccessController.doPrivileged(): {{ public static ResourceBundle getResourceBundle(final String bundle, final Locale locale) {return AccessController.doPrivileged(new PrivilegedAction() {public ResourceBundle run() {try {return PropertyResourceBundle.getBundle(bundle, locale);} catch (MissingResourceException e) {try {return PropertyResourceBundle.getBundle(bundle, new Locale("en", "US"));} catch (MissingResourceException e2) {throw new MissingResourceException("Could not load any resource bundle by " + bundle, bundle, "");}}}});} }} It seems that there is some difference in execution this code (despite it is the same). I will try to investigate what is different. That could be a way how to realized what is wrong. I think that it maybe will not be problem in plugin itself (bug in jdk or remoting or leaking some classes for master).Have any of us idea? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
   

[JIRA] [core] (JENKINS-18687) Intermittent failure whilst recording test results caused by java.util.MissingResourceException

[lvoty...@redhat.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lucie Votypkova edited a comment on  JENKINS-18687 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Intermittent failure whilst recording test results caused by java.util.MissingResourceException  
 
 
 
 
 
 
 
 
 
 I did a more investigation - I finally got the problem when it occurs - usually slave was restarted and fine when I received the ticket about this problem.I even find exact place where it is. To more explanation there is a difference in obtaining property.  for example my code on affected slave: {{ PropertyResourceBundle.getBundle("com.sun.org.apache.xerces.internal.impl.msg.SAXMessages", Locale.US) }}  this return right bundle without problems. but calling (as it is done in by in SAXReader used by this plugin) SecuritySupport.getResourceBundle("com.sun.org.apache.xerces.internal.impl.msg.SAXMessages", new Locale("en", "US"));this throws exception MissingResourceException.It is very strange because SecuritySupport.getResourceBundle() calls the same code (PropertyResourceBundle.getBundle("com.sun.org.apache.xerces.internal.impl.msg.SAXMessages", Locale.US) ) bud under AccessController.doPrivileged():public static ResourceBundle getResourceBundle(final String bundle, final Locale locale) {return AccessController.doPrivileged(new PrivilegedAction() {public ResourceBundle run() {try {return PropertyResourceBundle.getBundle(bundle, locale);} catch (MissingResourceException e) {try {return PropertyResourceBundle.getBundle(bundle, new Locale("en", "US"));} catch (MissingResourceException e2) {throw new MissingResourceException("Could not load any resource bundle by " + bundle, bundle, "");}}}});}It seems that there is some difference in execution this code (despite it is the same). I will try to investigate what is different. That could be a way how to realized what is wrong. I think that it maybe will not be problem in plugin itself (bug in jdk or remoting or leaking some classes for master).Have any of us idea? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
 

[JIRA] [core] (JENKINS-18687) Intermittent failure whilst recording test results caused by java.util.MissingResourceException

[lvoty...@redhat.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lucie Votypkova commented on  JENKINS-18687 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Intermittent failure whilst recording test results caused by java.util.MissingResourceException  
 
 
 
 
 
 
 
 
 
 
I did a more investigation - I finally got the problem when it occurs - usually slave was restarted and fine when I received the ticket about this problem. I even find exact place where it is. To more explanation there is a difference in obtaining property.  
for example my code on affected slave: 
PropertyResourceBundle.getBundle("com.sun.org.apache.xerces.internal.impl.msg.SAXMessages", Locale.US)  
this return right bundle without problems.  
but calling (as it is done in by in SAXReader used by this plugin)  
SecuritySupport.getResourceBundle("com.sun.org.apache.xerces.internal.impl.msg.SAXMessages", new Locale("en", "US")); 
this throws exception MissingResourceException. 
It is very strange because SecuritySupport.getResourceBundle() calls the same code (PropertyResourceBundle.getBundle("com.sun.org.apache.xerces.internal.impl.msg.SAXMessages", Locale.US) ) bud under AccessController.doPrivileged(): 
public static ResourceBundle getResourceBundle(final String bundle, final Locale locale) { return AccessController.doPrivileged(new PrivilegedAction() { public ResourceBundle run() { try  { return PropertyResourceBundle.getBundle(bundle, locale); } 
 catch (MissingResourceException e) { try  { return PropertyResourceBundle.getBundle(bundle, new Locale("en", "US")); } 
 catch (MissingResourceException e2)  { throw new MissingResourceException( "Could not load any resource bundle by " + bundle, bundle, ""); } 
 } } }); } 
It seems that there is some difference in execution this code (despite it is the same). I will try to investigate what is different. That could be a way how to realized what is wrong. I think that it maybe will not be problem in plugin itself (bug in jdk or remoting or leaking some classes for master). Have any of us idea? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 

[JIRA] [zephyr-for-jira-test-management-plugin] (JENKINS-32801) Pipeline build step for Zephyr for Jira

[rec...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32801 
 
 
 
  Pipeline build step for Zephyr for Jira  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Component/s:
 
 workflow-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] [maven-plugin] (JENKINS-32635) SNAPSHOT trigger enhacements

[zherebtsova...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Zherebtsov resolved as Done 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Pull request https://github.com/jenkinsci/maven-plugin/pull/57 merged 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32635 
 
 
 
  SNAPSHOT trigger enhacements  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Zherebtsov 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Done 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32802) Can't load Update Center from FTP mirror

[m...@daniel-spilker.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Spilker created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32802 
 
 
 
  Can't load Update Center from FTP mirror  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 05/Feb/16 12:13 PM 
 
 
 

Environment:
 

 Jenkins 1.642  openjdk version "1.8.0_66-internal"  Ubuntu 15.10 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Daniel Spilker 
 
 
 
 
 
 
 
 
 
 
I get an IOException when trying to fetch the latest update center data. 

 

java.io.IOException: Could not find JSON in http://updates.jenkins-ci.org/update-center.json?id=default&version=1.642
	at hudson.model.DownloadService.loadJSON(DownloadService.java:170)
	at hudson.model.UpdateSite.updateDirectlyNow(UpdateSite.java:173)
	at hudson.PluginManager.doCheckUpdatesServer(PluginManager.java:959)
...
 

 
Trying wget on the same host to download the data from works fine: 

 

$ wget -v "http://updates.jenkins-ci.org/update-center.json?id=default&version=1.642"
--2016-02-05 12:08:23--  http://updates.

[JIRA] [multi-branch-project-plugin] (JENKINS-32255) Multi-branch multi-configuration projects

[jvp...@jvprat.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jordi Vilalta Prat commented on  JENKINS-32255 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Multi-branch multi-configuration projects  
 
 
 
 
 
 
 
 
 
 
I'm also interested on this. Would it be hard to implement? Just as a reference, integration with https://wiki.jenkins-ci.org/display/JENKINS/Matrix+Project+Plugin would be perfect. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32801) Pipeline build step for Zephyr for Jira

[ifernandezca...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ivan Fernandez Calvo created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32801 
 
 
 
  Pipeline build step for Zephyr for Jira  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 

Components:
 

 workflow-plugin, zephyr-for-jira-test-management-plugin 
 
 
 

Created:
 

 05/Feb/16 10:56 AM 
 
 
 

Labels:
 

 workflow 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Ivan Fernandez Calvo 
 
 
 
 
 
 
 
 
 
 
A way to run Zephyr from a pipeline. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 

[JIRA] [clearcase-ucm-plugin] (JENKINS-32800) Poll subscribe should show which baseline has not been tested (case 14218)

[m...@praqma.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mads Nielsen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32800 
 
 
 
  Poll subscribe should show which baseline has not been tested (case 14218)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mads Nielsen 
 
 
 

Summary:
 
 Poll subscribe should show which baseline has not been tested .  (case 14218) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [clearcase-ucm-plugin] (JENKINS-32800) Poll subscribe should show which baseline has not been tested.

[m...@praqma.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mads Nielsen created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32800 
 
 
 
  Poll subscribe should show which baseline has not been tested.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Praqma Support 
 
 
 

Components:
 

 clearcase-ucm-plugin 
 
 
 

Created:
 

 05/Feb/16 10:37 AM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Mads Nielsen 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are 

[JIRA] [matrix-combinations-parameter-plugin] (JENKINS-32799) Jenkins failed to generate new Multi-configuration build page when Combination Filter includes build parameter

[sstorozhe...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sergey Storozhenko updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32799 
 
 
 
  Jenkins failed to generate new Multi-configuration build page when Combination Filter includes build parameter  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sergey Storozhenko 
 
 
 

Attachment:
 
 Screen Shot 2016-02-05 at 13.24.44.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [matrix-combinations-parameter-plugin] (JENKINS-32799) Jenkins failed to generate new Multi-configuration build page when Combination Filter includes build parameter

[sstorozhe...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sergey Storozhenko created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32799 
 
 
 
  Jenkins failed to generate new Multi-configuration build page when Combination Filter includes build parameter  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 matrix-combinations-parameter-plugin 
 
 
 

Created:
 

 05/Feb/16 10:29 AM 
 
 
 

Environment:
 

 Debian 8.0, Jenkins 1.631, Matrix Project Plugin 1.6, Matrix Configuration Parameter Plugin 1.0.9 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Sergey Storozhenko 
 
 
 
 
 
 
 
 
 
 
I have a matrix project with a user-defined axis (multiple values) and label _expression_ (single value).  
In order to skip some test environments listed in a user-defined axis, I've added a Combination Filter: 

 

!(VERIFIER=="true" && (VM_NAME=="win2003x86" || VM_NAME=="win2003x64"))
 

 
, where: 
 

VERIFIER is a project Boolean parameter
 
  

[JIRA] [ec2-plugin] (JENKINS-32703) Unable to use LDAP accounts as remote user to connect slaves using EC2 plugin

[svmkph...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Murali Phani edited a comment on  JENKINS-32703 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unable to use LDAP accounts as remote user to connect slaves using EC2 plugin  
 
 
 
 
 
 
 
 
 
 Able to launch slave .But authentication issue remain there.Please find attached log  [^jenkins._auth.log]   
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ec2-plugin] (JENKINS-32703) Unable to use LDAP accounts as remote user to connect slaves using EC2 plugin

[svmkph...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Murali Phani updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32703 
 
 
 
  Unable to use LDAP accounts as remote user to connect slaves using EC2 plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Murali Phani 
 
 
 

Attachment:
 
 jenkins._auth.log 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ec2-plugin] (JENKINS-32703) Unable to use LDAP accounts as remote user to connect slaves using EC2 plugin

[svmkph...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Murali Phani commented on  JENKINS-32703 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unable to use LDAP accounts as remote user to connect slaves using EC2 plugin  
 
 
 
 
 
 
 
 
 
 
Able to launch slave .But authentication issue remain there.Please find attached log 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [packaging] (JENKINS-23273) RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}"

[o...@lenz.name (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Olaf Lenz commented on  JENKINS-23273 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}"  
 
 
 
 
 
 
 
 
 
 
As for the argument that we should support migration from hudson: the whole mechanism with the JENKINS_USER is somewhat broken, anyway. To be able to use it, you first have to create /etc/sysconfig/jenkins, as the chown happens in the RPM postinstall script.  If you edit the file and change the JENKINS_USER only after the installation and then try to start jenkins (e.g. via sudo /etc/init.d/jenkins start), it won't start, and it will not give a useful error message, as it cannot write its log or anything, as the paths are not chowned. 
So, from my POV, the whole mechanism is useful only for very few people, anyway, if it was useful at all. So I suggest: remove the mechanism, it will hurt nobody. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.

[zschi...@kombinat-berlin.de (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Zschille assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-10160 
 
 
 
  When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.  
 
 
 
 
 
 
 
 
 

Change By:
 
 David Zschille 
 
 
 

Assignee:
 
 David Zschille 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.

[zschi...@kombinat-berlin.de (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Zschille assigned an issue to David Zschille 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-10160 
 
 
 
  When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.  
 
 
 
 
 
 
 
 
 

Change By:
 
 David Zschille 
 
 
 

Assignee:
 
 David Zschille 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [_unsorted] (JENKINS-32796) Can't update plugins: incorrect checksum

[alexander.buchho...@qudosoft.de (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexander Buchholtz updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32796 
 
 
 
  Can't update plugins: incorrect checksum  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alexander Buchholtz 
 
 
 
 
 
 
 
 
 
 When trying to update to latest  plugin  version  (e.g.  v1.3.4 from v1.3.0 the following error is reported by Jenkins Update-Center:java.io.IOException: Downloaded file /var/lib/jenkins/plugins/dependency-check-jenkins-plugin.jpi.tmp does not match expected SHA-1, expected 'f2ncNlydUUSPrk6SoG255v+2kQU=', actual 'lZRJco4Ouv1j0AG4Aet7HadHg/Q=' at hudson.model.UpdateCenter.verifyChecksums(UpdateCenter.java:1307) at hudson.model.UpdateCenter.access$900(UpdateCenter.java:124) at hudson.model.UpdateCenter$InstallationJob.replace(UpdateCenter.java:1406) at hudson.model.UpdateCenter$UpdateCenterConfiguration.install(UpdateCenter.java:846) at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1186) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1364) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1161) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) at java.lang.Thread.run(Thread.java:745) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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,

[JIRA] [_unsorted] (JENKINS-32796) Can't update plugins: incorrect checksum

[alexander.buchho...@qudosoft.de (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexander Buchholtz updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32796 
 
 
 
  Can't update plugins: incorrect checksum  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alexander Buchholtz 
 
 
 

Summary:
 
 Can't update  to v1.3.4  plugins : incorrect checksum 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [_unsorted] (JENKINS-32796) Can't update plugins: incorrect checksum

[alexander.buchho...@qudosoft.de (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexander Buchholtz updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32796 
 
 
 
  Can't update plugins: incorrect checksum  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alexander Buchholtz 
 
 
 
 
 
 
 
 
 
 When trying to update to latest plugin version (e.g.  dependency-check-jenkins-plugin  v1.3.4 from v1.3.0  )  the following error is reported by Jenkins Update-Center:java.io.IOException: Downloaded file /var/lib/jenkins/plugins/dependency-check-jenkins-plugin.jpi.tmp does not match expected SHA-1, expected 'f2ncNlydUUSPrk6SoG255v+2kQU=', actual 'lZRJco4Ouv1j0AG4Aet7HadHg/Q=' at hudson.model.UpdateCenter.verifyChecksums(UpdateCenter.java:1307) at hudson.model.UpdateCenter.access$900(UpdateCenter.java:124) at hudson.model.UpdateCenter$InstallationJob.replace(UpdateCenter.java:1406) at hudson.model.UpdateCenter$UpdateCenterConfiguration.install(UpdateCenter.java:846) at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1186) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1364) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1161) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) at java.lang.Thread.run(Thread.java:745) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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...@g

[JIRA] [_unsorted] (JENKINS-32796) Can't update to v1.3.4: incorrect checksum

[alexander.buchho...@qudosoft.de (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexander Buchholtz updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32796 
 
 
 
  Can't update to v1.3.4: incorrect checksum  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alexander Buchholtz 
 
 
 

Component/s:
 
 _unsorted 
 
 
 

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] [core] (JENKINS-32796) Can't update to v1.3.4: incorrect checksum

[alexander.buchho...@qudosoft.de (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexander Buchholtz updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32796 
 
 
 
  Can't update to v1.3.4: incorrect checksum  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alexander Buchholtz 
 
 
 

Component/s:
 
 core 
 
 
 

Component/s:
 
 dependency-check-jenkins-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] [dependency-check-jenkins-plugin] (JENKINS-32796) Can't update to v1.3.4: incorrect checksum

[alexander.buchho...@qudosoft.de (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexander Buchholtz commented on  JENKINS-32796 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Can't update to v1.3.4: incorrect checksum  
 
 
 
 
 
 
 
 
 
 
I don't have the issue with "Check now". It completes without an error. Log file says "Obtained the latest update center data file for UpdateSource default". The error only occurs when attempting to update any plugin, so you are right it doesn't seem to be a plugin specific issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32797) Access to check for unprotected/never secured paths

[bryso...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bryson Gibbons commented on  JENKINS-32797 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Access to check for unprotected/never secured paths  
 
 
 
 
 
 
 
 
 
 
I am willing to create a pull request, if this seems reasonable. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [_unsorted] (JENKINS-32798) apt-get: Failed to fetch http://pkg.jenkins-ci.org

[zschi...@kombinat-berlin.de (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Zschille created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32798 
 
 
 
  apt-get: Failed to fetch http://pkg.jenkins-ci.org  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Oleg Nenashev 
 
 
 

Components:
 

 _unsorted 
 
 
 

Created:
 

 05/Feb/16 9:27 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 David Zschille 
 
 
 
 
 
 
 
 
 
 
I can not upgrade Jenkins: 

 

$ sudo apt-get upgrade jenkins
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be upgraded:
  jenkins
1 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 63.3 MB of archives.
After this operation, 342 kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Err http://pkg.jenkins-ci.org/debian-stable/ binary/ jenkins 1.642.1
  302  Found
Failed to fetch http://pkg.jenkins-ci.org/debian-stable/binary/jenkins_1.642.1_all.deb  302  Found
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
 

 
apt-get update or --fix-missing doesn't help. 
 
 
 
 
 
 
 
 
 
 
 
 
  

[JIRA] [core] (JENKINS-32797) Access to check for unprotected/never secured paths

[bryso...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bryson Gibbons created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32797 
 
 
 
  Access to check for unprotected/never secured paths  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 UnprotectedPatch.diff 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 05/Feb/16 9:26 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Bryson Gibbons 
 
 
 
 
 
 
 
 
 
 
Currently no method exists (that I could find) to allow authentication plugins working on top of Jenkins to test a path to see if it does not require authentication; Jenkins does it (in part, at least) using Jenkins.getTarget() (https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/model/Jenkins.java#L3875). This function does too much for some plugins, e.g. NegotiateSSO, because it first checks for read permissions. 
I propose breaking the functionality of Jenkins.getTarget() into several functions, allowing a plugin to access the checks for paths that shouldn't be protected. The attached diff file gives an example (diff base is commit e014700, on jenkinsci/jenkins). 
The other solutions that have been given to me so far involve maintaining a list of exceptions, which seems unwise to me. 
 
 
 
 

[JIRA] [active-choices-plugin] (JENKINS-32566) Render an AC Reactive reference as a functional Jenkins File Parameter

[brunodepau...@yahoo.com.br (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruno P. Kinoshita commented on  JENKINS-32566 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Render an AC Reactive reference as a functional Jenkins File Parameter  
 
 
 
 
 
 
 
 
 
 
The groovy script needs to have the name equals file, not value in this case. 

 

html='''
"file" type="file" jsonaware="true">
'''
return html
 

 
Furthermore, the plug-in was always, by default, returning a parameter value of type String. Now when you pass a key file in the JSON (it is all done automagically in Jenkins), the plug-in first checks for that and once it finds it, it returns a file definition parameter instead. 
Hopefully the old behaviour was not affected, but just to play safe, I won't release it immediately. 
Posting about new release to mailing list, which will require some testing in our testbed server with the snapshot, which will contain the fix for this issue. In case you find that it works there, just let me know and I will cut a new release. Might be a good if we add some notes to the Wiki about how to use file upload controllers with active choice 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] [active-choices-plugin] (JENKINS-32566) Render an AC Reactive reference as a functional Jenkins File Parameter

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32566 
 
 
 
  Render an AC Reactive reference as a functional Jenkins File Parameter  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

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] [active-choices-plugin] (JENKINS-32566) Render an AC Reactive reference as a functional Jenkins File Parameter

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-32566 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Render an AC Reactive reference as a functional Jenkins File Parameter  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Bruno P. Kinoshita Path: src/main/java/org/biouno/unochoice/AbstractUnoChoiceParameter.java http://jenkins-ci.org/commit/active-choices-plugin/10b9b24d468dfd36f62d88ded3ad7d816d16a75b Log: [FIXED JENKINS-32566] Return a FileParameterDefinition when JSON request for a HTML rendered parameter contains a file key 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [active-choices-plugin] (JENKINS-32566) Render an AC Reactive reference as a functional Jenkins File Parameter

[brunodepau...@yahoo.com.br (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruno P. Kinoshita stopped work on  JENKINS-32566 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Bruno P. Kinoshita 
 
 
 

Status:
 
 In Progress Open 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [dependency-check-jenkins-plugin] (JENKINS-32796) Can't update to v1.3.4: incorrect checksum

[zschi...@kombinat-berlin.de (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Zschille commented on  JENKINS-32796 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Can't update to v1.3.4: incorrect checksum  
 
 
 
 
 
 
 
 
 
 
I have this error also with every plugin in try to update: 

 

Git plugin  Failure
java.io.IOException: Downloaded file /var/lib/jenkins/plugins/git.jpi.tmp does not match expected SHA-1, expected 'lwiTe8A0PGiqYzaeKElzmefzY2Q=', actual 'anAU1+oliegyXOf0ZFTogzVOe7s='
	at hudson.model.UpdateCenter.verifyChecksums(UpdateCenter.java:1309)
	at hudson.model.UpdateCenter.access$900(UpdateCenter.java:124)
	at hudson.model.UpdateCenter$InstallationJob.replace(UpdateCenter.java:1408)
	at hudson.model.UpdateCenter$UpdateCenterConfiguration.install(UpdateCenter.java:846)
	at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1188)
	at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1366)
	at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1163)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110)
	at java.lang.Thread.run(Thread.java:745)
 

 
When i choose to "Check now" the update information, i get this error:  

 

java.io.IOException: Could not find JSON in http://updates.jenkins-ci.org/update-center.json?id=default&version=1.625.3
	at hudson.model.DownloadService.loadJSON(DownloadService.java:170)
	at hudson.model.UpdateSite.updateDirectlyNow(UpdateSite.java:173)
	at hudson.PluginManager.doCheckUpdatesServer(PluginManager.java:894)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
	at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:46)
	at org.kohsuke.stapler.Function$InterceptedFunction.invoke(Function.java:399)
	at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
	at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
	at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
	at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:183)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49)
	at org.eclipse.j

[JIRA] [artifactory-plugin] (JENKINS-29262) ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.com java.lang.NullPointerException

[swapnils...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 swapnil soor resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
It was pom.xml file issue only, incorrect parent dependency. Since it was working fine during CI build could not out the cause immediately & thought its plugin issue. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-29262 
 
 
 
  ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.com java.lang.NullPointerException  
 
 
 
 
 
 
 
 
 

Change By:
 
 swapnil soor 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Assignee:
 
 yossis swapnil soor 
 
 
 

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 sto

[JIRA] [artifactory-plugin] (JENKINS-29262) ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.com java.lang.NullPointerException

[swapnils...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 swapnil soor commented on  JENKINS-29262 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.com java.lang.NullPointerException  
 
 
 
 
 
 
 
 
 
 
Oh, It was some internal parent dependency issue, got the fix, but error was misleading. Normally it should point the pom error, which was the case. 
Anyways, it got fixed now, Thanks! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [dependency-check-jenkins-plugin] (JENKINS-32796) Can't update to v1.3.4: incorrect checksum

[alexander.buchho...@qudosoft.de (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexander Buchholtz created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32796 
 
 
 
  Can't update to v1.3.4: incorrect checksum  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 dependency-check-jenkins-plugin 
 
 
 

Created:
 

 05/Feb/16 8:53 AM 
 
 
 

Environment:
 

 v1.3.0 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Alexander Buchholtz 
 
 
 
 
 
 
 
 
 
 
When trying to update to latest version v1.3.4 from v1.3.0 the following error is reported by Jenkins Update-Center: 
java.io.IOException: Downloaded file /var/lib/jenkins/plugins/dependency-check-jenkins-plugin.jpi.tmp does not match expected SHA-1, expected 'f2ncNlydUUSPrk6SoG255v+2kQU=', actual 'lZRJco4Ouv1j0AG4Aet7HadHg/Q=' at hudson.model.UpdateCenter.verifyChecksums(UpdateCenter.java:1307) at hudson.model.UpdateCenter.access$900(UpdateCenter.java:124) at hudson.model.UpdateCenter$InstallationJob.replace(UpdateCenter.java:1406) at hudson.model.UpdateCenter$UpdateCenterConfiguration.install(UpdateCenter.java:846) at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1186) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1364) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1161) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at hudson.remoting.AtmostOneThreadExecutor$Wo