[JIRA] (JENKINS-60392) Allow environment variables with Bitbucket Server Integration Pipeline

2020-02-25 Thread bcov...@nycm.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruce Coveny edited a comment on  JENKINS-60392  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow environment variables with Bitbucket Server Integration Pipeline   
 

  
 
 
 
 

 
 [~mhenschke_atlassian]It appears using double quotes worked for the branch name but it does not appear to work for other variables like credentialsId and produces an error.  Please note values have been changed from hard-coded values for data sensitivity reasons.Example call:   {code:java}bbs_checkout branches: bbs_checkout branches:  [[name: "${env.BRANCH}"]],  credentialsId: "${env.CREDENTIALS_ID}",  id: 'id',  mirrorName: '',  projectName: 'project',  repositoryName: 'repo',  serverId: 'serverid'{code}Log output:      {noformat}[Pipeline] bbs_checkoutusing credential [proper-credential-id] > git.exe rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git.exe config remote.repo.url https://localhost:8443/scm/project/repo.git # timeout=10Fetching upstream changes from https://localhost:8443/scm/project/repo.git > git.exe --version # timeout=10using GIT_ASKPASS to set credentials Signon > git.exe fetch --tags --force --progress -- https://localhost:8443/scm/project/repo.git +refs/heads/*:refs/remotes/repo/* # timeout=10 > git.exe rev-parse "repo/*master^{commit}" # timeout=10 > git.exe rev-parse "develop^{commit}" # timeout=10[Pipeline] }Posting build status of FAILED to Bitbucket ServerERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.Finished: FAILURE{noformat}Taking out the "${env.CREDENTIALS_ID}" and changing to something like 'hardcoded-credential-id' works.This would work better if the payload configured in the Jenkins job could be injected as per issue JENKINS-60340 and not having to duplicate these values in the Jenkins job and in the Jenkinsfile.  We have different values for these based on different branches for access level information which is why we need to change the values around and not hard-code them in the Jenkinsfile.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 
   

[JIRA] (JENKINS-60392) Allow environment variables with Bitbucket Server Integration Pipeline

2020-02-25 Thread bcov...@nycm.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruce Coveny commented on  JENKINS-60392  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow environment variables with Bitbucket Server Integration Pipeline   
 

  
 
 
 
 

 
 Martin Henschke It appears using double quotes worked for the branch name but it does not appear to work for other variables like credentialsId and produces an error.  Please note values have been changed from hard-coded values for data sensitivity reasons. Example call:   

 

bbs_checkout branches: bbs_checkout branches:  [[name: "${env.BRANCH}"]],  credentialsId: "${env.CREDENTIALS_ID}",  id: 'id',  mirrorName: '',  projectName: 'project',  repositoryName: 'repo',  serverId: 'serverid'
 

 Log output:     

 
[Pipeline] bbs_checkout
using credential [proper-credential-id]
 > git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git.exe config remote.repo.url https://localhost:8443/scm/project/repo.git # timeout=10
Fetching upstream changes from https://localhost:8443/scm/project/repo.git
 > git.exe --version # timeout=10
using GIT_ASKPASS to set credentials Signon
 > git.exe fetch --tags --force --progress -- https://localhost:8443/scm/project/repo.git +refs/heads/*:refs/remotes/repo/* # timeout=10
 > git.exe rev-parse "repo/*master^{commit}" # timeout=10
 > git.exe rev-parse "develop^{commit}" # timeout=10
[Pipeline] }
Posting build status of FAILED to Bitbucket ServerERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.
Finished: FAILURE 

 Taking out the "${env.CREDENTIALS_ID}" and changing to something like 'hardcoded-credential-id' works. This would work better if the payload configured in the Jenkins job could be injected as per issue JENKINS-60340 and not having to duplicate these values in the Jenkins job and in the Jenkinsfile.  We have different values for these based on different branches for access level information which is why we need to change the values around and not hard-code them in the Jenkinsfile.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  

[JIRA] (JENKINS-60392) Allow environment variables with Bitbucket Server Integration Pipeline

2019-12-06 Thread bcov...@nycm.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruce Coveny created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60392  
 
 
  Allow environment variables with Bitbucket Server Integration Pipeline   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Kristy Hughes  
 
 
Components: 
 atlassian-bitbucket-server-integration-plugin  
 
 
Created: 
 2019-12-06 18:06  
 
 
Environment: 
 Jenkins 2.207  Bitbucket Server Integration 1.0.3  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Bruce Coveny  
 

  
 
 
 
 

 
 When creating a pipeline build none of the options allow environment variables. The documentation I found at https://jenkins.io/doc/pipeline/steps/atlassian-bitbucket-server-integration/ states that the branch name should be able to use environment variable, however, it doesn't appear to mark it up.   Hard Coded Example: branches: [[name: 'branchname']] Results: Produces a scan just on branch with name 'branchname'   Environment Example 1: branches: [[name: '${ENV_VARNAME}']] Result: Produces a scan of all branches in all the repoisotry   Environment Example 2: branches: [[name: '${env.ENV_VARNAME}']]  Result: Stack Exception     
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

[JIRA] (JENKINS-28576) WebSphere Crashes on Jenkins 1.612 and higher supporting Java 7 changes

2019-10-29 Thread bcov...@nycm.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruce Coveny closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 No longer run on WebSphere and use internal server to run.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-28576  
 
 
  WebSphere Crashes on Jenkins 1.612 and higher supporting Java 7 changes   
 

  
 
 
 
 

 
Change By: 
 Bruce Coveny  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this 

[JIRA] (JENKINS-30123) OutputStream encountered error during write

2019-10-29 Thread bcov...@nycm.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruce Coveny closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 No long run on WebSphere and use internal server for running.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-30123  
 
 
  OutputStream encountered error during write   
 

  
 
 
 
 

 
Change By: 
 Bruce Coveny  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

[JIRA] (JENKINS-30715) Disk Usage Plugin Crashes Java, Crashes WebSphere Server

2019-10-29 Thread bcov...@nycm.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruce Coveny closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-30715  
 
 
  Disk Usage Plugin Crashes Java, Crashes WebSphere Server
 

  
 
 
 
 

 
Change By: 
 Bruce Coveny  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.165327.1443610563000.4519.1572359520393%40Atlassian.JIRA.


[JIRA] (JENKINS-34406) Failed to Initialize Jenkins Incompatible Ant

2019-10-29 Thread bcov...@nycm.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruce Coveny closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34406  
 
 
  Failed to Initialize Jenkins Incompatible Ant   
 

  
 
 
 
 

 
Change By: 
 Bruce Coveny  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.169988.1461371437000.4486.1572359460821%40Atlassian.JIRA.


[JIRA] (JENKINS-34863) WebSphere Plugin Configure System Missing

2019-10-29 Thread bcov...@nycm.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruce Coveny closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34863  
 
 
  WebSphere Plugin Configure System Missing   
 

  
 
 
 
 

 
Change By: 
 Bruce Coveny  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170525.146343113.4483.1572359400303%40Atlassian.JIRA.


[JIRA] (JENKINS-59974) Windows Event - Git Credentials Manager - System.UriFormatException: Invalid URI: The hostname could not be parsed.

2019-10-29 Thread bcov...@nycm.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruce Coveny updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59974  
 
 
  Windows Event - Git Credentials Manager - System.UriFormatException: Invalid URI: The hostname could not be parsed.   
 

  
 
 
 
 

 
Change By: 
 Bruce Coveny  
 

  
 
 
 
 

 
 Receive Windows events in viewer for the following:System.UriFormatException: Invalid URI: The hostname could not be parsed. at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind) at System.UriBuilder.get_Uri() at Microsoft.Alm.Cli.OperationArguments.CreateTargetUri() at Microsoft.Alm.Cli.OperationArguments..ctor(Stream readableStream) *at Microsoft.Alm.Cli.Program.Store()* at Microsoft.Alm.Cli.Program.Main(String[] args) System.UriFormatException: Invalid URI: The hostname could not be parsed. at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind) at System.UriBuilder.get_Uri() at Microsoft.Alm.Cli.OperationArguments.CreateTargetUri() at Microsoft.Alm.Cli.OperationArguments..ctor(Stream readableStream) *at Microsoft.Alm.Cli.Program.Get()* at Microsoft.Alm.Cli.Program.Main(String[] args) The only differences between the two events is one is a "Get()" and one is a "Store()".Have confirmed coming from Jenkins as stopping Jenkins the events stop and starting Jenkins back up the events start occurring again.I do not see anything in the Jenkins logs to point to potential issue.I found 3 jobs which may have been incorrect but have changed and corrected those issues but events still occur.  In one environment they occur almost every minute and several of them at a time.I am not saying this is a bug but was wondering:   * Has anyone seen this?   * Anyway to tie the Windows Event to a Jenkins Job, Polling Event, or other?   * Anyway to pump out additional logging to find out where issue is coming from in Jenkins?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  

[JIRA] (JENKINS-59974) Windows Event - Git Credentials Manager - System.UriFormatException: Invalid URI: The hostname could not be parsed.

2019-10-29 Thread bcov...@nycm.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruce Coveny updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59974  
 
 
  Windows Event - Git Credentials Manager - System.UriFormatException: Invalid URI: The hostname could not be parsed.   
 

  
 
 
 
 

 
Change By: 
 Bruce Coveny  
 

  
 
 
 
 

 
 Receive  windows  Windows  events in viewer for the following:System.UriFormatException: Invalid URI: The hostname could not be parsed. at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind) at System.UriBuilder.get_Uri() at Microsoft.Alm.Cli.OperationArguments.CreateTargetUri() at Microsoft.Alm.Cli.OperationArguments..ctor(Stream readableStream) *at Microsoft.Alm.Cli.Program.Store()* at Microsoft.Alm.Cli.Program.Main(String[] args) System.UriFormatException: Invalid URI: The hostname could not be parsed. at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind) at System.UriBuilder.get_Uri() at Microsoft.Alm.Cli.OperationArguments.CreateTargetUri() at Microsoft.Alm.Cli.OperationArguments..ctor(Stream readableStream) *at Microsoft.Alm.Cli.Program.Get()* at Microsoft.Alm.Cli.Program.Main(String[] args)     The only differences between the two events is one is a "Get()" and one is a "Store()".Have confirmed coming from Jenkins as stopping Jenkins the  event  events  stop and starting Jenkins back up the events start occurring again.I do not see anything in the Jenkins logs to point to potential issue.I found 3 jobs which may have been incorrect but have changed and corrected those issues but events still occur.  In one environment they occur almost every minute and several of them at a time.I am not saying this is a bug but was wondering:Has anyone seen this?Anyway to tie the Windows Event to a Jenkins Job, Polling Event, or other?Anyway to pump out additional logging to find out where issue is coming from in Jenkins?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
   

[JIRA] (JENKINS-59974) Windows Event - Git Credentials Manager - System.UriFormatException: Invalid URI: The hostname could not be parsed.

2019-10-29 Thread bcov...@nycm.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruce Coveny created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59974  
 
 
  Windows Event - Git Credentials Manager - System.UriFormatException: Invalid URI: The hostname could not be parsed.   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Mark Waite  
 
 
Components: 
 git-plugin  
 
 
Created: 
 2019-10-29 14:10  
 
 
Environment: 
 Windows 2012R2  Jenkins 2.202  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Bruce Coveny  
 

  
 
 
 
 

 
 Receive windows events in viewer for the following: System.UriFormatException: Invalid URI: The hostname could not be parsed. at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind) at System.UriBuilder.get_Uri() at Microsoft.Alm.Cli.OperationArguments.CreateTargetUri() at Microsoft.Alm.Cli.OperationArguments..ctor(Stream readableStream) at Microsoft.Alm.Cli.Program.Store() at Microsoft.Alm.Cli.Program.Main(String[] args)   System.UriFormatException: Invalid URI: The hostname could not be parsed. at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind) at System.UriBuilder.get_Uri() at Microsoft.Alm.Cli.OperationArguments.CreateTargetUri() at Microsoft.Alm.Cli.OperationArguments..ctor(Stream readableStream) at Microsoft.Alm.Cli.Program.Get() at Microsoft.Alm.Cli.Program.Main(String[] args) The only differences between the two events is one is a "Get()" and one is a "Store()". Have confirmed coming from Jenkins as stopping Jenkins the event stop and starting Jenkins back up the events start occurring again. I do not see anything in the Jenkins logs to point to potential issue. I found 3 jobs which may have been incorrect but have changed and corrected those issues but events still occur.  In one environment they occur almost every minute and several of them at a time. I am not saying this is a bug but was wondering: Has anyone seen this? Anyway to tie the Windows Event to a 

[JIRA] (JENKINS-30123) OutputStream encountered error during write

2016-07-25 Thread bcov...@nycm.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruce Coveny commented on  JENKINS-30123  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: OutputStream encountered error during write   
 

  
 
 
 
 

 
 This still occurs in version 2.14 is there anyway we could find out why these appear in the log and help to try and remedy the situation? Attached is an updated stack trace in case code changed: [7/25/16 0:00:14:232 EDT] 007d ServletWrappe E com.ibm.ws.webcontainer.servlet.ServletWrapper service SRVE0014E: Uncaught service() exception root cause Stapler: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: wsjar:file:/C:/Program%20Files%20(x86)/%DIRREMOVED%/jenkins_war.ear/jenkins.war/WEB-INF/lib/jenkins-core-2.14.jar!/hudson/model/View/index.jelly:42:43:  org.apache.commons.jelly.JellyTagException: wsjar:file:/C:/Program%20Files%20(x86)/%DIRREMOVED%/jenkins_war.ear/jenkins.war/WEB-INF/lib/jenkins-core-2.14.jar!/lib/hudson/buildHealth.jelly:56:56:  OutputStream encountered error during write at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:735) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:813) 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:668) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1232) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:781) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:480) at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:136) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:97) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:198) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:176) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:99) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at 

[JIRA] (JENKINS-34863) WebSphere Plugin Configure System Missing

2016-06-29 Thread bcov...@nycm.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruce Coveny commented on  JENKINS-34863  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: WebSphere Plugin Configure System Missing   
 

  
 
 
 
 

 
 Hi Daniel,  Not to be a pain but is this documented somewhere? I went back through all the what's news for the change log and also the overview of Jenkins 2.0. Something like this I would have thought would have been a bigger announcement since all configuration like this was done in one spot before. Thank you for the information and I do see where that information can be found and changed now.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-34794) Jenkins doesn't start because of NPE

2016-06-14 Thread bcov...@nycm.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruce Coveny commented on  JENKINS-34794  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins doesn't start because of NPE   
 

  
 
 
 
 

 
 Last night we updated to Jenkins 2.9 from 2.8 and also the monitoring plugin was updated from 1.57 to 1.59. We are no experiencing this issue and had to downgrade the plugin. When will this be released as it is marked as resolved.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-34863) WebSphere Plugin Configure System Missing

2016-05-17 Thread bcov...@nycm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34863 
 
 
 
  WebSphere Plugin Configure System Missing  
 
 
 
 
 
 
 
 
 

Change By:
 
 Bruce Coveny 
 
 
 
 
 
 
 
 
 
 Since the upgrade to Jenkins 2.0 - 2.4 the configuration setup for the WAS Builder Plugin does not show up in the Manage Jenkins -> Configure System.  In Jenkins 1.xxx you would go there to configure the server names.It looks like the information is stored in a file in the home directory by the  name  filename  of com.michelin.cio.hudson.plugins.wasbuilder.WASInstallation.xml  You can manually modify this file and the information will only show up if you restart the Jenkins instance.  The configuration doesn't refresh if you reload the configuration from disk.  Also if the password is different than another server you cannot create the password encryption manually. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34863) WebSphere Plugin Configure System Missing

2016-05-16 Thread bcov...@nycm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34863 
 
 
 
  WebSphere Plugin Configure System Missing  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Daniel Petisme 
 
 
 

Components:
 

 core, was-builder-plugin 
 
 
 

Created:
 

 2016/May/16 8:38 PM 
 
 
 

Environment:
 

 JENKINS WAR VERSION 2.04   WINDOWS SERVER 2008 R2 ENTERPRISE   AMD OPTERON(TM) PROCESSOR 6136 2.4 GHZ (4 PROCESSORS)   6.0 GB RAM   64-BIT OPERATION SYSTEM   WEBSPHERE APPLICATION SERVER 8.5.5.9   JAVA 1.7.1  WAS BUILDER PLUGIN 1.6.1 
 
 
 

Labels:
 

 was-builder-plugin configuration 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Bruce Coveny 
 
 
 
 
 
 
 
 
 
 
Since the upgrade to Jenkins 2.0 - 2.4 the configuration setup for the WAS Builder Plugin does not show up in the Manage Jenkins -> Configure System. In Jenkins 1.xxx you would go there to configure the server names. 
It looks like the information is stored in a file in the home directory by the name of com.michelin.cio.hudson.plugins.wasbuilder.WASInstallation.xml  
You can manually modify this file and the information will 

[JIRA] [core] (JENKINS-34406) Failed to Initialize Jenkins Incompatible Ant

2016-04-23 Thread bcov...@nycm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny commented on  JENKINS-34406 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Failed to Initialize Jenkins Incompatible Ant  
 
 
 
 
 
 
 
 
 
 
Hi Daniel, 
I had issues installing the new war overtop of the war already installed. In doing so I had to uninstall and reinstall the war file. In doing so I missed the step that the classloader on the war needed to be change to "Classes loaded with local class loader first (parent last)" and "Single class loader for application". Both of these needed to be applied so that the server looked at the Ant instance which Jenkins has bundled in it. I found additional information on the Wiki site https://wiki.jenkins-ci.org/display/JENKINS/IBM+WebSphere as well as this post on Stack Overflow http://stackoverflow.com/questions/6471815/websphere-6-1-hudson-ant  
So this was a known issue that I overlooked and I apologize for any confusion. 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34406) Failed to Initialize Jenkins Incompatible Ant

2016-04-23 Thread bcov...@nycm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34406 
 
 
 
  Failed to Initialize Jenkins Incompatible Ant  
 
 
 
 
 
 
 
 
 

Change By:
 
 Bruce Coveny 
 
 
 

Attachment:
 
 screenshot-1.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] [core] (JENKINS-34406) Failed to Initialize Jenkins Incompatible Ant

2016-04-22 Thread bcov...@nycm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34406 
 
 
 
  Failed to Initialize Jenkins Incompatible Ant  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/Apr/23 12:30 AM 
 
 
 

Environment:
 

 JENKINS WAR VERSION 2.0   WINDOWS SERVER 2008 R2 ENTERPRISE   AMD OPTERON(TM) PROCESSOR 6136 2.4 GHZ (4 PROCESSORS)   6.0 GB RAM   64-BIT OPERATION SYSTEM   WEBSPHERE APPLICATION SERVER 8.5.5.8   JAVA 1.7.1  
 
 
 

Labels:
 

 jenkins2.0 ant 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Bruce Coveny 
 
 
 
 
 
 
 
 
 
 
Upgraded to version 2.0 of Jenkins. Upon restarting server Jenkins fails to initialize saying an incompatible Ant version loaded. 
[4/22/16 20:20:51:658 EDT] 008f BootFailure E Failed to initialize Jenkins hudson.util.IncompatibleAntVersionDetected: Incompatible Ant loaded from bundleresource://130.fwk2046797665:4/org/apache/tools/ant/types/FileSet.class at hudson.WebAppMain.contextInitialized(WebAppMain.java:180) at 

[JIRA] [core] (JENKINS-30123) OutputStream encountered error during write

2015-11-24 Thread bcov...@nycm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30123 
 
 
 
  OutputStream encountered error during write  
 
 
 
 
 
 
 
 
 

Change By:
 
 Bruce Coveny 
 
 
 
 
 
 
 
 
 
 Getting errors in the  system out log  for a few versions now.  Doesn't seem to impact the viewing of the pages but sometimes pages load slower than normal and the  follow  following  stack  traces are  trace is  shown in the  server  log.{panel:title=Stack Trace}[8/25/15 7:25:02:027 EDT] 0076 webappE com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[Stapler]: org.apache.commons.jelly.JellyTagException: wsjar:file:/%DIRREMOVE%/jenkins_war.ear/jenkins.war/WEB-INF/lib/jenkins-core-1.626.jar!/lib/layout/layout.jelly:81:26:  OutputStream encountered error during write at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:95) 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 hudson.init.impl.InstallUncaughtExceptionHandler$1.reportException(InstallUncaughtExceptionHandler.java:27) at org.kohsuke.stapler.compression.CompressionFilter.reportException(CompressionFilter.java:77) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:55) at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:967) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1107) at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3923) at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1006) at 

[JIRA] [parameterized-trigger-plugin] (JENKINS-17460) Error occurs viewing build history on some builds

2015-10-27 Thread bcov...@nycm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-17460 
 
 
 
  Error occurs viewing build history on some builds  
 
 
 
 
 
 
 
 
 

Change By:
 
 Bruce Coveny 
 
 
 

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] [active-directory-plugin] (JENKINS-17718) Active Directory Plugin Fails

2015-10-27 Thread bcov...@nycm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny closed an issue as Duplicate 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-17718 
 
 
 
  Active Directory Plugin Fails  
 
 
 
 
 
 
 
 
 

Change By:
 
 Bruce Coveny 
 
 
 

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] [sidebar-link-plugin] (JENKINS-18887) Alllow links to open in new window/tab

2015-10-27 Thread bcov...@nycm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny closed an issue as Duplicate 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-18887 
 
 
 
  Alllow links to open in new window/tab  
 
 
 
 
 
 
 
 
 

Change By:
 
 Bruce Coveny 
 
 
 

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-19073) Edit View - Regular Expression - Broken

2015-10-27 Thread bcov...@nycm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-19073 
 
 
 
  Edit View - Regular _expression_ - Broken  
 
 
 
 
 
 
 
 
 

Change By:
 
 Bruce Coveny 
 
 
 

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-25337) Jenkins fails to start

2015-10-27 Thread bcov...@nycm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny closed an issue as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-25337 
 
 
 
  Jenkins fails to start  
 
 
 
 
 
 
 
 
 

Change By:
 
 Bruce Coveny 
 
 
 

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] [cli] (JENKINS-25338) list-jobs cli

2015-10-27 Thread bcov...@nycm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-25338 
 
 
 
  list-jobs cli  
 
 
 
 
 
 
 
 
 

Change By:
 
 Bruce Coveny 
 
 
 

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] [publish-over-ssh-plugin] (JENKINS-30922) Publish Over SSH Plugin fails to load after updating to 1.633

2015-10-27 Thread bcov...@nycm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny closed an issue as Duplicate 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30922 
 
 
 
  Publish Over SSH Plugin fails to load after updating to 1.633  
 
 
 
 
 
 
 
 
 

Change By:
 
 Bruce Coveny 
 
 
 

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] [artifactdeployer-plugin] (JENKINS-23313) Overwrite Files or only cleanup files to be copied to remote directory

2015-10-27 Thread bcov...@nycm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny closed an issue as Won't Fix 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-23313 
 
 
 
  Overwrite Files or only cleanup files to be copied to remote directory  
 
 
 
 
 
 
 
 
 

Change By:
 
 Bruce Coveny 
 
 
 

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] [ssh-plugin] (JENKINS-30912) SSH Plugin fails to add and connect to remote host site

2015-10-14 Thread bcov...@nycm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny commented on  JENKINS-30912 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: SSH Plugin fails to add and connect to remote host site  
 
 
 
 
 
 
 
 
 
 
Seems to be related to my issue where the publish over ssh plugin fails to load on upon starting Jenkins. Thus going to configure a build or configure Jenkins it generates this 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] [publish-over-ssh-plugin] (JENKINS-30922) Publish Over SSH Plugin fails to load after updating to 1.633

2015-10-13 Thread bcov...@nycm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30922 
 
 
 
  Publish Over SSH Plugin fails to load after updating to 1.633  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 bap 
 
 
 

Components:
 

 publish-over-ssh-plugin 
 
 
 

Created:
 

 13/Oct/15 11:12 AM 
 
 
 

Environment:
 

 JENKINS WAR VERSION 1.626  WINDOWS SERVER 2008 R2 ENTERPRISE  AMD OPTERON(TM) PROCESSOR 6136 2.4 GHZ (2 PROCESSORS)  6.0 GB RAM  64-BIT OPERATION SYSTEM  WEBSPHERE APPLICATION SERVER 8.5.5.6  JAVA 1.7.1  publish-over-ssh 1.13 
 
 
 

Labels:
 

 publish-over-ssh 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Bruce Coveny 
 
 
 
 
 
 
 
 
 
 
The plugin fails to load with changes in 1.633 version of Jenkins. Reverting back to .1632 the plugin loads without any issue. 
10/12/15 21:13:03:702 EDT] 0067 ExtensionFind W Failed to instantiate Key[type=jenkins.plugins.publish_over_ssh.BapSshPublisherPlugin$Descriptor, annotation=[none]]; skipping this component com.google.inject.ProvisionException: Guice provision errors: 
1) Error injecting constructor, java.lang.RuntimeException: 

[JIRA] [disk-usage-plugin] (JENKINS-30715) Disk Usage Plugin Crashes Java, Crashes WebSphere Server

2015-10-06 Thread bcov...@nycm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny commented on  JENKINS-30715 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Disk Usage Plugin Crashes Java, Crashes WebSphere Server   
 
 
 
 
 
 
 
 
 
 
If you could provide ways of giving more information I am happy to do so. However, this causes a Java crash and it is a prompt on the server stating that Java is not responding. You than have to answer to continue waiting or end program. The information provided is from the event monitor. There is no Java dump or even a core dump from WebSphere that could be provided. The logging on the server all together just stops. We disabled the plugin and after a period of time we had the same issue. We uninstalled in the plugin and the server has been stable since. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [disk-usage-plugin] (JENKINS-30715) Disk Usage Plugin Crashes Java, Crashes WebSphere Server

2015-10-02 Thread bcov...@nycm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30715 
 
 
 
  Disk Usage Plugin Crashes Java, Crashes WebSphere Server   
 
 
 
 
 
 
 
 
 

Change By:
 
 Bruce Coveny 
 
 
 

Priority:
 
 Critical Blocker 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [disk-usage-plugin] (JENKINS-30715) Disk Usage Plugin Crashes Java, Crashes WebSphere Server

2015-10-02 Thread bcov...@nycm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30715 
 
 
 
  Disk Usage Plugin Crashes Java, Crashes WebSphere Server   
 
 
 
 
 
 
 
 
 

Change By:
 
 Bruce Coveny 
 
 
 

Labels:
 
 crash performance 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [disk-usage-plugin] (JENKINS-30715) Disk Usage Plugin Crashes Java, Crashes WebSphere Server

2015-10-02 Thread bcov...@nycm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny commented on  JENKINS-30715 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Disk Usage Plugin Crashes Java, Crashes WebSphere Server   
 
 
 
 
 
 
 
 
 
 
Downgraded to 0.26 from 0.27 server still crashed, we don't fully rely on this plugin so disabled it all together, server has been stable. Also have noticed on another Jenkins instance that the plugin seems to be out of control lately. within 4 seconds it polled the same project and build id 11 times! 
[10/2/15 9:23:04:222 EDT] 2088 SystemOut O create build disk usage for build [JOBNAME] #14345 of project [JOBNAME]  [10/2/15 9:23:04:222 EDT] 2088 SystemOut O information Id 14345 number 14345 size 0 [10/2/15 9:23:04:222 EDT] 2088 SystemOut O create build disk usage for build [JOBNAME] #14345 of project [JOBNAME]  [10/2/15 9:23:04:222 EDT] 2088 SystemOut O information Id 14345 number 14345 size 0 [10/2/15 9:23:04:222 EDT] 2088 SystemOut O create build disk usage for build [JOBNAME] #14345 of project [JOBNAME]  [10/2/15 9:23:04:222 EDT] 2088 SystemOut O information Id 14345 number 14345 size 0 [10/2/15 9:23:04:222 EDT] 2088 SystemOut O create build disk usage for build [JOBNAME] #14345 of project [JOBNAME]  [10/2/15 9:23:04:222 EDT] 2088 SystemOut O information Id 14345 number 14345 size 0 [10/2/15 9:23:08:185 EDT] 2088 SystemOut O create build disk usage for build [JOBNAME] #14345 of project [JOBNAME]  [10/2/15 9:23:08:185 EDT] 2088 SystemOut O information Id 14345 number 14345 size 0 [10/2/15 9:23:08:185 EDT] 2088 SystemOut O create build disk usage for build [JOBNAME] #14345 of project [JOBNAME]  [10/2/15 9:23:08:185 EDT] 2088 SystemOut O information Id 14345 number 14345 size 0 [10/2/15 9:23:08:185 EDT] 2088 SystemOut O create build disk usage for build [JOBNAME] #14345 of project [JOBNAME]  [10/2/15 9:23:08:185 EDT] 2088 SystemOut O information Id 14345 number 14345 size 0 [10/2/15 9:23:08:185 EDT] 2088 SystemOut O create build disk usage for build [JOBNAME] #14345 of project [JOBNAME]  [10/2/15 9:23:08:185 EDT] 2088 SystemOut O information Id 14345 number 14345 size 0 [10/2/15 9:23:08:185 EDT] 2088 SystemOut O create build disk usage for build [JOBNAME] #14345 of project [JOBNAME]  [10/2/15 9:23:08:185 EDT] 2088 SystemOut O information Id 14345 number 14345 size 0 [10/2/15 9:23:08:185 EDT] 2088 SystemOut O create build disk usage for build [JOBNAME] #14345 of project [JOBNAME]  [10/2/15 9:23:08:185 EDT] 2088 SystemOut O information Id 14345 number 14345 size 0 [10/2/15 9:23:08:185 EDT] 2088 SystemOut O create build disk usage for build [JOBNAME] #14345 of project [JOBNAME]  [10/2/15 9:23:08:185 EDT] 2088 SystemOut O information Id 14345 number 14345 size 0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
  

[JIRA] [disk-usage-plugin] (JENKINS-30715) Disk Usage Plugin Crashes Java, Crashes WebSphere Server

2015-10-02 Thread bcov...@nycm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30715 
 
 
 
  Disk Usage Plugin Crashes Java, Crashes WebSphere Server   
 
 
 
 
 
 
 
 
 

Change By:
 
 Bruce Coveny 
 
 
 

Priority:
 
 Blocker Critical 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [disk-usage-plugin] (JENKINS-30715) Disk Usage Plugin Crashes Java, Crashes WebSphere Server

2015-10-02 Thread bcov...@nycm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30715 
 
 
 
  Disk Usage Plugin Crashes Java, Crashes WebSphere Server   
 
 
 
 
 
 
 
 
 

Change By:
 
 Bruce Coveny 
 
 
 

Priority:
 
 Critical Blocker 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-30123) OutputStream encountered error during write

2015-10-02 Thread bcov...@nycm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30123 
 
 
 
  OutputStream encountered error during write  
 
 
 
 
 
 
 
 
 

Change By:
 
 Bruce Coveny 
 
 
 

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] [disk-usage-plugin] (JENKINS-30715) Disk Usage Plugin Crashes Java, Crashes WebSphere Server

2015-09-30 Thread bcov...@nycm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30715 
 
 
 
  Disk Usage Plugin Crashes Java, Crashes WebSphere Server   
 
 
 
 
 
 
 
 
 

Change By:
 
 Bruce Coveny 
 
 
 

Environment:
 
 JENKINS WAR VERSION 1.626 WINDOWS SERVER 2008 R2 ENTERPRISE AMD OPTERON(TM) PROCESSOR 6136 2.4 GHZ (2 PROCESSORS) 6.0 GB RAM 64-BIT OPERATION SYSTEM WEBSPHERE APPLICATION SERVER 8.5.5.6 JAVA 1.7.1 disk-usage-plugin 0.27 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [disk-usage-plugin] (JENKINS-30715) Disk Usage Plugin Crashes Java, Crashes WebSphere Server

2015-09-30 Thread bcov...@nycm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30715 
 
 
 
  Disk Usage Plugin Crashes Java, Crashes WebSphere Server   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Lucie Votypkova 
 
 
 

Components:
 

 disk-usage-plugin 
 
 
 

Created:
 

 30/Sep/15 10:56 AM 
 
 
 

Environment:
 

 JENKINS WAR VERSION 1.626  WINDOWS SERVER 2008 R2 ENTERPRISE  AMD OPTERON(TM) PROCESSOR 6136 2.4 GHZ (2 PROCESSORS)  6.0 GB RAM  64-BIT OPERATION SYSTEM  WEBSPHERE APPLICATION SERVER 8.5.5.6  JAVA 1.7.1 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Bruce Coveny 
 
 
 
 
 
 
 
 
 
 
Since the last plugin up the server has crashed 3 out 6 days. The crash is shown as a prompt on the server saying that Java has stopped running. The disk-usage plugin was the only update that has been done to the server.  
Log Name: Application Source: Application Error Date: 9/29/2015 11:16:55 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: [COMPUTERNAME] Description: Faulting application name: java.exe, version: 7.0.0.0, time stamp: 0x552cec04 Faulting module name: ntdll.dll, version: 6.1.7601.18933, time stamp: 0x55a6a196 Exception code: 0xc0fd Fault offset: 0x000510a1 Faulting process id: 0x36c Faulting application start time: 0x01d0fb244f4c8870 Faulting application path: %WEBSPHERE_DIR%\AppServer\java_1.7.1_64\bin\java.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 

[JIRA] [core] (JENKINS-30123) OutputStream encountered error during write

2015-08-25 Thread bcov...@nycm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-30123 
 
 
 
  OutputStream encountered error during write  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 25/Aug/15 11:36 AM 
 
 
 

Environment:
 

 JENKINS WAR VERSION 1.626  WINDOWS SERVER 2008 R2 ENTERPRISE  AMD OPTERON(TM) PROCESSOR 6136 2.4 GHZ (2 PROCESSORS)  6.0 GB RAM  64-BIT OPERATION SYSTEM  WEBSPHERE APPLICATION SERVER 8.5.5.6  JAVA 1.7.1 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Bruce Coveny 
 
 
 
 
 
 
 
 
 
 
Getting errors in the for a few versions now. Doesn't seem to impact the viewing of the pages but sometimes pages load slower than normal and the follow stack traces are shown in the server log. 


My title

 
[8/25/15 7:25:02:027 EDT] 0076 webapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[Stapler]: org.apache.commons.jelly.JellyTagException: wsjar:file:/%DIRREMOVE%/jenkins_war.ear/jenkins.war/WEB-INF/lib/jenkins-core-1.626.jar!/lib/layout/layout.jelly:81:26: x:doctype OutputStream encountered error during write at 

[JIRA] [core] (JENKINS-30123) OutputStream encountered error during write

2015-08-25 Thread bcov...@nycm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-30123 
 
 
 
  OutputStream encountered error during write  
 
 
 
 
 
 
 
 
 

Change By:
 
 Bruce Coveny 
 
 
 
 
 
 
 
 
 
 Gettingerrorsintheforafewversionsnow.Doesn'tseemtoimpacttheviewingofthepagesbutsometimespagesloadslowerthannormalandthefollowstacktracesareshownintheserverlog.{panel:title= Mytitle StackTrace }[8/25/157:25:02:027EDT]0076webappEcom.ibm.ws.webcontainer.webapp.WebApplogServletErrorSRVE0293E:[ServletError]-[Stapler]:org.apache.commons.jelly.JellyTagException:wsjar:file:/%DIRREMOVE%/jenkins_war.ear/jenkins.war/WEB-INF/lib/jenkins-core-1.626.jar!/lib/layout/layout.jelly:81:26:x:doctypeOutputStreamencounterederrorduringwrite atorg.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) atorg.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) atorg.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) atorg.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) atorg.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) atorg.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) atorg.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:95) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:876) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:649) athudson.init.impl.InstallUncaughtExceptionHandler$1.reportException(InstallUncaughtExceptionHandler.java:27) atorg.kohsuke.stapler.compression.CompressionFilter.reportException(CompressionFilter.java:77) atorg.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:55) atcom.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195) atcom.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91) athudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) atcom.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195) atcom.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91) atorg.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) atcom.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195) atcom.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91) atcom.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:967) atcom.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1107) atcom.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3923) atcom.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304) atcom.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1006) atcom.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1662) atcom.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:200) 

[JIRA] [active-directory-plugin] (JENKINS-28576) WebSphere Crashes on Jenkins 1.612 and higher supporting Java 7 changes

2015-07-24 Thread bcov...@nycm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny commented on  JENKINS-28576 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: WebSphere Crashes on Jenkins 1.612 and higher supporting Java 7 changes  
 
 
 
 
 
 
 
 
 
 
Removing the active directory settings made the server stable and not crash. It took some time to get the configuration setup for the LDAP plugin. We have successfully switched to the LDAP Plugin and the server is up and stable under JDK 1.7. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-28576) WebSphere Crashes on Jenkins 1.612 and higher supporting Java 7 changes

2015-06-06 Thread bcov...@nycm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny commented on  JENKINS-28576 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: WebSphere Crashes on Jenkins 1.612 and higher supporting Java 7 changes  
 
 
 
 
 
 
 
 
 
 
Yes we do use active directory plugin. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [core] (JENKINS-28576) WebSphere Crashes on Jenkins 1.612 and higher supporting Java 7 changes

2015-05-26 Thread bcov...@nycm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Coveny created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-28576 
 
 
 
  WebSphere Crashes on Jenkins 1.612 and higher supporting Java 7 changes  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 26/May/15 1:18 PM 
 
 
 

Environment:
 

 JENKINS WAR VERSION 1.612 - 1.615  WINDOWS SERVER 2008 R2 ENTERPRISE  AMD OPTERON(TM) PROCESSOR 6136 2.4 GHZ (2 PROCESSORS)  4.0 GB RAM  64-BIT OPERATION SYSTEM  WEBSPHERE APPLICATION SERVER 8.5.5.5  JAVA 1.7.1 
 
 
 

Labels:
 

 com4j 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Bruce Coveny 
 
 
 
 
 
 
 
 
 
 
WebSphere crashes when attempting to use newer versions of Jenkins built on Java 7. We have updated to all the latest patches of WebSphere 8.5.5.5 and to the newly released IBM JDK 1.7.1. IBM Support states they have seen similar things with com4j corruption. Is it possible for you to look into what IBM states? 
Here is IBM's last email. 
-- I have found a similar pattern of corruption like in the old PMRs which  was due 

[JIRA] [core] (JENKINS-25337) Jenkins fails to start

2014-10-28 Thread bcov...@nycm.com (JIRA)














































Bruce Coveny
 created  JENKINS-25337


Jenkins fails to start















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


28/Oct/14 11:21 AM



Description:


After updating to version 1.586 the Jenkins application fails to load with stack trace of the following:

10/28/14 7:10:57:152 EDT 00a0 SystemErr R Exception in thread "Jenkins initialization thread" java.lang.NoClassDefFoundError: hudson.util.HudsonFailedToLoad
10/28/14 7:10:57:152 EDT 00a0 SystemErr R 	at hudson.WebAppMain$3.run(WebAppMain.java:234)
10/28/14 7:10:57:152 EDT 00a0 SystemErr R Caused by: java.lang.ClassNotFoundException: hudson.util.HudsonFailedToLoad
10/28/14 7:10:57:152 EDT 00a0 SystemErr R 	at java.net.URLClassLoader.findClass(URLClassLoader.java:434)
10/28/14 7:10:57:152 EDT 00a0 SystemErr R 	at com.ibm.ws.bootstrap.ExtClassLoader.findClass(ExtClassLoader.java:204)
10/28/14 7:10:57:152 EDT 00a0 SystemErr R 	at java.lang.ClassLoader.loadClassHelper(ClassLoader.java:699)
10/28/14 7:10:57:152 EDT 00a0 SystemErr R 	at java.lang.ClassLoader.loadClass(ClassLoader.java:678)
10/28/14 7:10:57:152 EDT 00a0 SystemErr R 	at com.ibm.ws.bootstrap.ExtClassLoader.loadClass(ExtClassLoader.java:119)
10/28/14 7:10:57:152 EDT 00a0 SystemErr R 	at java.lang.ClassLoader.loadClass(ClassLoader.java:661)
10/28/14 7:10:57:152 EDT 00a0 SystemErr R 	at com.ibm.ws.classloader.ProtectionClassLoader.loadClass(ProtectionClassLoader.java:62)
10/28/14 7:10:57:152 EDT 00a0 SystemErr R 	at com.ibm.ws.classloader.ProtectionClassLoader.loadClass(ProtectionClassLoader.java:58)
10/28/14 7:10:57:152 EDT 00a0 SystemErr R 	at com.ibm.ws.classloader.CompoundClassLoader.loadClass(CompoundClassLoader.java:616)
10/28/14 7:10:57:152 EDT 00a0 SystemErr R 	at java.lang.ClassLoader.loadClass(ClassLoader.java:661)
10/28/14 7:10:57:152 EDT 00a0 SystemErr R 	... 1 more
10/28/14 7:10:57:355 EDT 008f SystemErr R com.ibm.ws.exception.RuntimeWarning: com.ibm.ws.webcontainer.exception.WebAppNotLoadedException: Failed to load webapp: Failed to load webapp: SRVE8111E: The application, jenkins_war, is trying to modify a cookie which matches a pattern in the restricted programmatic session cookies list domain=*, name=JSESSIONID, path=/.
10/28/14 7:10:57:355 EDT 008f SystemErr R 	at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:432)
10/28/14 7:10:57:355 EDT 008f SystemErr R 	at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:718)
10/28/14 7:10:57:355 EDT 008f SystemErr R 	at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1175)
10/28/14 7:10:57:355 EDT 008f SystemErr R 	at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1370)
10/28/14 7:10:57:355 EDT 008f SystemErr R 	at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:639)
10/28/14 7:10:57:355 EDT 008f SystemErr R 	at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:968)
10/28/14 7:10:57:355 EDT 008f SystemErr R 	at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:774)
10/28/14 7:10:57:355 EDT 008f SystemErr R 	at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplicationDynamically(ApplicationMgrImpl.java:1374)
10/28/14 7:10:57:355 EDT 008f SystemErr R 	at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:2179)
10/28/14 7:10:57:355 EDT 008f SystemErr R 	at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:445)
10/28/14 7:10:57:355 EDT 008f SystemErr R 	at com.ibm.ws.runtime.component.CompositionUnitImpl.start(CompositionUnitImpl.java:123)
10/28/14 7:10:57:355 EDT 008f SystemErr R 	at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:388)
10/28/14 7:10:57:355 EDT 008f SystemErr R 	at 

[JIRA] [core] (JENKINS-23942) quietDown reports HTTP 405 Method Not Allowed

2014-10-28 Thread bcov...@nycm.com (JIRA)















































Bruce Coveny
 closed  JENKINS-23942 as Fixed


quietDown reports HTTP 405 Method Not Allowed
















Tested in 1.585 works now.





Change By:


Bruce Coveny
(28/Oct/14 11:24 AM)




Status:


Resolved
Closed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-25337) Jenkins fails to start

2014-10-28 Thread bcov...@nycm.com (JIRA)














































Bruce Coveny
 commented on  JENKINS-25337


Jenkins fails to start















Reverting back to 1.585 Jenkins starts successfully.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [cli] (JENKINS-25338) list-jobs cli

2014-10-28 Thread bcov...@nycm.com (JIRA)














































Bruce Coveny
 created  JENKINS-25338


list-jobs cli















Issue Type:


Improvement



Assignee:


Unassigned


Components:


cli



Created:


28/Oct/14 1:10 PM



Description:


Currently the list-jobs prints out the "Display Name" in the advanced option configuration of the job.  However other commands such as get-job requires the "Project Name".  Can the commands be either changed to accept either of these names or have parameters on the list-jobs to select which name to print out.  get-job submits an error while using the "Display Name" which states the project name in it.  For example if the "Display Name" is "My Build" and project name is "MY_BUILD" if you do get-job "My Build" it gives you the error "No such job 'My Build'; perhaps you meant 'MY_BUILD'?




Environment:


JENKINS WAR VERSION 1.586 

WINDOWS SERVER 2008 R2 ENTERPRISE 

AMD OPTERON(TM) PROCESSOR 6136 2.4 GHZ (2 PROCESSORS) 

4.0 GB RAM 

64-BIT OPERATION SYSTEM 

WEBSPHERE APPLICATION SERVER 8.5.5 




Project:


Jenkins



Priority:


Minor



Reporter:


Bruce Coveny

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-25337) Jenkins fails to start

2014-10-28 Thread bcov...@nycm.com (JIRA)














































Bruce Coveny
 commented on  JENKINS-25337


Jenkins fails to start















Confused by this.  So it shouldn't be HttpOnly?  Why would this change between Jenkins 1.585 and 1.586.  Also according to the property in WebSphere it makes it sound like you want it HttpOnly to prevent cross-site scripting attacks.

WebSphere checkbox label:
Set session cookies to HTTPOnly to help prevent cross-site scripting attacks 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-25337) Jenkins fails to start

2014-10-28 Thread bcov...@nycm.com (JIRA)














































Bruce Coveny
 commented on  JENKINS-25337


Jenkins fails to start















I tried setting flags based on http://www-01.ibm.com/support/docview.wss?uid=swg21422185  however messing with either of the flags resulted in Jenkins still failing to start.  The only way I was able to get Jenkins to start was to change the name of the cookie from JSESSIONID to JSESSIONID_SVR.  I do not feel this is optimal and would like suggestions on how to continue.  I tried all different combo's of the two checkboxes in the attached image.






























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-25337) Jenkins fails to start

2014-10-28 Thread bcov...@nycm.com (JIRA)














































Bruce Coveny
 commented on  JENKINS-25337


Jenkins fails to start















I understand what is it saying, just have no idea on how to fix since we have not changed any of the settings of WebSphere from the default settings.  So I have not disabled anything it was already set like that by default.  So how to unset it?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [ldap] (JENKINS-18961) LDAP plugin does not support nested groups

2014-09-08 Thread bcov...@nycm.com (JIRA)














































Bruce Coveny
 commented on  JENKINS-18961


LDAP plugin does not support nested groups 















There has been some chat on the springsource ticket and wondering if this could be investigated to what they said to allow nested groups.  My firm only uses nested groups so instead of one or two groups we now have to add 50 different groups to Jenkins security console and maintain them all.


Jean-Pierre Bergamin added a comment - 17/Jun/14 1:31 AM 

I use this class here: https://gist.github.com/ractive/258dd06c99d2939781c0
 Put it in the package org.springframework.security.ldap.authentication.ad and you should be ready to go...



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-23942) quietDown reports HTTP 405 Method Not Allowed

2014-07-23 Thread bcov...@nycm.com (JIRA)














































Bruce Coveny
 created  JENKINS-23942


quietDown reports HTTP 405 Method Not Allowed















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


core



Created:


23/Jul/14 12:10 PM



Description:


When going to Manage Jenkins and clicking Prepare for Shutdown the /quietDown throws a HTTP 405 Method Not Allowed.  I cannot find anything in any logs as to why.




Environment:


JENKINS WAR VERSION 1.573

WINDOWS SERVER 2008 R2 ENTERPRISE 

AMD OPTERON(TM) PROCESSOR 6136 2.4 GHZ (2 PROCESSORS) 

4.0 GB RAM 

64-BIT OPERATION SYSTEM 

WEBSPHERE APPLICATION SERVER 8.5.5 




Project:


Jenkins



Labels:


jenkins
exception




Priority:


Critical



Reporter:


Bruce Coveny

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-23942) quietDown reports HTTP 405 Method Not Allowed

2014-07-23 Thread bcov...@nycm.com (JIRA)














































Bruce Coveny
 commented on  JENKINS-23942


quietDown reports HTTP 405 Method Not Allowed















/quietDown did not work on 1.572 or 1.573 for me.  I cannot use a "pristine" version of Jenkins as I can only use the instances of Jenkins we have.  I think the @RequirePOST is potentially the issue here.  The other thing I am seeing (which could be related) is using the CLI jar and attempting to do quiet-down doesn't work either.  I get the exception noted below even though the username I am using has the Overall/Administer permission.

hudson.security.AccessDeniedException2: anonymous is missing the Overall/Administer permission
at hudson.security.ACL.checkPermission(ACL.java:55)
at hudson.model.Node.checkPermission(Node.java:417)
at jenkins.model.Jenkins.doQuietDown(Jenkins.java:2892)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at hudson.cli.declarative.MethodBinder.call(MethodBinder.java:102)
at hudson.cli.declarative.CLIRegisterer$1.main(CLIRegisterer.java:185)
at hudson.cli.CliManagerImpl.main(CliManagerImpl.java:92)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:309)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:290)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:249)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:328)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at hudson.cli.CliManagerImpl$1.call(CliManagerImpl.java:63)
at hudson.remoting.InterceptingExecutorService$2.call(InterceptingExecutorService.java:95)
at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314)
at java.util.concurrent.FutureTask.run(FutureTask.java:149)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:906)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:929)
at java.lang.Thread.run(Thread.java:773)



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-23942) quietDown reports HTTP 405 Method Not Allowed

2014-07-23 Thread bcov...@nycm.com (JIRA)














































Bruce Coveny
 commented on  JENKINS-23942


quietDown reports HTTP 405 Method Not Allowed















The who-am-i has no bearing on this as I pass in --username %username and --password $password.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-23942) quietDown reports HTTP 405 Method Not Allowed

2014-07-23 Thread bcov...@nycm.com (JIRA)














































Bruce Coveny
 commented on  JENKINS-23942


quietDown reports HTTP 405 Method Not Allowed















I understand that but I am obviously passing in the credentials much like that should be passed to the /quietDown URL when logged in from the screens.  I feel this is the issue that the credentials are not properly supplied and generating the error HTTP 405 as well as the cli throwing the error thinking that I am anonymous which doesn't have the proper permissions where my username does have the proper permissions.  With you saying this is working in 1.572 and 1.573 is your instance configured with security and the anonymous account not having the overall/administer permission?  Can you try to change that and see if your errors like this?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-23942) quietDown reports HTTP 405 Method Not Allowed

2014-07-23 Thread bcov...@nycm.com (JIRA)














































Bruce Coveny
 updated  JENKINS-23942


quietDown reports HTTP 405 Method Not Allowed
















cli cancel-quiet-down security





Change By:


Bruce Coveny
(23/Jul/14 7:01 PM)




Attachment:


jenkins_cancel_quiet_down_cli_error.png



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-23942) quietDown reports HTTP 405 Method Not Allowed

2014-07-23 Thread bcov...@nycm.com (JIRA)














































Bruce Coveny
 commented on  JENKINS-23942


quietDown reports HTTP 405 Method Not Allowed















So your testing on 1.572 and 1.573 was without security enabled?

I gave anonymous  Overall/Administer permission and the /quietDown still gives me HTTP 405 error.  I then tried the cli again and the cli now works with quiet-down.  The /cancelQuietDown gives me the HTTP 405 error as well.  The cli for cancel-quiet-down works.  I then took the security option for Overall/Adminsiter back away and the cancel-quiet-down fails.




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-23942) quietDown reports HTTP 405 Method Not Allowed

2014-07-23 Thread bcov...@nycm.com (JIRA)












































 
Bruce Coveny
 edited a comment on  JENKINS-23942


quietDown reports HTTP 405 Method Not Allowed
















So your testing on 1.572 and 1.573 was without security enabled?

I gave anonymous  Overall/Administer permission and the /quietDown still gives me HTTP 405 error.  I then tried the cli again and the cli now works with quiet-down.  The /cancelQuietDown gives me the HTTP 405 error as well.  The cli for cancel-quiet-down works.  I then took the security option for Overall/Adminsiter back away and the cancel-quiet-down fails. (Added image of this situation to request)




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [artifactdeployer] (JENKINS-23313) Overwrite Files or only cleanup files to be copied to remote directory

2014-06-04 Thread bcov...@nycm.com (JIRA)














































Bruce Coveny
 created  JENKINS-23313


Overwrite Files or only cleanup files to be copied to remote directory















Issue Type:


Improvement



Affects Versions:


current



Assignee:


Gregory Boissinot



Components:


artifactdeployer



Created:


04/Jun/14 1:39 PM



Description:


When attempting to write to a remote server unless you specify "Clean-up remote directory before deployment" the files fail to move with error:

ArtifactDeployer - Starting deployment from the post-action ...
ArtifactDeployer - All the files have not been deployed. There was 2 input files but only 0 was copied. Maybe you have to use 'Delete content of remote directory' feature for deleting remote directory before deploying.
ArtifactDeployer - Stopping deployment from the post-action...

I assume this is the option that is what the error is referring to as there is no option for 'Delete content of remote directory'.  The only issue with this is that it deletes everything from the directory.  This is a file share and there are other files in the directory that need to reside in the directory that are generated from other builds and used by other builds.

Either the cleanup option should only remove files that are attempting to be moved, allow another option to perform that way, or have an option to overwrite the files if they exist.

This plug works as I need to with the exception of this and I cannot use the plugin until a better cleanup solution exists. 





Environment:


JENKINS WAR VERSION 1.566

WINDOWS SERVER 2008 R2 ENTERPRISE 

AMD OPTERON(TM) PROCESSOR 6136 2.4 GHZ (2 PROCESSORS) 

4.0 GB RAM 

64-BIT OPERATION SYSTEM 

WEBSPHERE APPLICATION SERVER 8.5.5 




Project:


Jenkins



Priority:


Blocker



Reporter:


Bruce Coveny

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-17460) Error occurs viewing build history on some builds

2013-11-22 Thread bcov...@nycm.com (JIRA)














































Bruce Coveny
 updated  JENKINS-17460


Error occurs viewing build history on some builds
















Change By:


Bruce Coveny
(22/Nov/13 1:16 PM)




Environment:


JENKINSWARVERSION1.509-1.
529
539
WINDOWSSERVER2008R2ENTERPRISEAMDOPTERON(TM)PROCESSOR61362.4GHZ(2PROCESSORS)4.0GBRAM64-BITOPERATIONSYSTEMWEBSPHEREAPPLICATIONSERVER8.5.5



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


[JIRA] [core] (JENKINS-20675) Java platform binary has stopped working message appears when starting Jenkins 1.540

2013-11-20 Thread bcov...@nycm.com (JIRA)














































Bruce Coveny
 commented on  JENKINS-20675


Java platform binary has stopped working message appears when starting Jenkins 1.540















This is happening to us as well but we are running on a WAS server and it crashes the server and I cannot find a way to "downgrade" to 1.539 any suggestions?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


[JIRA] [sidebar-link] (JENKINS-18887) Alllow links to open in new window/tab

2013-07-23 Thread bcov...@nycm.com (JIRA)














































Bruce Coveny
 created  JENKINS-18887


Alllow links to open in new window/tab















Issue Type:


Improvement



Assignee:


Unassigned


Components:


sidebar-link



Created:


23/Jul/13 2:11 PM



Description:


Allow links added to sidebar to be able to open in a new window or new tab.




Project:


Jenkins



Priority:


Minor



Reporter:


Bruce Coveny

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] [core] (JENKINS-17460) Error occurs viewing build history on some builds

2013-06-26 Thread bcov...@nycm.com (JIRA)














































Bruce Coveny
 updated  JENKINS-17460


Error occurs viewing build history on some builds
















Change By:


Bruce Coveny
(26/Jun/13 11:29 AM)




Environment:


JENKINSWARVERSION1.509
/
-
1.
510
519
WINDOWSSERVER2008R2ENTERPRISEAMDOPTERON(TM)PROCESSOR61362.4GHZ(2PROCESSORS)4.0GBRAM64-BITOPERATIONSYSTEMWEBSPHEREAPPLICATIONSERVER7.0.0.23



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] [core] (JENKINS-17715) Display Name is not shown

2013-05-20 Thread bcov...@nycm.com (JIRA)














































Bruce Coveny
 commented on  JENKINS-17715


Display Name is not shown















This states resolved but I we are on version 1.514 and are still seeing the Job Name being shown in the tabs on the main screen and not the Job Display Name.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] [core] (JENKINS-17715) Display Name is not shown

2013-05-20 Thread bcov...@nycm.com (JIRA)












































 
Bruce Coveny
 edited a comment on  JENKINS-17715


Display Name is not shown
















This states resolved but we are on version 1.514 and are still seeing the Job Name being shown in the tabs on the main screen and not the Job Display Name.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] [active-directory] (JENKINS-17718) Active Directory Plugin Fails

2013-04-23 Thread bcov...@nycm.com (JIRA)














































Bruce Coveny
 created  JENKINS-17718


Active Directory Plugin Fails















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


active-directory



Created:


23/Apr/13 3:16 PM



Description:


Upgraded from version 1.30 of plugin to version 1.31 and cannot login, and get error "Incorrect password" and error "The server is not operational".  I have attached stack trace of error with some XXX_excluded sections removed for security reasons.

Setup for plugin is as follows:
Domain Name:  BLANK
Domain Controller:  ldap_server_ip:389

4/23/13 11:03:05:166 EDT 001f Authenticatio I   Login attempt failed
 org.acegisecurity.BadCredentialsException: Incorrect password for uid_excluded for="" class="error">conn_string_excluded: error=8007203A; nested exception is com4j.ComException: 8007203a The server is not operational. : The server is not operational.
 : .\invoke.cpp:517
	at hudson.plugins.active_directory.ActiveDirectoryAuthenticationProvider.retrieveUser(ActiveDirectoryAuthenticationProvider.java:109)
	at org.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:122)
	at org.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:200)
	at org.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:47)
	at org.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:74)
	at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
	at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
	at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
	at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)
	at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)
	at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50)
	at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)
	at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)
	at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
	at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)
	at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)
	at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:77)
	at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:908)
	at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:934)
	at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:502)
	at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:181)
	at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3935)
	at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:276)
	at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:931)
	at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1592)
	at 

[JIRA] [active-directory] (JENKINS-17718) Active Directory Plugin Fails

2013-04-23 Thread bcov...@nycm.com (JIRA)














































Bruce Coveny
 commented on  JENKINS-17718


Active Directory Plugin Fails















Also could not downgrade:

java.io.IOException: Failed to rename JENKINS_HOME\active-directory.bak to JENKINS_HOME\plugins\active-directory.jpi
	at hudson.model.UpdateCenter$PluginDowngradeJob.replace(UpdateCenter.java:1417)
	at hudson.model.UpdateCenter$UpdateCenterConfiguration.install(UpdateCenter.java:806)
	at hudson.model.UpdateCenter$PluginDowngradeJob._run(UpdateCenter.java:1406)
	at hudson.model.UpdateCenter$PluginDowngradeJob.run(UpdateCenter.java:1389)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:736)



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] [active-directory] (JENKINS-17718) Active Directory Plugin Fails

2013-04-23 Thread bcov...@nycm.com (JIRA)














































Bruce Coveny
 updated  JENKINS-17718


Active Directory Plugin Fails
















Change By:


Bruce Coveny
(23/Apr/13 3:26 PM)




Description:


Upgradedfromversion1.30ofplugintoversion1.31andcannotlogin,andgeterrorIncorrectpasswordanderrorTheserverisnotoperational.Ihaveattachedstacktraceoferrorwithsome[XXX_excluded]sectionsremovedforsecurityreasons.
Revertingbacktoversion1.30andhavenoissueswithlogin.
Setupforpluginisasfollows:DomainName:[BLANK]DomainController:[ldap_server_ip]:389[4/23/1311:03:05:166EDT]001fAuthenticatioILoginattemptfailedorg.acegisecurity.BadCredentialsException:Incorrectpasswordfor[uid_excluded]for="">:.\invoke.cpp:517	athudson.plugins.active_directory.ActiveDirectoryAuthenticationProvider.retrieveUser(ActiveDirectoryAuthenticationProvider.java:109)	atorg.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:122)	atorg.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:200)	atorg.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:47)	atorg.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:74)	atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252)	athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)	atorg.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)	athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)	atjenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64)	athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)	atorg.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)	athudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)	athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)	athudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)	athudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)	atcom.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)	atcom.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)	atorg.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50)	atcom.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)	atcom.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)	athudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)	atcom.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)	atcom.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)	atcom.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:77)	atcom.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:908)	atcom.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:934)	atcom.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:502)	atcom.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:181)	atcom.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3935)	atcom.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:276)	atcom.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:931)	atcom.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1592)	atcom.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:186)	atcom.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:452)	atcom.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:511)	atcom.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:305)	atcom.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:83)	atcom.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)	

[JIRA] [active-directory] (JENKINS-17718) Active Directory Plugin Fails

2013-04-23 Thread bcov...@nycm.com (JIRA)














































Bruce Coveny
 updated  JENKINS-17718


Active Directory Plugin Fails
















Change By:


Bruce Coveny
(23/Apr/13 3:33 PM)




Description:


Upgradedfromversion1.30ofplugintoversion1.31andcannotlogin,andgeterrorIncorrectpasswordanderrorTheserverisnotoperational.Ihaveattachedstacktraceoferrorwithsome[XXX_excluded]sectionsremovedforsecurityreasons.Revertingbacktoversion1.30andhavenoissueswithlogin.
{code}
Setupforpluginisasfollows:DomainName:[BLANK]DomainController:[ldap_server_ip]:389
{code}

{code}
[4/23/1311:03:05:166EDT]001fAuthenticatioILoginattemptfailedorg.acegisecurity.BadCredentialsException:Incorrectpasswordfor[uid_excluded]for="">:.\invoke.cpp:517	athudson.plugins.active_directory.ActiveDirectoryAuthenticationProvider.retrieveUser(ActiveDirectoryAuthenticationProvider.java:109)	atorg.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:122)	atorg.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:200)	atorg.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:47)	atorg.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:74)	atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252)	athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)	atorg.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)	athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)	atjenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64)	athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)	atorg.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)	athudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)	athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)	athudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)	athudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)	atcom.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)	atcom.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)	atorg.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50)	atcom.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)	atcom.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)	athudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)	atcom.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)	atcom.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)	atcom.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:77)	atcom.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:908)	atcom.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:934)	atcom.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:502)	atcom.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:181)	atcom.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3935)	atcom.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:276)	atcom.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:931)	atcom.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1592)	atcom.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:186)	atcom.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:452)	atcom.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:511)	atcom.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:305)	atcom.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:83)	atcom.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)	

[JIRA] [active-directory] (JENKINS-17718) Active Directory Plugin Fails

2013-04-23 Thread bcov...@nycm.com (JIRA)














































Bruce Coveny
 updated  JENKINS-17718


Active Directory Plugin Fails
















Change By:


Bruce Coveny
(23/Apr/13 3:33 PM)




Description:


Upgradedfromversion1.30ofplugintoversion1.31andcannotlogin,andgeterrorIncorrectpasswordanderrorTheserverisnotoperational.Ihaveattachedstacktraceoferrorwithsome[XXX_excluded]sectionsremovedforsecurityreasons.Revertingbacktoversion1.30andhavenoissueswithlogin.

{code}Setupforpluginisasfollows:DomainName:[BLANK]DomainController:[ldap_server_ip]:389{code}{code}[4/23/1311:03:05:166EDT]001fAuthenticatioILoginattemptfailedorg.acegisecurity.BadCredentialsException:Incorrectpasswordfor[uid_excluded]for="">:.\invoke.cpp:517	athudson.plugins.active_directory.ActiveDirectoryAuthenticationProvider.retrieveUser(ActiveDirectoryAuthenticationProvider.java:109)	atorg.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:122)	atorg.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:200)	atorg.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:47)	atorg.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:74)	atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252)	athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)	atorg.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)	athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)	atjenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64)	athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)	atorg.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)	athudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)	athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)	athudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)	athudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)	atcom.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)	atcom.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)	atorg.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50)	atcom.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)	atcom.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)	athudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)	atcom.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)	atcom.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)	atcom.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:77)	atcom.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:908)	atcom.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:934)	atcom.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:502)	atcom.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:181)	atcom.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3935)	atcom.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:276)	atcom.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:931)	atcom.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1592)	atcom.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:186)	atcom.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:452)	atcom.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:511)	atcom.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:305)	atcom.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:83)	atcom.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)	

[JIRA] [active-directory] (JENKINS-17718) Active Directory Plugin Fails

2013-04-23 Thread bcov...@nycm.com (JIRA)














































Bruce Coveny
 updated  JENKINS-17718


Active Directory Plugin Fails
















Change By:


Bruce Coveny
(23/Apr/13 4:35 PM)




Description:


Upgradedfromversion1.30ofplugintoversion1.31andcannotlogin,andgeterrorIncorrectpasswordanderrorTheserverisnotoperational.Ihaveattachedstacktraceoferrorwithsome[XXX_excluded]sectionsremovedforsecurityreasons.Revertingbacktoversion1.30andhavenoissueswithlogin.
\\
{code}Setupforpluginisasfollows:DomainName:[BLANK]DomainController:[ldap_server_ip]:389{code}{code}[4/23/1311:03:05:166EDT]001fAuthenticatioILoginattemptfailedorg.acegisecurity.BadCredentialsException:Incorrectpasswordfor[uid_excluded]for="">:.\invoke.cpp:517	athudson.plugins.active_directory.ActiveDirectoryAuthenticationProvider.retrieveUser(ActiveDirectoryAuthenticationProvider.java:109)	atorg.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:122)	atorg.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:200)	atorg.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:47)	atorg.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:74)	atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252)	athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)	atorg.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)	athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)	atjenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64)	athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)	atorg.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)	athudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)	athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)	athudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)	athudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)	atcom.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)	atcom.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)	atorg.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50)	atcom.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)	atcom.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)	athudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)	atcom.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)	atcom.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)	atcom.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:77)	atcom.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:908)	atcom.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:934)	atcom.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:502)	atcom.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:181)	atcom.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3935)	atcom.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:276)	atcom.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:931)	atcom.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1592)	atcom.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:186)	atcom.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:452)	atcom.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:511)	atcom.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:305)	atcom.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:83)	atcom.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)	

[JIRA] [active-directory] (JENKINS-17718) Active Directory Plugin Fails

2013-04-23 Thread bcov...@nycm.com (JIRA)












































 
Bruce Coveny
 edited a comment on  JENKINS-17718


Active Directory Plugin Fails
















Also could not downgrade:


java.io.IOException: Failed to rename [JENKINS_HOME]\active-directory.bak to [JENKINS_HOME]\plugins\active-directory.jpi
	at hudson.model.UpdateCenter$PluginDowngradeJob.replace(UpdateCenter.java:1417)
	at hudson.model.UpdateCenter$UpdateCenterConfiguration.install(UpdateCenter.java:806)
	at hudson.model.UpdateCenter$PluginDowngradeJob._run(UpdateCenter.java:1406)
	at hudson.model.UpdateCenter$PluginDowngradeJob.run(UpdateCenter.java:1389)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:736)


Manually downgraded and have no issues with login.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] [core] (JENKINS-17460) Error occurs viewing build history on some builds

2013-04-23 Thread bcov...@nycm.com (JIRA)














































Bruce Coveny
 updated  JENKINS-17460


Error occurs viewing build history on some builds
















Change By:


Bruce Coveny
(23/Apr/13 4:37 PM)




Description:


Whentryingtoviewbuildhistoryfromprojectgeterrorsandpagewillnotdisplay.Noteveryprojectfailsjustcertainones.ProjectswiththenameXseemtowork,butprojectswithnameX(YYY)seemtofail.IthoughtitmighthavetodowithaspacebutprojectswithnameX()workfinewithoutissue.AttachedstacktraceisfromSystemOut.logfromWebSphereserver.
\\

\\{code}
[4/3/1315:33:36:725EDT]0021servletEcom.ibm.ws.webcontainer.servlet.ServletWrapperserviceSRVE0068E:UncaughtexceptioncreatedinoneoftheservicemethodsoftheservletStaplerinapplicationjenkins_war.Exceptioncreated:javax.servlet.ServletException:org.apache.commons.jelly.JellyTagException:wsjar:file:/jenkins_war.ear/jenkins.war/WEB-INF/lib/jenkins-core-1.509.jar!/hudson/model/AbstractBuild/index.jelly:112:84:st:includeCannotcomparejava.util.ArrayListwithvalue[]andjava.lang.Integerwithvalue0	atorg.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117)	atorg.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127)	atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:666)	atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:770)	atorg.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384)	atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677)	atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:770)	atorg.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)	atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)	atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677)	atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:770)	atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:583)	atorg.kohsuke.stapler.Stapler.service(Stapler.java:214)	atjavax.servlet.http.HttpServlet.service(HttpServlet.java:831)	atcom.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1657)	atcom.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1597)	atcom.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:131)	athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)	athudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)	athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)	athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)	atcom.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)	atcom.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)	athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)	atcom.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)	atcom.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)	athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)	athudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)	athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)	atorg.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124)	athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)	atorg.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)	athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)	atorg.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)	athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)	atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)	athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)	atorg.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)	athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)	atjenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64)	athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)	

[JIRA] [core] (JENKINS-17460) Error occurs viewing build history on some builds

2013-04-15 Thread bcov...@nycm.com (JIRA)














































Bruce Coveny
 updated  JENKINS-17460


Error occurs viewing build history on some builds
















Change By:


Bruce Coveny
(15/Apr/13 3:53 PM)




Component/s:


parameterized-trigger



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] [core] (JENKINS-17460) Error occurs viewing build history on some builds

2013-04-11 Thread bcov...@nycm.com (JIRA)














































Bruce Coveny
 commented on  JENKINS-17460


Error occurs viewing build history on some builds















I was able to recreate doing the following.  Create a build called "test", this does not have to any steps included in it.  Create another build called "test (test)".  In this build configuration create the build step of "Trigger/call builds on other projects" with the following properties:

Projects to build:  test
Block until the triggered projects finsih their builds:  checked
Fail this build step if the triggered build is worse or equal to:  FAILURE
Mark this build as failure if the triggered build is worse or equal to:  FAILURE
Mark this build as unstable if the triggered build is worse or equal to:  UNSTABLE

Save the configuration.  Run the build on "test (test)".  Once the build history shows on the left hand side, click the link for view the build history.  This is when the failure occurs.  You can click the menu dropdown for the build history to view the console output and that link works fine, its just the main page for the build that fails.

Note this still happens in 1.510.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] [core] (JENKINS-17460) Error occurs viewing build history on some builds

2013-04-11 Thread bcov...@nycm.com (JIRA)












































 
Bruce Coveny
 edited a comment on  JENKINS-17460


Error occurs viewing build history on some builds
















I was able to recreate doing the following.  Create a build called "test", this does not have to any steps included in it.  Create another build called "test (test)".  In this build configuration create the build step of "Trigger/call builds on other projects" with the following properties:

Projects to build:  test
Block until the triggered projects finish their builds:  checked
Fail this build step if the triggered build is worse or equal to:  FAILURE
Mark this build as failure if the triggered build is worse or equal to:  FAILURE
Mark this build as unstable if the triggered build is worse or equal to:  UNSTABLE

Save the configuration.  Run the build on "test (test)".  Once the build history shows on the left hand side, click the link for view the build history.  This is when the failure occurs.  You can click the menu dropdown for the build history to view the console output and that link works fine, its just the main page for the build that fails.

Note this still happens in 1.510.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] [core] (JENKINS-17460) Error occurs viewing build history on some builds

2013-04-03 Thread bcov...@nycm.com (JIRA)














































Bruce Coveny
 updated  JENKINS-17460


Error occurs viewing build history on some builds
















Change By:


Bruce Coveny
(03/Apr/13 8:38 PM)




Environment:


JENKINSWARVERSION1.509WINDOWSSERVER2008R2ENTERPRISEAMDOPTERON(TM)PROCESSOR61362.4GHZ(2PROCESSORS)4.0GBRAM64-BITOPERATIONSYSTEM
WEBSPHER
WEBSPHERE
APPLICATIONSERVER7.0.0.23



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] [core] (JENKINS-17460) Error occurs viewing build history on some builds

2013-04-03 Thread bcov...@nycm.com (JIRA)














































Bruce Coveny
 created  JENKINS-17460


Error occurs viewing build history on some builds















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


core



Created:


03/Apr/13 8:37 PM



Description:


When trying to view build history from project get errors and page will not display.  Not every project fails just certain ones.  Projects with the name 'X' seem to work, but projects with name 'X (YYY)' seem to fail.  I thought it might have to do with a space but projects with name 'X ( )' work fine without issue.

Attached stack trace is from SystemOut.log from WebSphere server.

4/3/13 15:33:36:725 EDT 0021 servlet   E com.ibm.ws.webcontainer.servlet.ServletWrapper service SRVE0068E: Uncaught exception created in one of the service methods of the servlet Stapler in application jenkins_war. Exception created : javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: wsjar:file:/jenkins_war.ear/jenkins.war/WEB-INF/lib/jenkins-core-1.509.jar!/hudson/model/AbstractBuild/index.jelly:112:84: st:include Cannot compare java.util.ArrayList with value '[]' and java.lang.Integer with value '0'
	at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117)
	at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:666)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
	at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:214)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
	at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1657)
	at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1597)
	at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:131)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
	at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
	at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)
	at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
	at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)
	at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
	at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
	at