date:20140620

2014-06-20 Thread stu...@somepointinthefuture.co.nz (JIRA)















































Oleg Nenashev
 updated  JENKINS-23525


Crash when using Folders plugin: com.cloudbees.hudson.plugins.folder.Folder cannot be cast to hudson.model.Job
















It is a wrong items handling in xfpanel plugin.
Currently, the plugin passes Jenkins Items to a method, which takes only Jobs.

https://github.com/jenkinsci/xfpanel-plugin/blob/cfeaa9101e1634e795dd885368797a563c8c2ff9/src/main/resources/maps/hudson/plugin/xfpanel/XFPanelView/configure-entries.jelly


  




https://github.com/jenkinsci/xfpanel-plugin/blob/cfeaa9101e1634e795dd885368797a563c8c2ff9/src/main/java/maps/hudson/plugin/xfpanel/XFPanelView.java

public Collection> getPrioritySortedJobs(Collection> jobs) {
if (jobs != null) {
List> sortedJobs = new ArrayList>();
Map> jobMap = new HashMap>();

int priority = 0, added = 0;
if (priorityPerJob != null) {

// Set elements
EXCEPTION(386) ==>  for (Job job: jobs) {
   













Change By:


Oleg Nenashev
(21/Jun/14 6:58 AM)




Assignee:


Jesse Glick
Julien RENAUT





Component/s:


cloudbees-folder



























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] [cloudbees-folder] (JENKINS-23525) Crash when using Folders plugin: com.cloudbees.hudson.plugins.folder.Folder cannot be cast to hudson.model.Job















































Stuart Whelan
 created  JENKINS-23525


Crash when using Folders plugin: com.cloudbees.hudson.plugins.folder.Folder cannot be cast to hudson.model.Job















Issue Type:


Bug



Assignee:


Jesse Glick



Components:


cloudbees-folder, xfpanel



Created:


21/Jun/14 5:48 AM



Description:


javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/plugins/xfpanel/WEB-INF/lib/classes.jar!/maps/hudson/plugin/xfpanel/XFPanelView/configure-entries.jelly:43:73:  method getPrioritySortedJobs threw exception: com.cloudbees.hudson.plugins.folder.Folder cannot be cast to hudson.model.Job
	at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:225)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
	at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	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 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 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:74)
	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 org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.util.CharacterEn

[JIRA] [maven] (JENKINS-19827) Maven builds via Maven Project Plugin in Jenkins fail when using the openjpa-maven-plugin with enhance goal

2014-06-20 Thread mreba...@gmail.com (JIRA)
















































Marcelo Rebasti
 resolved  JENKINS-19827 as Cannot Reproduce


Maven builds via Maven Project Plugin in Jenkins fail when using the openjpa-maven-plugin with enhance goal
















Chris,

After 8 months without response I assume that the issue is resolved.

If you still have the problem, feel free to reopen the issue.
Regards.

Marcelo Rebasti





Change By:


Marcelo Rebasti
(21/Jun/14 1:31 AM)




Status:


Open
Resolved





Resolution:


Cannot Reproduce



























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] [ws-cleanup] (JENKINS-23523) External delete cmd doesn't work properly















































SCM/JIRA link daemon
 commented on  JENKINS-23523


External delete cmd doesn't work properly















Code changed in jenkins
User: Vojtech Juranek
Path:
 src/main/java/hudson/plugins/ws_cleanup/Cleanup.java
http://jenkins-ci.org/commit/ws-cleanup-plugin/6ecea969cab0b7691bcb6395a0bb41b9d6b8f626
Log:
  [FIXED JENKINS-23523] Fix external delete reg. exp and refactoring





























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] [ws-cleanup] (JENKINS-23523) External delete cmd doesn't work properly
















































SCM/JIRA link daemon
 resolved  JENKINS-23523 as Fixed


External delete cmd doesn't work properly
















Change By:


SCM/JIRA link daemon
(21/Jun/14 1:26 AM)




Status:


Open
Resolved





Resolution:


Fixed



























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] [build-pipeline] (JENKINS-23524) Build Pipeline does not discover downstream promoted jobs?

2014-06-20 Thread mwigz...@tweddle.com (JIRA)

Mark Wigzell
created JENKINS-23524

Build Pipeline does not discover downstream promoted jobs?

Issue Type:

Bug

Affects Versions:

current

Assignee:

Unassigned

Components:

build-pipeline

Created:

21/Jun/14 12:02 AM

Description:

I installed Build Pipeline and tried it on my jobs. They work by invoking a build as a promotion action. I was disappointed that the pipeline view failed to follow my builds except where there was a direct chain of automatic chained jobs.
I guess perhaps my expectation doesn't match the pipeline concept? Or perhaps my build flow is not a pipeline?
Basically, we have a continuous build job which allows a selected build to be promoted. The promotion action causes another build to be executed. Generally we do not have an automatic build chain, but a manual promotion chain. This approach works better for us, since we don't have to maintain (and archive) any build history unless a build is promoted.
Perhaps my expectation is in error, however I think it would be a great enhancement to a great plugin!

Environment:

Jenkins 1.554, Build Pipeline version 1.4.3

Project:

Jenkins

Labels:

promoted-build-chain

Priority:

Major

Reporter:

Mark Wigzell

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-23040) Problems with some objects names















































Daniel Beck
 commented on  JENKINS-23040


Problems with some objects names















Please run System.getProperty('file.encoding') in Manage Jenkins » Script Console and Manage Jenkins » Manage Nodes » (executing slave) » Script Console and provide output of both.



























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-23040) Problems with some objects names













































  
Daniel Beck
 edited a comment on  JENKINS-23040


Problems with some objects names
















Please run System.getProperty('file.encoding') in Manage Jenkins » Script Console and Manage Jenkins » Manage Nodes » (executing slave) » Script Console and provide output of both.



























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] [golang] (JENKINS-23509) Go versions newer than 1.2.1 cannot be installed















































SCM/JIRA link daemon
 commented on  JENKINS-23509


Go versions newer than 1.2.1 cannot be installed















Code changed in jenkins
User: Christopher Orr
Path:
 golang.groovy
http://jenkins-ci.org/commit/backend-crawler/872558d37a776d80f78cbcc7152844e1bf541153
Log:
  [FIXED JENKINS-23509] Write Go download URLs which don't point to 302 redirects.





























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] [golang] (JENKINS-23509) Go versions newer than 1.2.1 cannot be installed
















































SCM/JIRA link daemon
 resolved  JENKINS-23509 as Fixed


Go versions newer than 1.2.1 cannot be installed
















Change By:


SCM/JIRA link daemon
(20/Jun/14 9:26 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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-23364) Rename hudson-dev:run to jenkins-dev:run















































Oleg Nenashev
 commented on  JENKINS-23364


Rename hudson-dev:run to jenkins-dev:run















Reversing the behavior could be a breaking change.
Is it possible to a support both call options out-of-the-box (e.g. by parametrizing the prefix)?



























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] [ws-cleanup] (JENKINS-23523) External delete cmd doesn't work properly

2014-06-20 Thread vjura...@java.net (JIRA)















































vjuranek
 created  JENKINS-23523


External delete cmd doesn't work properly















Issue Type:


Bug



Assignee:


vjuranek



Components:


ws-cleanup



Created:


20/Jun/14 9:02 PM



Description:


When external delete command is setup, it doesn't work properly - path contains quotes and the result is that nothing is deleted.




Project:


Jenkins



Priority:


Major



Reporter:


vjuranek

























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-23364) Rename hudson-dev:run to jenkins-dev:run

2014-06-20 Thread jenk...@albersweb.de (JIRA)















































Harald Albers
 commented on  JENKINS-23364


Rename hudson-dev:run to jenkins-dev:run















created PR #1



























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-23486) Uninstalling Jenkins leaves Program Files full of files













































  
Oleg Nenashev
 edited a comment on  JENKINS-23486


Uninstalling Jenkins leaves Program Files full of files
















jenkins.wxs file does not define specific uninstaller handlers.
See https://github.com/jenkinsci/jenkins/blob/master/msi/jenkins.wxs

It means that only explicitly defined package contents (e.g. jenkins.exe) will be deleted.

I'm not sure if this issue is a bug or an improvement, but Windows apps usually ask if the user wants to delete created files. After that, they forget to clean up their garbage 



























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-23486) Uninstalling Jenkins leaves Program Files full of files















































Oleg Nenashev
 commented on  JENKINS-23486


Uninstalling Jenkins leaves Program Files full of files















jenkins.wxs file does not define specific uninstaller handlers.
See https://github.com/jenkinsci/jenkins/blob/master/msi/jenkins.wxs

It means that only explicitly deleted files (e.g. jenkins.exe) will be deleted.

I'm not sure if this issue is a bug or an improvement, but Windows apps usually ask if the user wants to delete created files. After that, they forget to clean up their garbage 



























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-23486) Uninstalling Jenkins leaves Program Files full of files

2014-06-20 Thread mark.earl.wa...@gmail.com (JIRA)















































Mark Waite
 commented on  JENKINS-23486


Uninstalling Jenkins leaves Program Files full of files















Typically Windows installers do not remove user data.  The removal process most familiar to me is that all files registered through the MSI install process are removed by the uninstall process.  User data does not usually exist at initial install, so it cannot be registered with the MSI install process.

However, they also do not place user data in the "Program Files" structure.  It is more common that "Program Files" is just for the executables, so user data is not there to be removed.

I'm not sure what the Jenkins Windows installer does, though I assume it places some user data in the C:\Program Files\Jenkins directory (based on this bug report).



























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-23517) email-ext plugin doesn't handle tokens when slave has gone offline

2014-06-20 Thread aba...@java.net (JIRA)















































abayer
 updated  JENKINS-23517


email-ext plugin doesn't handle tokens when slave has gone offline
















Gotcha - Jesse, is this going to be fixed?





Change By:


abayer
(20/Jun/14 7:13 PM)




Assignee:


Alex Earl
Jesse Glick





Component/s:


core



























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-23330) Spaces in project names are not encoded on IDs















































Daniel Beck
 commented on  JENKINS-23330


Spaces in project names are not encoded on  IDs















Is this ID even used anywhere?



























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-23040) Problems with some objects names















































Oleg Nenashev
 updated  JENKINS-23040


Problems with some objects names
















Seems to be a core issue or slave plugin issue. BTW, I have no idea how to create a reproducible scenario.

@Andres
What slave type do you use?
Please also provide the system information (see https://wiki.jenkins-ci.org/display/JENKINS/Issue+Tracking#IssueTracking-Whattoputinthedescriptionofanissuereport%3F)





Change By:


Oleg Nenashev
(20/Jun/14 7:01 PM)




Component/s:


core





Component/s:


plugin



























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-23486) Uninstalling Jenkins leaves Program Files full of files















































Daniel Beck
 updated  JENKINS-23486


Uninstalling Jenkins leaves Program Files full of files
















Is it really an expectation on Windows that uninstalling an application removes all user data?





Change By:


Daniel Beck
(20/Jun/14 6:59 PM)




Assignee:


R. Tyler Croy



























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] [youtrack] (JENKINS-23522) StackOverflowError in org.jenkinsci.plugins.youtrack.YouTrackSCMListener.onChangeLogParsed()















































Oleg Nenashev
 updated  JENKINS-23522


StackOverflowError in org.jenkinsci.plugins.youtrack.YouTrackSCMListener.onChangeLogParsed()
















Change By:


Oleg Nenashev
(20/Jun/14 6:57 PM)




Summary:


StackOverflowError
 in org.jenkinsci.plugins.youtrack.YouTrackSCMListener.onChangeLogParsed()



























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-23508) Duplicated status info for many projects on dashboard















































Daniel Beck
 commented on  JENKINS-23508


Duplicated status info for many projects on dashboard















In the global configuration, click the 'Advanced' button near the top right and check the configured builds directory. It absolutely must refer to 'ITEM_FULL_NAME', 'ITEM_FULLNAME' or 'ITEM_ROOTDIR'.



























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-22677) Allow Post-Steps to run on failed/unstable builds















































Daniel Beck
 commented on  JENKINS-22677


Allow Post-Steps to run on failed/unstable builds















Could you be more specific at to what you're referring to?



























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] [email-ext] (JENKINS-23517) email-ext plugin doesn't handle tokens when slave has gone offline















































Daniel Beck
 commented on  JENKINS-23517


email-ext plugin doesn't handle tokens when slave has gone offline















This is probably more of a core issue, see https://github.com/jenkinsci/subversion-plugin/pull/83#issuecomment-44050410



























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] [websphere-deployer] (JENKINS-23520) SOAP Connection Exception at 8879

2014-06-20 Thread erik.lump...@firstdata.com (JIRA)















































Erik Lumpkin
 commented on  JENKINS-23520


SOAP Connection Exception at 8879















This same pattern (successfully connecting to only 1 of 2 WAS instances per restart) applies to the 'Test Connection' button as well.



























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] [git] (JENKINS-18588) Git polling builds same branch multiple times when 'Execute concurrent builds if necessary' turned on

2014-06-20 Thread mike.friedr...@gmail.com (JIRA)















































Mike Friedrich
 commented on  JENKINS-18588


Git polling builds same branch multiple times when 'Execute concurrent builds if necessary' turned on















We have this issue too.
Please change the priority to Blocker, because it basically blocks the usage of concurrent builds.



























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] [youtrack] (JENKINS-23522) StackOverflowError

2014-06-20 Thread zihao...@hbo.com (JIRA)















































Zihao Yu
 created  JENKINS-23522


StackOverflowError















Issue Type:


Bug



Assignee:


Unassigned


Components:


youtrack



Created:


20/Jun/14 5:55 PM



Description:


Jenkins 1.568
Youtrack plugin 0.5.3

I'm seeing the following in build console output.


[EnvInject] - Loading node environment variables.
Building on master in workspace /opt/jenkins/workspace/infrastructure
 > git rev-parse --is-inside-work-tree
Fetching changes from the remote Git repository
 > git config remote.origin.url g...@github.com:foo/infrastructure.git
Fetching upstream changes from g...@github.com:foo/infrastructure.git
 > git --version
 > git fetch --tags --progress g...@github.com:foo/infrastructure.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse origin/master^{commit}
Checking out Revision 517c3364c34516e77a2cee7096b610ad42d7e3f5 (origin/master)
 > git config core.sparsecheckout
 > git checkout -f 517c3364c34516e77a2cee7096b610ad42d7e3f5
 > git rev-list 090eea6834088108021c40a2824ac4bf6dfd0fe4
Cleaning workspace
 > git rev-parse --verify HEAD
Resetting working tree
 > git reset --hard
 > git clean -fdx
FATAL: null
java.lang.StackOverflowError
	at java.io.UnixFileSystem.getBooleanAttributes0(Native Method)
	at java.io.UnixFileSystem.getBooleanAttributes(UnixFileSystem.java:242)
	at java.io.File.exists(File.java:819)
	at sun.misc.URLClassPath$FileLoader.getResource(URLClassPath.java:1081)
	at sun.misc.URLClassPath$FileLoader.findResource(URLClassPath.java:1048)
	at sun.misc.URLClassPath$1.next(URLClassPath.java:226)
	at sun.misc.URLClassPath$1.hasMoreElements(URLClassPath.java:236)
	at java.net.URLClassLoader$3$1.run(URLClassLoader.java:589)
	at java.net.URLClassLoader$3$1.run(URLClassLoader.java:587)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader$3.next(URLClassLoader.java:586)
	at java.net.URLClassLoader$3.hasMoreElements(URLClassLoader.java:611)
	at sun.misc.CompoundEnumeration.next(CompoundEnumeration.java:45)
	at sun.misc.CompoundEnumeration.hasMoreElements(CompoundEnumeration.java:54)
	at sun.misc.CompoundEnumeration.next(CompoundEnumeration.java:45)
	at sun.misc.CompoundEnumeration.hasMoreElements(CompoundEnumeration.java:54)
	at java.util.ServiceLoader$LazyIterator.hasNextService(ServiceLoader.java:354)
	at java.util.ServiceLoader$LazyIterator.hasNext(ServiceLoader.java:393)
	at java.util.ServiceLoader$1.hasNext(ServiceLoader.java:474)
	at javax.xml.parsers.FactoryFinder$1.run(FactoryFinder.java:293)
	at java.security.AccessController.doPrivileged(Native Method)
	at javax.xml.parsers.FactoryFinder.findServiceProvider(FactoryFinder.java:289)
	at javax.xml.parsers.FactoryFinder.find(FactoryFinder.java:267)
	at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:127)
	at org.jenkinsci.plugins.youtrack.youtrackapi.YouTrackServer.getProjects(YouTrackServer.java:283)
	at org.jenkinsci.plugins.youtrack.YouTrackSCMListener.performActions(YouTrackSCMListener.java:42)
	at org.jenkinsci.plugins.youtrack.YouTrackSCMListener.onChangeLogParsed(YouTrackSCMListener.java:34)
	at hudson.model.listeners.SCMListener.onChangeLogParsed(SCMListener.java:113)
	at hudson.model.listeners.SCMListener.onChangeLogParsed(SCMListener.java:119)
	at org.jenkinsci.plugins.youtrack.YouTrackSCMListener.onChangeLogParsed(YouTrackSCMListener.java:36)
	at hudson.model.listeners.SCMListener.onChangeLogParsed(SCMListener.java:113)
	at hudson.model.listeners.SCMListener.onChangeLogParsed(SCMListener.java:119)
	at org.jenkinsci.plugins.youtrack.YouTrackSCMListener.onChangeLogParsed(YouTrackSCMListener.java:36)
	at hudson.model.listeners.SCMListener.onChangeLogParsed(SCMListener.java:113)
	at hudson.model.listeners.SCMListener.onChangeLogParsed(SCMListener.java:119)
	at org.jenkinsci.plugins.youtrack.YouTrackSCMListener.onChangeLogParsed(YouTrackSCMListener.java:36)
	at hudson.model.listeners.SCMListener.onChangeLogParsed(SCMListener.java:113)
	at hudson.model.listeners.SCMListener.onChangeLogParsed(SCMListener.java:119)
	at org.jenkinsci.plugins.youtrack.YouTrackSCMListener.onChangeLogParsed(YouTrackSCMListener.java:36)
	at hudson.model.listeners.S

[JIRA] [rvm] (JENKINS-23521) Build breaks if job name contains space

2014-06-20 Thread dsero...@gmail.com (JIRA)















































dserodio
 created  JENKINS-23521


Build breaks if job name contains space















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


rvm



Created:


20/Jun/14 5:53 PM



Description:


The build fails when trying to execute rvm-installer if the job name contains a space:

Building in workspace /var/lib/jenkins/workspace/RVM test
Capturing environment variables produced by 'rvm use 2.0.0-p247'
$ bash -c export
$ bash -c "test -f ~/.rvm/scripts/rvm"
$ bash -c "test -f /usr/local/rvm/scripts/rvm"
Installing RVM
$ /var/lib/jenkins/workspace/RVM test/rvm-installer
FATAL: Cannot run program "/var/lib/jenkins/workspace/RVM": java.io.IOException: error=2, No such file or directory
java.io.IOException: Cannot run program "/var/lib/jenkins/workspace/RVM": java.io.IOException: error=2, No such file or directory
	at java.lang.ProcessBuilder.start(ProcessBuilder.java:475)
	at hudson.Proc$LocalProc.(Proc.java:244)
	at hudson.Proc$LocalProc.(Proc.java:216)
	at hudson.Launcher$LocalLauncher.launch(Launcher.java:775)
	at hudson.Launcher$ProcStarter.start(Launcher.java:355)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:616)
	at org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(JavaMethod.java:440)
	at org.jruby.javasupport.JavaMethod.invokeDirect(JavaMethod.java:304)
	at org.jruby.java.invokers.InstanceMethodInvoker.call(InstanceMethodInvoker.java:52)
	at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:134)
	at org.jruby.ast.CallNoArgNode.interpret(CallNoArgNode.java:64)
	at org.jruby.ast.CallOneArgNode.interpret(CallOneArgNode.java:57)
	at org.jruby.ast.NewlineNode.interpret(NewlineNode.java:105)
	at org.jruby.ast.BlockNode.interpret(BlockNode.java:71)
	at org.jruby.evaluator.ASTInterpreter.INTERPRET_METHOD(ASTInterpreter.java:75)
	at org.jruby.internal.runtime.methods.InterpretedMethod.call(InterpretedMethod.java:225)
	at org.jruby.internal.runtime.methods.DefaultMethod.call(DefaultMethod.java:204)
	at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:202)
	at org.jruby.ast.FCallSpecialArgNode.interpret(FCallSpecialArgNode.java:41)
	at org.jruby.ast.CallNoArgNode.interpret(CallNoArgNode.java:64)
	at org.jruby.ast.NewlineNode.interpret(NewlineNode.java:105)
	at org.jruby.evaluator.ASTInterpreter.INTERPRET_METHOD(ASTInterpreter.java:75)
	at org.jruby.internal.runtime.methods.InterpretedMethod.call(InterpretedMethod.java:225)
	at org.jruby.internal.runtime.methods.DefaultMethod.call(DefaultMethod.java:204)
	at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:346)
	at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:204)
	at org.jruby.ast.CallTwoArgNode.interpret(CallTwoArgNode.java:59)
	at org.jruby.ast.NewlineNode.interpret(NewlineNode.java:105)
	at org.jruby.ast.BlockNode.interpret(BlockNode.java:71)
	at org.jruby.ast.IfNode.interpret(IfNode.java:116)
	at org.jruby.ast.NewlineNode.interpret(NewlineNode.java:105)
	at org.jruby.ast.BlockNode.interpret(BlockNode.java:71)
	at org.jruby.evaluator.ASTInterpreter.INTERPRET_METHOD(ASTInterpreter.java:75)
	at org.jruby.internal.runtime.methods.InterpretedMethod.call(InterpretedMethod.java:268)
	at org.jruby.internal.runtime.methods.DefaultMethod.call(DefaultMethod.java:220)
	at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:366)
	at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:238)
	at org.jruby.ast.CallThreeArgNode.interpret(CallThreeArgNode.java:61)
	at org.jruby.ast.NewlineNode.interpret(NewlineNode.java:105)
	at org.jruby.ast.BlockNode.interpret(BlockNode.java:71)
	at org.jruby.ast.RescueNode.executeBody(RescueNode.java:224)
	at org.jruby.ast.RescueNode.interpret(RescueNode.java:119)
	at org.jruby.evaluator.ASTInterpreter.INTERPRET_METHOD(ASTInterpreter.java:75)

[JIRA] [websphere-deployer] (JENKINS-23520) SOAP Connection Exception at 8879

2014-06-20 Thread rdines...@gmail.com (JIRA)

Dinesh Rajendran
created JENKINS-23520

SOAP Connection Exception at 8879

Issue Type:

Bug

Assignee:

Unassigned

Components:

websphere-deployer

Created:

20/Jun/14 5:05 PM

Description:

We are trying to deploy different ear files to 2 different WAS servers using Jenkins. Successful SOAP connection at port 8879 is happening only to one server at a time from Jenkins. Following is the exception we get when we test the connection.

Connection failed: com.ibm.websphere.management.exception.ConnectorException: ADMC0016E: The system cannot create a SOAP connector to connect to host at port 8879.
Caused by: com.ibm.websphere.management.exception.ConnectorNotAvailableException: [SOAPException: faultCode=SOAP-ENV:Client; msg=Error opening socket: java.io.IOException: Exception during sslSocket.startHandshake: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target; targetException=java.lang.IllegalArgumentException: Error opening socket: java.io.IOException: Exception during sslSocket.startHandshake: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target]
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.reconnect(SOAPConnectorClient.java:422)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.(SOAPConnectorClient.java:222)
... 82 more
Caused by: [SOAPException: faultCode=SOAP-ENV:Client; msg=Error opening socket: java.io.IOException: Exception during sslSocket.startHandshake: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target;

For Example: If we have two different WAS app servers A(uses WAS 7) and B(uses WAS 8). Soap connection at port 8879 happens only to one server at a time and the other one fails. Lets say, if Jenkins is restarted and we test the connection to server A first and successful. Then when we try for server B, it fails. Then when we restart Jenkins and try the connection to Server B first and successful. Then if we try for Server A, then it fails.

We have verified the cacerts of JDK1.7 which our Jenkins uses and it has the required certificates entries of both which has been added based on InstallCert.java.

Please advice.

Environment:

jdk1.7.0_45

Project:

Jenkins

Priority:

Critical

Reporter:

Dinesh Rajendran

[JIRA] [disk-usage] (JENKINS-23519) Misspelling in Disk Usage plugin

2014-06-20 Thread exgr...@gmail.com (JIRA)















































Eric Griswold
 created  JENKINS-23519


Misspelling in Disk Usage plugin















Issue Type:


Bug



Assignee:


Lucie Votypkova



Components:


disk-usage



Created:


20/Jun/14 4:53 PM



Description:


In the Disk-Usage plugin (v 0.23) , there is a misspelling of "workspace" as "workpsace" in this message:

  Counting of workpsace disk usage is executing now. 




Project:


Jenkins



Priority:


Trivial



Reporter:


Eric Griswold

























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] [concurrent-build] (JENKINS-23518) GitHub webhooks and concurrent builds don't work

2014-06-20 Thread cfuns...@hotmail.com (JIRA)

Chris Funston
created JENKINS-23518

GitHub webhooks and concurrent builds don't work

Issue Type:

Bug

Assignee:

Kohsuke Kawaguchi

Components:

concurrent-build, github

Created:

20/Jun/14 4:40 PM

Description:

Simple Jenkins configuration, 1 master, no slaves. My project has 1 build trigger: "Build when a change is pushed to GitHub". I also have "Execute concurrent builds if necessary" enabled.

If a new trigger occurrs as a result from a push to GitHub, the concurrent workspace is not created. Jenkins waits until the current request is complete, then starts. If there were 2 queued up, it only executes the 'latest' one.

If I use a custom workspace, the concurrent builds DO work. Unfortunately, I cannot use this option as each of the workspaces need to be unique.

Environment:

Ubuntu 12.04.4

Jenkins Version 1.554.1

Project:

Jenkins

Priority:

Major

Reporter:

Chris Funston

[JIRA] [email-ext] (JENKINS-23517) email-ext plugin doesn't handle tokens when slave has gone offline

2014-06-20 Thread aba...@java.net (JIRA)















































abayer
 created  JENKINS-23517


email-ext plugin doesn't handle tokens when slave has gone offline















Issue Type:


Bug



Assignee:


Alex Earl



Components:


email-ext, token-macro



Created:


20/Jun/14 4:37 PM



Description:


We've been having a problem lately with some of our cloud slaves getting killed during the build - when this happens, email-ext/token-macro fails to actually transform any tokens, ending up with a useless email. Here's the stacktrace from the logs:


Jun 20, 2014 2:34:35 AM hudson.plugins.emailext.plugins.ContentBuilder transformText
SEVERE: null
java.lang.IllegalArgumentException: Node ec2-beefy-slave-406.vpc.cloudera.com seems to be offline
at hudson.tools.ToolInstaller.preferredLocation(ToolInstaller.java:120)
at hudson.tools.JDKInstaller.performInstallation(JDKInstaller.java:109)
at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:61)
at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:107)
at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:204)
at hudson.model.JDK.forNode(JDK.java:126)
at hudson.model.AbstractProject.getEnvironment(AbstractProject.java:359)
at hudson.model.Run.getEnvironment(Run.java:2173)
at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:914)
at org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(TokenMacro.java:229)
at hudson.plugins.emailext.plugins.ContentBuilder.transformText(ContentBuilder.java:71)
at hudson.plugins.emailext.ExtendedEmailPublisher.setSubject(ExtendedEmailPublisher.java:585)
at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:473)
at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:290)
at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:281)
at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:233)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:757)
at hudson.model.Build$BuildExecution.cleanUp(Build.java:192)
at hudson.model.Run.execute(Run.java:1710)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:246)





Environment:


Jenkins 1.532.2, email-ext 2.38, token-macro 1.10




Project:


Jenkins



Priority:


Critical



Reporter:


abayer

























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] [git] (JENKINS-23511) InvalidClassException for SSHAuthenticator$1 when doing a git clone on an AIX slave

2014-06-20 Thread cl...@exiter.com (JIRA)

Robert Clark
edited a comment on JENKINS-23511

InvalidClassException for SSHAuthenticator$1 when doing a git clone on an AIX slave

The Java version, and AIX version with patch level is in the "Environment" section. I've not yet seen this on any other platform (including HP-UX, which is another non-Oracle JVM) so I'm not yet sure how to reproduce this somewhere sane.

I'm still working on this and I'll update the issue if I discover anything new.

I was poking around in the source code and, as a wild-ass guess, I think putting an serialVersionUID = 1 in the anonymous inner class in SSHAuthenticator.newInstance() might be the correct solution. I know we've had trouble in the past with different default serialVersionUIDs from different VMs when doing any kind of RMI.

Edit: I've not tried it yet, but I think an IBM VM (http://www.ibm.com/developerworks/java/jdk/) running on Linux might show the same behaviour. That would at least take AIX out of the mix. I'll see if I can break loose some time to experiment with that.

[JIRA] [jacoco] (JENKINS-23516) Support matching JARs as class "directories" in class pattern

2014-06-20 Thread chris.a.willi...@gmail.com (JIRA)















































Chris Williams
 created  JENKINS-23516


Support matching JARs as class "directories" in class pattern















Issue Type:


Improvement



Assignee:


Ognjen Bubalo



Components:


jacoco



Created:


20/Jun/14 4:15 PM



Description:


We use Jenkins to build Eclipse plugins. This plugins typically end up as JARs. Right now when I want to get coverage I point at the eclipse/plugins dir as my classPattern and use inclusion/exclusion patterns to choose which JARs I care about (to filter out the base eclipse ones). The problem is that it ends up copying then entire eclipse plugins directory to the build's jacoco/classes dir and post filtering. This results in taking up huge amounts of disk space for JARs we never care about for coverage.




Project:


Jenkins



Priority:


Major



Reporter:


Chris Williams

























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] [jacoco] (JENKINS-23515) Support exclusions inside JAR files

2014-06-20 Thread chris.a.willi...@gmail.com (JIRA)















































Chris Williams
 created  JENKINS-23515


Support exclusions inside JAR files















Issue Type:


Improvement



Assignee:


Ognjen Bubalo



Components:


jacoco



Created:


20/Jun/14 4:07 PM



Description:


We use Jenkins to do CI on eclipse plugins we develop. It's common for Eclipse plugins to use a Messages class to hold externalized UI strings, and to keep the plugins packaged as JARs. As a result, my coverage reports include this translation string class in them, messing with my coverage counts. I'd love the ability to exclude classes/packages inside JARs similar to how zipfileset through ant works with Jacoco.




Project:


Jenkins



Priority:


Major



Reporter:


Chris Williams

























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] [security] (JENKINS-17060) Jenkins errors when 'Remember me on this computer' is checked.

2014-06-20 Thread martin.cass...@gamma.co.uk (JIRA)















































Martin Cassidy
 commented on  JENKINS-17060


Jenkins errors when 'Remember me on this computer' is checked.















I'm getting this same issue when using remember me with the crowd 2 plugin.



























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] [git] (JENKINS-23511) InvalidClassException for SSHAuthenticator$1 when doing a git clone on an AIX slave

2014-06-20 Thread cl...@exiter.com (JIRA)















































Robert Clark
 commented on  JENKINS-23511


InvalidClassException for SSHAuthenticator$1 when doing a git clone on an AIX slave















The Java version, and AIX version with patch level is in the "Environment" section. I've not yet seen this on any other platform (including HP-UX, which is another non-Oracle JVM) so I'm not yet sure how to reproduce this somewhere sane.

I'm still working on this and I'll update the issue if I discover anything new.

I was poking around in the source code and, as a wild-ass guess, I think putting an serialVersionUID = 1 in the anonymous inner class in SSHAuthenticator.newInstance() might be the correct solution. I know we've had trouble in the past with different default serialVersionUIDs from different VMs when doing any kind of RMI.



























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-23514) Deadlock in Xstream at Jenkins startup

2014-06-20 Thread clecl...@cloudbees.com (JIRA)















































Cyrille Le Clerc
 created  JENKINS-23514


Deadlock in Xstream at Jenkins startup















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Attachments:


deadlock.log, jebc-startup-logs-deadlock.log



Components:


core



Created:


20/Jun/14 3:01 PM



Description:


Deadlock in com.thoughtworks.xstream.mapper.AnnotationMapper when Jenkins loads folders (see thread dump fragment, "www", "mobile" and "admin"are Jenkins folders).

Deadlock occur systematically when the stdout and stderr are routed to the shell console. The workaround is to route stdout and stderr to a file.

Attached:


	jenkins-startup.log: jenkins stdout & stderr
	deadlock.log: threaddump highlighting the dead lock in XStream






Java stack information for the threads listed above:
===
"Loading job www":
	at java.lang.Class.initAnnotationsIfNecessary(Class.java:3175)
	- waiting to lock <0x0007e22586b0> (a java.lang.Class for hudson.model.Job)
	at java.lang.Class.getAnnotation(Class.java:3137)
	at com.thoughtworks.xstream.mapper.AnnotationMapper$UnprocessedTypesSet.add(AnnotationMapper.java:625)
	at com.thoughtworks.xstream.mapper.AnnotationMapper$UnprocessedTypesSet.add(AnnotationMapper.java:610)
	at com.thoughtworks.xstream.mapper.AnnotationMapper.processAnnotations(AnnotationMapper.java:181)
	at com.thoughtworks.xstream.mapper.AnnotationMapper.getLocalConverter(AnnotationMapper.java:153)
	at com.thoughtworks.xstream.mapper.MapperWrapper.getLocalConverter(MapperWrapper.java:99)
	at hudson.util.xstream.MapperDelegate.getLocalConverter(MapperDelegate.java:112)
	at com.thoughtworks.xstream.mapper.MapperWrapper.getLocalConverter(MapperWrapper.java:99)
	at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:348)
	at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:289)
	at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:228)
	at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)
	at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)
	at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)
	at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50)
	at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134)
	at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32)
	at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1189)
	at hudson.util.XStream2.unmarshal(XStream2.java:113)
	at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1173)
	at com.thoughtworks.xstream.XStream.fromXML(XStream.java:1053)
	at hudson.XmlFile.read(XmlFile.java:142)
	at hudson.model.Items.load(Items.java:275)
	at hudson.model.ItemGroupMixIn.loadChildren(ItemGroupMixIn.java:105)
	at com.cloudbees.hudson.plugins.folder.Folder.onLoad(Folder.java:238)
	at hudson.model.Items.load(Items.java:276)
	at jenkins.model.Jenkins$18.run(Jenkins.java:2588)
	at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
	at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
	at jenkins.model.Jenkins$7.runTask(Jenkins.java:899)
	at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
	at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)
"Loading job admin":
	at java.lang.Class.initAnnotationsIfNecessary(Class.java:3175)
	- waiting to lock <0x0007e1dce000> (a java.lang.Class for hudson.model.Run)
	at java.lang.Class.getAnnotation(Class.java:3137)
	at com.thoughtworks.xstream.mapper.AnnotationMapper$UnprocessedTypesSet.add(AnnotationMapper.java:625)
	at com.though

[JIRA] [git] (JENKINS-23511) InvalidClassException for SSHAuthenticator$1 when doing a git clone on an AIX slave

2014-06-20 Thread mark.earl.wa...@gmail.com (JIRA)















































Mark Waite
 commented on  JENKINS-23511


InvalidClassException for SSHAuthenticator$1 when doing a git clone on an AIX slave















Can you provide more details on the AIX environment where you're seeing the problem?

I doubt that any of the maintainers have access to an AIX machine, so we'll probably need to know details like which JDK is used on the AIX machine, and its version, and if there is some way to see the same results on a platform that is accessible to the plugin maintainers.



























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] [configurationslicing] (JENKINS-23476) git-client plugin timeout default is not configurable in a standard manner

2014-06-20 Thread mark.earl.wa...@gmail.com (JIRA)















































Mark Waite
 updated  JENKINS-23476


git-client plugin timeout default is not configurable in a standard manner
















Change By:


Mark Waite
(20/Jun/14 2:46 PM)




Issue Type:


Bug
Improvement



























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] [claim] (JENKINS-23513) Claim plugin doesn't allow you to claim unstable builds.

2014-06-20 Thread brian.sm...@novatel.com (JIRA)















































Brian Smith
 created  JENKINS-23513


Claim plugin doesn't allow you to claim unstable builds.















Issue Type:


Improvement



Affects Versions:


current



Assignee:


Christian Åkerström



Components:


claim



Created:


20/Jun/14 2:43 PM



Description:


It would be nice if the Claim plugin could be used with Unstable builds (at least all of my testing has indicated that it doesn't allow you to claim unstable builds)




Environment:


Windows Server, Windows Nodes, Linux Nodes, Jenkins 1.554.2, Claim Plugin 2.3




Project:


Jenkins



Priority:


Major



Reporter:


Brian Smith

























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] [display-upstream-changes] (JENKINS-23512) 'detail' link in upstream change leads to blank page

2014-06-20 Thread rob.pe...@gmail.com (JIRA)
















































Rob Petti
 assigned  JENKINS-23512 to Unassigned



'detail' link in upstream change leads to blank page
















Change By:


Rob Petti
(20/Jun/14 2:41 PM)




Assignee:


Rob Petti



























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] [display-upstream-changes] (JENKINS-23512) 'detail' link in upstream change leads to blank page

2014-06-20 Thread rema...@alum.wpi.edu (JIRA)















































Rob Mandeville
 created  JENKINS-23512


'detail' link in upstream change leads to blank page















Issue Type:


Bug



Affects Versions:


current



Assignee:


Rob Petti



Components:


display-upstream-changes



Created:


20/Jun/14 1:52 PM



Description:


In the upstream changes section of a build, each upstream change has a "detail" link.  This links to a URL based on the run of the current "downstream" job rather than the upstream job.  So if job downstream #22 is launched by the job upstream #14, the link we get is

http://somehost/jenkins/job/downstream/22/changes#detail0

When we really need

http://somehost/jenkins/job/upstream/14/changes#detail0

As a result, clicking the "detail" link of the downstream job takes you to a no-content Jenkins page.




Environment:


Display Upstream changes Plugin 0.1

Jenkins 1.554

Internal (jetty) container

OpenJDK 64-Bit Server VM (java version 1.7.0_51)

Linux ubuntu 3.11.0-18-generic






Project:


Jenkins



Priority:


Minor



Reporter:


Rob Mandeville

























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] [git] (JENKINS-23511) InvalidClassException for SSHAuthenticator$1 when doing a git clone on an AIX slave

2014-06-20 Thread cl...@exiter.com (JIRA)















































Robert Clark
 created  JENKINS-23511


InvalidClassException for SSHAuthenticator$1 when doing a git clone on an AIX slave















Issue Type:


Bug



Affects Versions:


current



Assignee:


Nicolas De Loof



Components:


git, ssh-credentials



Created:


20/Jun/14 1:49 PM



Description:


Attempting to clone a git repo at the start of a build on an AIX slave. 
This exception was triggered:


FATAL: Failed to fetch from ssh://@/.git
hudson.plugins.git.GitException: Failed to fetch from ssh://@/.git
   at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:623)
   at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:855)
   at hudson.plugins.git.GitSCM.checkout(GitSCM.java:880)
   at hudson.model.AbstractProject.checkout(AbstractProject.java:1411)
   at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652)
   at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
   at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:561)
   at hudson.model.Run.execute(Run.java:1665)
   at hudson.matrix.MatrixRun.run(MatrixRun.java:146)
   at hudson.model.ResourceController.execute(ResourceController.java:88)
   at hudson.model.Executor.run(Executor.java:246)
Caused by: hudson.plugins.git.GitException: org.eclipse.jgit.api.errors.TransportException: ssh://@/.git: Failed to connect
   at org.jenkinsci.plugins.gitclient.JGitAPIImpl$2.execute(JGitAPIImpl.java:460)
   at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
   at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
   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 java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:345)
   at java.util.concurrent.FutureTask.run(FutureTask.java:177)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1121)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:614)
   at java.lang.Thread.run(Thread.java:769)
Caused by: org.eclipse.jgit.api.errors.TransportException: ssh://@/.git: Failed to connect
   at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:139)
   at org.jenkinsci.plugins.gitclient.JGitAPIImpl$2.execute(JGitAPIImpl.java:458)
   ... 11 more
Caused by: org.eclipse.jgit.errors.TransportException: ssh://@/.git: Failed to connect
   at org.jenkinsci.plugins.gitclient.trilead.TrileadSessionFactory.getSession(TrileadSessionFactory.java:53)
   at org.eclipse.jgit.transport.SshTransport.getSession(SshTransport.java:121)
   at org.eclipse.jgit.transport.TransportGitSsh$SshFetchConnection.(TransportGitSsh.java:248)
   at org.eclipse.jgit.transport.TransportGitSsh.openFetch(TransportGitSsh.java:147)
   at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:136)
   at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:122)
   at org.eclipse.jgit.transport.Transport.fetch(Transport.java:)
   at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:130)
   ... 12 more
Caused by: java.io.InvalidClassException: com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator$1; local class incompatible: stream classdesc serialVersionUID = 4226456448964168241, local class serialVersionUID = 8217644684038495097
at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:604)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1620)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1515)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1769)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
at hudson.remoting.UserRequest.dese

[JIRA] [build-pipeline] (JENKINS-22146) Infinite recursion when the pipeline involves joined jobs triggering the same child job















































Régis Desgroppes
 updated  JENKINS-22146


Infinite recursion when the pipeline involves joined jobs triggering the same child job
















Here's a patch fixing the infinite recursion by stopping when encountering the very same project for the second time.





Change By:


Régis Desgroppes
(20/Jun/14 1:40 PM)




Attachment:


JENKINS-22146.patch



























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] [configurationslicing] (JENKINS-23510) Support for NodeLabel Parameter plugin in the Configuration Slicing plugin

2014-06-20 Thread tim.debacker....@gmail.com (JIRA)















































Tim De Backer
 created  JENKINS-23510


Support for NodeLabel Parameter plugin in the Configuration Slicing plugin















Issue Type:


Improvement



Assignee:


mdonohue



Components:


configurationslicing, nodelabelparameter



Created:


20/Jun/14 1:31 PM



Description:


The NodeLabel parameter plugin provides a new type of parameter. It would be nice to support this parameter type in the Configuration Slicing plugin!




Project:


Jenkins



Priority:


Major



Reporter:


Tim De Backer

























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] [build-pipeline] (JENKINS-22146) Infinite recursion when the pipeline involves joined jobs triggering the same child job















































Régis Desgroppes
 commented on  JENKINS-22146


Infinite recursion when the pipeline involves joined jobs triggering the same child job















With setup #1, the pipeline plugin traverses the projects the following way:

build -> test1 -> release.
  -> test2 -> release.


With setup #2, the pipeline plugin traverses the projects the following way:

build -> test1 -> release -> notify -> release -> notify -> ... (until stack overflows)

... because "notify" is considered as both a child (explicitly) and parent (implicitly, from the "join" trigger) of "release".



























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-17116) gracefull job termination

2014-06-20 Thread martin.danjo...@gmail.com (JIRA)

Martin d'Anjou
commented on JENKINS-17116

gracefull job termination

There is more to it than cleaning up the orphaned processes, which by the way should be done by Jenkins and not as an external process. The way this should work is that Jenkins should send the signal (SIGTERM or SIGTERM) and wait for the sub-processes to do their own cleanup. This gives the sub-processes a chance to propagate the signal to sub-sub-processes of their own (which by the way when you use a grid engine, might be running yet on other remote machines that are not Jenkins slaves).

I modified the first shell script to write to a file during the traps: Jenkins cuts the ties too early and no files show up anywhere.

#!/bin/bash
echo "Starting $0"
echo "Listing traps"
trap -p
echo "Setting trap"
trap 'echo SIGTERM | tee trap.sigterm; kill $pid; exit 15;' SIGTERM
trap 'echo SIGINT | tee trap.sigint; kill $pid; exit 2;' SIGINT
echo "Listing traps again"
trap -p
echo "Sleeping"
sleep 20 & pid=$!
echo "Waiting"
wait $pid
echo "Exit status: $?"
echo "Ending"

So the SIGINT -> wait N seconds for the build process to return -> SIGKILL (with a user configurable N) would be an acceptable solution. The value of N should be configurable for each job.

[JIRA] [dashboard-view] (JENKINS-20723) Add an option to include or exclude disabled jobs in the 'Unstable jobs' widget.

2014-06-20 Thread tim.debacker....@gmail.com (JIRA)















































Tim De Backer
 commented on  JENKINS-20723


Add an option to include or exclude disabled jobs in the 'Unstable jobs' widget.















Is there any progress on this? Thanks!



























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] [envinject] (JENKINS-17827) An intuïtive way to pass a variable/parameter (e.g. multijob build number) to all its downstream jobs.

2014-06-20 Thread tim.debacker....@gmail.com (JIRA)















































Tim De Backer
 commented on  JENKINS-17827


An intuïtive way to pass a variable/parameter (e.g. multijob build number) to all its downstream jobs. 















Is there any progress on this already? Thanks!



























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] [jenkins-multijob-plugin] (JENKINS-20468) Multijob should provide configuration option to be a flyweight tasks

2014-06-20 Thread tim.debacker....@gmail.com (JIRA)















































Tim De Backer
 commented on  JENKINS-20468


Multijob should provide configuration option to be a flyweight tasks















This would be very helpful indeed. We have a set-up in which only one job may run at the same time. We are combining this plugin with the NodeLabel Parameter plugin so all jobs of the MultiJob are run on the same node. However, the MultiJob itself takes up the single executor on that node!



























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] [testng] (JENKINS-20985) TestNG plugin should has a possibility to use thresholds for failed tests

2014-06-20 Thread gat...@java.net (JIRA)















































gatrot
 commented on  JENKINS-20985


TestNG plugin should has a possibility to use thresholds for failed tests















I lost some steam after the back and forth in January.  I'll pick it up again next week and send out a pull 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] [svnmerge] (JENKINS-23371) Manually-triggered integration

2014-06-20 Thread chris.pla...@gmail.com (JIRA)















































Chris Platts
 reopened  JENKINS-23371


Manually-triggered integration
















Reopening because the option to reintegrate isn't showing on a project and can't tell why





Change By:


Chris Platts
(20/Jun/14 11:50 AM)




Resolution:


Not A Defect





Status:


Resolved
Reopened



























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.

SSH authentication with Username and Password

2014-06-20 Thread andrerohrbeck

Hi,

Probably I am missing something basic, but I have troubles connecting to my
GIT-Repo hosted on Mac OS X Server (10.9 Mavericks) using Jenkins through
SSH.

Connecting to the Repo via SSH using Username/Password is possible, but I
haven't managed it yet to connect by using public/private key method (OS X
Server keeps asking me for a password, even if the SSH-Keys are available).
Thus logging in from Jenkins through SSH with Username/password would be my
preferred option.

According to the documentation of the SSH Slaves
plugin I
would expect an option "SSH Username with Password" when creating a new
credential. But this option doesn't show up in my Jenkins Installation
(Core. 1.568, SSH Credentials: 1.71, SSH Slaves 1.5). Only "Username with
Password" (without "SSH"), "Apple Developer Profile", "SSH Username with
Private Key" and "Certificate" are shown in the menu?

Am I missing something basic?
Is "Username with Password" Credential type supposed to work also with SSH
connections?
Was SSH Username/password support dropped?

Thanks for your help!

André

--
View this message in context:
http://jenkins-ci.361315.n4.nabble.com/SSH-authentication-with-Username-and-Password-tp4707273.html
Sent from the Jenkins issues mailing list archive at Nabble.com.

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

[JIRA] [ant] (JENKINS-23387) Build Failure report is missing

2014-06-20 Thread niall.n.brown...@aegon.co.uk (JIRA)
















































Niall Brownlee
 resolved  JENKINS-23387 as Not A Defect


Build Failure report is missing
















This was caused by a Salesforce API issue which was resolved by Salesforce Summer Patch release 7.0





Change By:


Niall Brownlee
(20/Jun/14 10:56 AM)




Status:


Open
Resolved





Resolution:


Not A Defect



























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] [ant] (JENKINS-23387) Build Failure report is missing

2014-06-20 Thread niall.n.brown...@aegon.co.uk (JIRA)
















































Niall Brownlee
 closed  JENKINS-23387 as Not A Defect


Build Failure report is missing
















Change By:


Niall Brownlee
(20/Jun/14 10:56 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] [build-pipeline] (JENKINS-22146) Infinite recursion when the pipeline involves joined jobs triggering the same child job













































  
Régis Desgroppes
 edited a comment on  JENKINS-22146


Infinite recursion when the pipeline involves joined jobs triggering the same child job
















Our initial setup was rather simple:

1
 ⎧ test1⎫
build ⎯→ ⎨ test2⎬ ⎯→ release
 ⎩ .⎭

... and supported by the build pipeline view.

Then we inserted the notification job everywhere:

2
 ⎧ test1⎫
 ⎪ ↪ notify ⎪
build ⎯→ ⎨ test2⎬ ⎯→ release
↪ notify ⎪ ↪ notify ⎪↪ notify
 ⎩ .⎭

... and the build pipeline view entered an infinite loop.



























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-23232) SEVERE: I/O error in channel Chunked connection

2014-06-20 Thread manjias...@googlemail.com (JIRA)















































Ashok Manji
 commented on  JENKINS-23232


SEVERE: I/O error in channel Chunked connection















@Daniel - There were no occurrences of "-Dhudson.diyChunking=true" in my startup scripts, yet this is set as true (even though the default is false)
I followed Peter's comment above to set this property to 'false' in /etc/sysconfig/jenkins and this has resolved the reported problem.



























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] [build-monitor] (JENKINS-23506) URLs in Build-Monitor-Plugin view are broken if Cloudbees-Folders-Plugin is in use

2014-06-20 Thread ed.rand...@ingenotech.com (JIRA)















































Ed Randall
 commented on  JENKINS-23506


URLs in Build-Monitor-Plugin view are broken if Cloudbees-Folders-Plugin is in use















A sub-folder URL containing some actual projects (jobs):
http://hostname/view/Web.Projects/job/Web.Projects.XYZ.trunk/

Link to a monitor view created at that sub-folder level:
http://hostname/view/Web.Projects/job/Web.Projects.XYZ.trunk/view/XYZMonitor/

Link from square on monitor view to a job:
http://hostname/view/Web.Projects/job/Web.Projects.XYZ.trunk/view/XYZMonitor/job/Web.Projects.XYZ.trunk/job/xyz_server.checkin/
But that link should actually be:
http://hostname/view/Web.Projects/job/Web.Projects.XYZ.trunk/job/xyz_server.checkin/


If I try to create and configure a view at the top level:
http://hostname/view/XYZMonitor2/configure
Only the folder "Web.Projects.XYZ.trunk" is offered as a "job", none of the real jobs are visible;
Select it anyway and click OK; the view appears with text: 
It seems a bit empty here... Maybe you'd like to add some jobs to this monitor?
The link takes you back to http://hostname/view/XYZMonitor2/configure





























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-7695) archiving throws hudson.util.IOException2: java.io.IOException: request to write '3977' bytes exceeds size in header of '41955006'

2014-06-20 Thread jakub.czapli...@gmail.com (JIRA)















































Jakub Czaplicki
 commented on  JENKINS-7695


archiving throws hudson.util.IOException2: java.io.IOException: request to write '3977' bytes exceeds size in header of '41955006'















I am seeing this issue in 1.555 :


11:12:54 ERROR: Failed to archive artifacts: *.log
11:12:54 java.io.IOException: java.util.concurrent.ExecutionException: java.io.IOException: request to write '8192' bytes exceeds size in header of '26982170' bytes for entry 'output.log'
11:12:54 	at hudson.FilePath.copyRecursiveTo(FilePath.java:2017)
11:12:54 	at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:57)
11:12:54 	at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:140)
11:12:54 	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
11:12:54 	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804)
11:12:54 	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776)
11:12:54 	at hudson.model.Build$BuildExecution.post2(Build.java:183)
11:12:54 	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:725)
11:12:54 	at hudson.model.Run.execute(Run.java:1701)
11:12:54 	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
11:12:54 	at hudson.model.ResourceController.execute(ResourceController.java:88)
11:12:54 	at hudson.model.Executor.run(Executor.java:231)
11:12:54 Caused by: java.util.concurrent.ExecutionException: java.io.IOException: request to write '8192' bytes exceeds size in header of '26982170' bytes for entry 'output.log'
11:12:54 	at hudson.remoting.Channel$3.adapt(Channel.java:755)
11:12:54 	at hudson.remoting.Channel$3.adapt(Channel.java:750)
11:12:54 	at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55)
11:12:54 	at hudson.FilePath.copyRecursiveTo(FilePath.java:2015)
11:12:54 	... 11 more
11:12:54 Caused by: java.io.IOException: request to write '8192' bytes exceeds size in header of '26982170' bytes for entry 'output.log'
11:12:54 	at hudson.org.apache.tools.tar.TarOutputStream.write(TarOutputStream.java:284)
11:12:54 	at hudson.util.io.TarArchiver.visit(TarArchiver.java:114)
11:12:54 	at hudson.util.DirScanner.scanSingle(DirScanner.java:49)
11:12:54 	at hudson.FilePath$ExplicitlySpecifiedDirScanner.scan(FilePath.java:2541)
11:12:54 	at hudson.FilePath.writeToTar(FilePath.java:2053)
11:12:54 	at hudson.FilePath.access$1000(FilePath.java:172)
11:12:54 	at hudson.FilePath$41.invoke(FilePath.java:1994)
11:12:54 	at hudson.FilePath$41.invoke(FilePath.java:1990)
11:12:54 	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2462)
11:12:54 	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
11:12:54 	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
11:12:54 	at hudson.remoting.Request$2.run(Request.java:328)
11:12:54 	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
11:12:54 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
11:12:54 	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
11:12:54 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
11:12:54 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
11:12:54 	at java.lang.Thread.run(Thread.java:662)
11:12:54 Build step 'Archive the artifacts' changed build result to FAILURE




























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] [golang] (JENKINS-23509) Go versions newer than 1.2.1 cannot be installed















































Christopher Orr
 created  JENKINS-23509


Go versions newer than 1.2.1 cannot be installed















Issue Type:


Bug



Assignee:


Christopher Orr



Components:


golang



Created:


20/Jun/14 10:22 AM



Description:


Any installations attempted from the new golang.org/dl/ site will fail (i.e. Go 1.2.2. Go 1.3 and newer).

This is because the JSON contains a URL like "http://golang.org/dl/..." but this is actually an HTTP 302 redirect to somewhere else.

Jenkins cannot handle HTTP 30x redirects when downloading tools automatically, so this fails — see JENKINS-23507.

Until that is fixed, the temporary workaround should be to have the backend-crawler follow the redirects, so that Jenkins doesn't have to follow them.
But this is fragile and not a good idea in general (i.e. we don't want to be breaking mirror networks etc.).




Project:


Jenkins



Priority:


Major



Reporter:


Christopher Orr

























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-23508) Duplicated status info for many projects on dashboard

2014-06-20 Thread lluis.gar...@gmail.com (JIRA)

Lluís M. García
created JENKINS-23508

Duplicated status info for many projects on dashboard

Issue Type:

Bug

Affects Versions:

current

Assignee:

Unassigned

Attachments:

Screen Shot 2014-06-20 at 11.15.44.png

Components:

core

Created:

20/Jun/14 10:18 AM

Description:

I was using Jenkins with a single project/job with no issues.

Recently added a new project/job and strange things started to happen.

In the beginning builds were shared among both projects and showing as if they were part of both. I cloned the jobs to try to fix the issues but didn't helped.

After some copies, restarts and re-reads of config from disk I got it to a state where at least builds show separately for each project but project status is shared between the two I have now.

You can see this in the screenshot attached.

I'm using version: 1.568

Project:

Jenkins

Priority:

Minor

Reporter:

Lluís M. García

[JIRA] [core] (JENKINS-23507) FilePath.installIfNecessaryFrom does not follow HTTP 30x redirects















































Christopher Orr
 created  JENKINS-23507


FilePath.installIfNecessaryFrom does not follow HTTP 30x redirects















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


20/Jun/14 10:17 AM



Description:


I'm using a tool installer which, for some downloads, the URL returns a 302 redirect.

However, Jenkins reads the contents of the redirect page (i.e. some text like "This page has moved to http://foo/bar") and attempts to parse that as the zip/tar/whatever file.

The stacktrace users see when this happens is pretty cryptic:


Unpacking Go from http://golang.org/dl/go1.3.darwin-amd64-osx10.6.tar.gz to /Users/Shared/Jenkins/Home/tools/org.jenkinsci.plugins.golang.GolangInstallation/Go_1.3 on Jenkins
FATAL: Failed to install http://golang.org/dl/go1.3.darwin-amd64-osx10.6.tar.gz to /Users/Shared/Jenkins/Home/tools/org.jenkinsci.plugins.golang.GolangInstallation/Go_1.3
hudson.util.IOException2: Failed to install http://golang.org/dl/go1.3.darwin-amd64-osx10.6.tar.gz to /Users/Shared/Jenkins/Home/tools/org.jenkinsci.plugins.golang.GolangInstallation/Go_1.3
	at hudson.FilePath.installIfNecessaryFrom(FilePath.java:768)
	at org.jenkinsci.plugins.golang.GolangInstaller.performInstallation(GolangInstaller.java:53)
	at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:61)
	at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:107)
	at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:204)
	at org.jenkinsci.plugins.golang.GolangInstallation.forNode(GolangInstallation.java:41)
	at org.jenkinsci.plugins.golang.GolangBuildWrapper.setUp(GolangBuildWrapper.java:34)
...
Caused by: hudson.util.IOException2: Failed to unpack http://golang.org/dl/go1.3.darwin-amd64-osx10.6.tar.gz (28 bytes read of total -1)
	at hudson.FilePath.installIfNecessaryFrom(FilePath.java:762)
	... 12 more
Caused by: hudson.util.IOException2: Failed to extract input stream
	at hudson.FilePath.readFromTar(FilePath.java:2071)
	...
Caused by: java.io.IOException: incorrect header check
	at com.jcraft.jzlib.InflaterInputStream.read(InflaterInputStream.java:112)
	at org.apache.tools.tar.TarBuffer.readBlock(TarBuffer.java:257)
	...



I will try and fix the tool installer in question to resolve the end URL, but this isn't a great idea in the long run — Jenkins should follow the 30x redirects itself.




Project:


Jenkins



Priority:


Major



Reporter:


Christopher Orr

























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] [build-monitor] (JENKINS-23506) URLs in Build-Monitor-Plugin view are broken if Cloudbees-Folders-Plugin is in use

2014-06-20 Thread ed.rand...@ingenotech.com (JIRA)















































Ed Randall
 created  JENKINS-23506


URLs in Build-Monitor-Plugin view are broken if Cloudbees-Folders-Plugin is in use















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


build-monitor



Created:


20/Jun/14 10:15 AM



Description:


Using:
Build Monitor Plugin version 1.4+build.102 
Cloudbees Folders plugin 4.2.1
Jenkins 1.554.2

We have many jobs hence we categorize them using subfolders using Cloudbees Folders plugin.

The Builc Monitor View, if created at the top level, can't be configured to see the jobs at all.  You get a blank view.
If created at the subfolder level where the jobs exist, it can see them, but the links to each project is incorrect.




Project:


Jenkins



Labels:


plugin
build-monitor-plugin




Priority:


Major



Reporter:


Ed Randall

























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] [golang] (JENKINS-23505) Wrong package for OS X version detected















































Christopher Orr
 commented on  JENKINS-23505


Wrong package for OS X version detected















Looking at the JSON, Go 1.3 lists the 10.6 package before the one for 10.8.
However, Go 1.2.1 (on the old download site) lists 10.8 before 10.6.

Looking at the code, we naively return the first package for which our os.version is higher...



























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] [golang] (JENKINS-23505) Wrong package for OS X version detected















































Christopher Orr
 created  JENKINS-23505


Wrong package for OS X version detected















Issue Type:


Bug



Assignee:


Christopher Orr



Components:


golang



Created:


20/Jun/14 9:55 AM



Description:


Testing on three different OS X machines (including the master), I see this in the build console output:

Unpacking Go from http://golang.org/dl/go1.3.darwin-amd64-osx10.6.tar.gz



However, these machines all have 10.9.3, so should install the "osx10.8" package.

System properties on the tested slaves are identical:

os.arch x86_64
os.name	Mac OS X
os.version  10.9.3






Project:


Jenkins



Priority:


Major



Reporter:


Christopher Orr

























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] [active-directory] (JENKINS-22561) publish-over-cifs should be able to use Jenkins session credentials - including domain when Jenkins Active Directory authentication is used

2014-06-20 Thread s...@liddicott.com (JIRA)















































Sam Liddicott
 commented on  JENKINS-22561


publish-over-cifs should be able to use Jenkins session credentials - including domain when Jenkins Active Directory authentication is used















Nudge,bump. 30 days to go. If $50 is too low, does anyone want to negotiate?



























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] [ssh-agent] (JENKINS-23504) SSH Agent Plugin - Infinite Thread - Thread Hangs - Thread stuck

2014-06-20 Thread carsu...@fullsix.com (JIRA)















































Thomas Carsuzan
 commented on  JENKINS-23504


SSH Agent Plugin - Infinite Thread - Thread Hangs - Thread stuck















The ssh agent still works perfectly but after several builds, several threads will be created and stuck in the jvm and you may have this error :

OutOfMemoryError: unable to create new native thread



























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] [ssh-agent] (JENKINS-23504) SSH Agent Plugin - Infinite Thread - Thread Hangs - Thread stuck

2014-06-20 Thread carsu...@fullsix.com (JIRA)















































Thomas Carsuzan
 created  JENKINS-23504


SSH Agent Plugin - Infinite Thread - Thread Hangs - Thread stuck















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


ssh-agent



Created:


20/Jun/14 9:17 AM



Description:


For every build, SSH Client plugin create a thread that never ends.
It seems to come from this class :
com/cloudbees/jenkins/plugins/sshagent/jna/AgentServer.java

AgentServer.java
thread = new Thread() {
public void run() {
try {
while (!stopped) {
final UnixSocketChannel clientSock = channel.accept();
clientSock.configureBlocking(true);
new SshAgentSession(clientSock, agent);
}
} catch (Exception e) {
if (!stopped) {
e.printStackTrace();
}
}
}
};


I do not really understand the while loop necessity here. The thread will hang in the "channel.accept()" method only the second time it passes in.

Here is the stack :

"Thread-2000" prio=10 tid=0x40e2f800 nid=0x527e runnable [0x7ff5ec313000]
   java.lang.Thread.State: RUNNABLE
	at com.kenai.jffi.Foreign.invokeN3O2(Native Method)
	at com.kenai.jffi.Invoker.invokeN3(Invoker.java:1092)
	at jnr.unixsocket.Native$LibC$jnr$ffi$0.accept(Unknown Source)
	at jnr.unixsocket.Native.accept(Native.java:91)
	at jnr.unixsocket.UnixServerSocketChannel.accept(UnixServerSocketChannel.java:56)
	at com.cloudbees.jenkins.plugins.sshagent.jna.AgentServer$1.run(AgentServer.java:77)






Environment:


Unix/RedHat6.5/Jenkins1.568/SSHClient 1.4.1




Project:


Jenkins



Priority:


Major



Reporter:


Thomas Carsuzan

























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] [build-pipeline] (JENKINS-22146) Infinite recursion when the pipeline involves joined jobs triggering the same child job