date:20130702















































SCM/JIRA link daemon
 commented on  JENKINS-18329


ConcurrentModificationException during pooling in version 2.9















Code changed in jenkins
User: Sascha Vogt
Path:
 src/main/java/hudson/scm/AbstractCvs.java
http://jenkins-ci.org/commit/cvs-plugin/c59089bf24ae828a1367f85732392f2f4a5cb2a5
Log:
  FIXED JENKINS-18329 - Prevent ConcurrentModificationException

Replace Iterator with ListIterator and use iterator methods for adding
and removing. This should fix any ConcurrentModificationExceptions





























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







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

[JIRA] [cvs] (JENKINS-18329) ConcurrentModificationException during pooling in version 2.9















































SCM/JIRA link daemon
 commented on  JENKINS-18329


ConcurrentModificationException during pooling in version 2.9















Code changed in jenkins
User: Michael Clarke
Path:
 src/main/java/hudson/scm/AbstractCvs.java
http://jenkins-ci.org/commit/cvs-plugin/839a9f84d88f9a6bdce09e915e47e0827dc94b84
Log:
  Merge pull request #22 from svogt/JENKINS-18329

FIXED JENKINS-18329 - Prevent ConcurrentModificationException


Compare: https://github.com/jenkinsci/cvs-plugin/compare/b1f5341a0332...839a9f84d88f




























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







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

[JIRA] [cvs] (JENKINS-18329) ConcurrentModificationException during pooling in version 2.9

2013-07-02 Thread thorsten.liep...@diehl-controls.com (JIRA)
















































SCM/JIRA link daemon
 resolved  JENKINS-18329 as Fixed


ConcurrentModificationException during pooling in version 2.9
















Change By:


SCM/JIRA link daemon
(02/Jul/13 10:52 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/groups/opt_out.

[JIRA] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable

2013-07-02 Thread andreas.b...@ericsson.com (JIRA)

Andréas Berg
created JENKINS-18578

Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable

Issue Type:

Improvement

Affects Versions:

current

Assignee:

Unassigned

Components:

core

Created:

02/Jul/13 11:13 AM

Description:

The default jar cache location is now hardcoded to ~/.jenkins/cache/jars which is a really bad idea for a big production environment with networked home directories and multiple accounts running slaves.

This behaviour was introduced with this commit:
https://github.com/jenkinsci/remoting/commit/b5145a06876f4390ef3229d70fa5a7edf0739dae

This cache location needs to be configurable.

A bonus would be if permissions within it were handled in a way that supports multi accounts using it. That might be the case already though.

We've put a workaround in place by defining "-Duser.home" to java but that affects other things too. It also needs to be done for master and every slave seperately so it is easy to make misstakes or forget it for some slaves.

Environment:

N/A

Project:

Jenkins

Labels:

jenkins
configuration
slave
cache

Priority:

Minor

Reporter:

Andréas Berg

[JIRA] [integrity-plugin] (JENKINS-18579) PTC Plugin does not restore symbolic links in filesystem















































Thorsten Liepert
 created  JENKINS-18579


PTC Plugin does not restore symbolic links in filesystem















Issue Type:


Bug



Affects Versions:


current



Assignee:


Cletus DSouza



Components:


integrity-plugin



Created:


02/Jul/13 11:23 AM



Description:


We have some Projects building for linux and so have checked in some libraries with the symbolic representation (e.g. glic.so - glibc.so.16). When checking out via MKS Client the links are restored. Check out via PTC-Plugin stores ling as file with following content
#Thu Jun 20 16:21:25 CEST 2013
isFile=true
targetPath=glibc.so.16

Is this an issue of the new PlugIn Version against an older Server? Or a general issu?




Environment:


Ubuntu Server 64Bit 12.04LTS 

Jenkins 1.520

MKS Integrity 2009 (API 4.10)




Project:


Jenkins



Labels:


plugin
scm




Priority:


Major



Reporter:


Thorsten Liepert

























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







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

[JIRA] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable

2013-07-02 Thread andreas.b...@ericsson.com (JIRA)















































Andréas Berg
 updated  JENKINS-18578


Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
















Change By:


Andréas Berg
(02/Jul/13 11:26 AM)




Issue Type:


Improvement
Bug





Priority:


Minor
Major





Description:


Thedefaultjarcachelocationisnowhardcodedto~/.jenkins/cache/jarswhichisareallybadideaforabigproductionenvironmentwithnetworkedhomedirectoriesandmultipleaccountsrunningslaves.Thisbehaviourwasintroducedwiththiscommit:https://github.com/jenkinsci/remoting/commit/b5145a06876f4390ef3229d70fa5a7edf0739daeThiscachelocationneedstobeconfigurable.Abonuswouldbeifpermissionswithinitwerehandledinawaythatsupportsmultiaccountsusingit.Thatmightbethecasealreadythough.Weve
triedto
putaworkaroundinplacebydefining-Duser.hometojavabutthataffectsotherthingstoo
.Italsoneedstobe
andevenwhen
doneformasterandeveryslaveseperately
so
it
iseasytomakemisstakesorforgetitforsomeslaves
doesnotgetridofthebehaviour
.



























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







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

[JIRA] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable

2013-07-02 Thread andreas.b...@ericsson.com (JIRA)















































Andréas Berg
 updated  JENKINS-18578


Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
















Change By:


Andréas Berg
(02/Jul/13 11:44 AM)




Description:


Thedefaultjarcachelocationisnowhardcodedto~/.jenkins/cache/jarswhichisareallybadideaforabigproductionenvironmentwithnetworkedhomedirectoriesandmultipleaccountsrunningslaves.Thisbehaviourwasintroducedwiththiscommit:https://github.com/jenkinsci/remoting/commit/b5145a06876f4390ef3229d70fa5a7edf0739daeThiscachelocationneedstobeconfigurable.Abonuswouldbeifpermissionswithinitwerehandledinawaythatsupportsmultiaccountsusingit.Thatmightbethecasealreadythough.Wevetriedtoputaworkaroundinplacebydefining-Duser.hometojavabutthataffectsotherthingstooandevenwhendoneformasterandeveryslaveseperately
itdoes
Iam
not
getridof
sureifitsolves
the
behaviour
problementirely
.



























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







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

[JIRA] [core] (JENKINS-18580) Error when creating a job with umlauts or workspace files with umlauts

2013-07-02 Thread l.wol...@his.de (JIRA)

Lars Wolter
created JENKINS-18580

Error when creating a job with umlauts or workspace files with umlauts

Issue Type:

Bug

Affects Versions:

current

Assignee:

Unassigned

Attachments:

screenshot.PNG

Components:

core

Created:

02/Jul/13 12:05 PM

Description:

1. When creating a job with German umlauts in its name the corresponding directory in the file system has '?' instead of the umlauts.
As a consequence the build fails because of a java.nio.file.NoSuchFileException.

2. If a file name in a job's workspace contains umlauts, the file cannot be opened via Jenkins because it also has '?' instead of umlauts and cannot be found (- screenshot)

Locale is set to de_DE.UTF-8
Jenkins is started with -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=UTF-8

sun.io.unicode.encoding UnicodeLittle
sun.jnu.encoding UTF-8
file.encoding UTF-8
file.encoding.pkg sun.io

But I wasn't able to get it to work

Environment:

Ubuntu 12.04.2 LTS, Jenkins standalone

Project:

Jenkins

Priority:

Major

Reporter:

Lars Wolter

[JIRA] [clearcase] (JENKINS-12911) Clearecase Plugin Not Detecting Changes

2013-07-02 Thread rudolf.honeg...@siemens.com (JIRA)















































Rudolf Honegger
 commented on  JENKINS-12911


Clearecase Plugin Not Detecting Changes















I just updated to 1.520 and now it works fine.



























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







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

[JIRA] [ws-cleanup] (JENKINS-18446) Add ability to specify if the workspace should be wiped out via a job parameter















































SCM/JIRA link daemon
 commented on  JENKINS-18446


Add ability to specify if the workspace should be wiped out via a job parameter















Code changed in jenkins
User: flozzone
Path:
 pom.xml
 src/main/java/hudson/plugins/ws_cleanup/PreBuildCleanup.java
 src/main/resources/hudson/plugins/ws_cleanup/PreBuildCleanup/config.jelly
 src/main/webapp/help/jobParameter.html
http://jenkins-ci.org/commit/ws-cleanup-plugin/1b9cffa77d9e5a3d809f83c1f16226cb5de9680b
Log:
  JENKINS-18446: Check optional env variable if ws should be cleaned up.

Signed-off-by: Florin Hillebrand florin.hillebr...@streamunlimited.com





























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







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

[JIRA] [clearcase] (JENKINS-12911) Clearecase Plugin Not Detecting Changes

2013-07-02 Thread thomas.bi...@cassidian.com (JIRA)















































Thomas Birkl
 commented on  JENKINS-12911


Clearecase Plugin Not Detecting Changes















Updated yesterday to 1.520.
Seems to detect changes properly now over misc. platforms (Linux Slave - Windows Master),
which did not work before.



























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







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

[JIRA] [warnings] (JENKINS-17794) Replace StyleCop parser with native parser

2013-07-02 Thread ullrich.haf...@gmail.com (JIRA)
















































Ulli Hafner
 resolved  JENKINS-17794 as Fixed


Replace StyleCop parser with native parser
















Change By:


Ulli Hafner
(02/Jul/13 12:35 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/groups/opt_out.

[JIRA] [build-pipeline] (JENKINS-18162) Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects

2013-07-02 Thread b.bott...@projectnibble.org (JIRA)















































Benny Bottema
 commented on  JENKINS-18162


Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects















I looked up the /api/json for two deploy builds of the downstream project and noticed that the parameters are the same despite being triggered by different upstream builds in two separate pipelines. I also noticed the build-pipeline plugin modified the publishers/ tag of the downstream project during the first deploy build, but with the second the publisher tag is left unmodified.

In effect, the downstream project deployed the same application twice.



























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







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

[JIRA] [ws-cleanup] (JENKINS-18446) Add ability to specify if the workspace should be wiped out via a job parameter

2013-07-02 Thread vjura...@java.net (JIRA)
















































vjuranek
 resolved  JENKINS-18446 as Fixed


Add ability to specify if the workspace should be wiped out via a job parameter
















Done in 0.16, release right now





Change By:


vjuranek
(02/Jul/13 12:37 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/groups/opt_out.

[JIRA] [build-pipeline] (JENKINS-18162) Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects

2013-07-02 Thread b.bott...@projectnibble.org (JIRA)













































 
Benny Bottema
 edited a comment on  JENKINS-18162


Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects
















In an older Jenkins version (1.486) I looked up the /api/json for two deploy builds of the downstream project and noticed that the parameters are the same despite being triggered by different upstream builds in two separate pipelines. I also noticed the build-pipeline plugin modified the publishers/ tag of the downstream project during the first deploy build, but with the second the publisher tag is left unmodified.

In effect, the downstream project deployed the same application twice.



























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







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

[JIRA] [build-pipeline] (JENKINS-18162) Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects

2013-07-02 Thread b.bott...@projectnibble.org (JIRA)













































 
Benny Bottema
 edited a comment on  JENKINS-18162


Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects
















In an older Jenkins version (1.486, with build-pipeline 1.3.3) I looked up the /api/json for two deploy builds of the downstream project and noticed that the parameters are the same despite being triggered by different upstream builds in two separate pipelines. I also noticed the build-pipeline plugin modified the publishers/ tag of the downstream project during the first deploy build, but with the second the publisher tag is left unmodified.

In effect, the downstream project deployed the same application twice.



























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







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

[JIRA] [clearcase] (JENKINS-12911) Clearecase Plugin Not Detecting Changes

2013-07-02 Thread vinc...@latombe.net (JIRA)
















































Vincent Latombe
 closed  JENKINS-12911 as Fixed


Clearecase Plugin Not Detecting Changes
















I'm closing as fixed even if the bug was not in the plugin but rather in Jenkins core. Issue is fixed in Jenkins 1.520+





Change By:


Vincent Latombe
(02/Jul/13 1:06 PM)




Status:


Open
Closed





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/groups/opt_out.

[JIRA] [clearcase] (JENKINS-7059) Polling Builds project regardless of changes













































 
Chris Wozny
 edited a comment on  JENKINS-7059


Polling Builds project regardless of changes
















I am still getting this in 1.3.14. I see that a build went off last night and when I look at the details it says "No changes from last build." but also says "Started by an SCM change"

The polling log is shown below:

Started on Jul 2, 2013 2:54:56 AM
(removed asterisks due to formatting in comments) get view CSPEC (removed asterisks due to formatting in comments)
Builds $ "C:\Program Files (x86)\Rational\ClearCase\bin\cleartool" catcs -tag JENKINS_CONFIG_SPEC
element * CHECKEDOUT
element * X
load \XX1
load \XX2
(removed asterisks due to formatting in comments)
INFO CSPEC changed = false
JENKINS_CONFIG_SPEC $ "C:\Program Files (x86)\Rational\ClearCase\bin\cleartool" lsview -cview -s
Done. Took 0.1 sec
Changes found



























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







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

[JIRA] [clearcase] (JENKINS-7059) Polling Builds project regardless of changes















































Chris Wozny
 commented on  JENKINS-7059


Polling Builds project regardless of changes















I am still getting this in 1.3.14. I see that a build went off last night and when I look at the details it says "No changes from last build." but also says "Started by an SCM change"

The polling log is shown below:

Started on Jul 2, 2013 2:54:56 AM

	
	
		
		
			
			


	
	
		
		
			
			


	
	
		
		
			
			


	
	
		
		
			
			


	
	
		
		
			
			


	
	
		
		
			
			


	
	
		
		
			
			


	
	
		
		
			
			


	
	
		
		
			
			


	
	
		
		
			
			


	get view CSPEC 
Builds $ "C:\Program Files (x86)\Rational\ClearCase\bin\cleartool" catcs -tag JENKINS_CONFIG_SPEC
element * CHECKEDOUT
element * X
load \XX1
load \XX2

INFO CSPEC changed = false
JENKINS_CONFIG_SPEC $ "C:\Program Files (x86)\Rational\ClearCase\bin\cleartool" lsview -cview -s
Done. Took 0.1 sec
Changes found


			
			
		
		
	
	


			
			
		
		
	
	


			
			
		
		
	
	


			
			
		
		
	
	


			
			
		
		
	
	


			
			
		
		
	
	


			
			
		
		
	
	


			
			
		
		
	
	


			
			
		
		
	
	


			
			
		
		
	
	





























This message is automatically generated by JIRA.
If you think it was sent

[JIRA] [git] (JENKINS-4418) do shallow clone by default

2013-07-02 Thread vladimirbod...@yahoo.fr (JIRA)















































Vladimir Bodnartchouk
 commented on  JENKINS-4418


do shallow clone by default















This seems to be an important feature that can significantly speedup the build process, the checkbox sounds perfect!



























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







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

[JIRA] [analysis-core] (JENKINS-17780) Expose plug-in results in build and project action
















































SCM/JIRA link daemon
 resolved  JENKINS-17780 as Fixed


Expose plug-in results in build and project action 
















Change By:


SCM/JIRA link daemon
(02/Jul/13 1:55 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/groups/opt_out.

[JIRA] [analysis-core] (JENKINS-17780) Expose plug-in results in build and project action















































SCM/JIRA link daemon
 commented on  JENKINS-17780


Expose plug-in results in build and project action 















Code changed in jenkins
User: Ulli Hafner
Path:
 src/main/java/hudson/plugins/analysis/core/BuildResult.java
http://jenkins-ci.org/commit/analysis-core-plugin/7a18edf6769ad79b8e79ff08f6543ea3b3081fb2
Log:
  Merge pull request #17 from mmenev/JENKINS-17780

FIXED JENKINS-17780 Added new exported properties in build result.


Compare: https://github.com/jenkinsci/analysis-core-plugin/compare/ba39109c4dda...7a18edf6769a




























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







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

[JIRA] [core] (JENKINS-18276) Archiving artifacts from a slave node is extremely slow even with 1.509.1+

2013-07-02 Thread jakub.stil...@bsc-ideas.com (JIRA)















































Jakub Štiller
 commented on  JENKINS-18276


Archiving artifacts from a slave node is extremely slow even with 1.509.1+















We found that problem is not only copy of artifacts. Also upload artifacts to Nexus via Deploy Artifacts to Maven repository is slow only 3MB/s. When setup job on slave to run mvn deploy the upload speed is 30MB/s. So something must be wrong with master server. The master runs on Tomcat 6.0.36. 

I have also look at Jenkins sources and what I understand that uploading artifacts is done via Maven native API, so I think that there should be no differences when calling maven in build and in artifacts upload on master.

Do you have any hints, where the problem may be?  We are looking on tomcat, java, OS setup. But no luck yet. 



























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







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

[JIRA] [github] (JENKINS-18581) Jenkins crashes upon receiving HTTP 502 response from github API

2013-07-02 Thread jpres...@safaribooksonline.com (JIRA)















































John Prestel
 created  JENKINS-18581


Jenkins crashes upon receiving HTTP 502 response from github API















Issue Type:


Bug



Assignee:


Unassigned


Attachments:


jenkins_github_500.png



Components:


github



Created:


02/Jul/13 2:11 PM



Description:


Tried to hit our Jenkins server this morning and found it crashed (server 500) and not recovering. A restart of the service resolved the issue.

From the logs:


Jul 2, 2013 9:35:06 AM org.kohsuke.stapler.compression.CompressionFilter reportException
WARNING: Untrapped servlet exception
java.io.IOException: {
  "message": "Server Error"
}

at org.kohsuke.github.Requester.handleApiError(Requester.java:342)
at org.kohsuke.github.Requester._to(Requester.java:177)
at org.kohsuke.github.Requester.to(Requester.java:141)
at org.kohsuke.github.GitHub.getMyself(GitHub.java:230)
at org.kohsuke.github.GitHub.init(GitHub.java:127)
at org.kohsuke.github.GitHub.connectUsingOAuth(GitHub.java:184)
at org.jenkinsci.plugins.GithubAuthenticationToken.init(GithubAuthenticationToken.java:68)
at org.jenkinsci.plugins.GithubSecurityRealm.doFinishLogin(GithubSecurityRealm.java:315)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:297)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:160)
at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:95)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:683)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:776)
at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:201)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:683)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:776)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:585)
at org.kohsuke.stapler.Stapler.service(Stapler.java:216)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:206)
at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179)
at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86)
at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at

[JIRA] [analysis-core] (JENKINS-17663) Fail by publishing report will fail whole build















































SCM/JIRA link daemon
 commented on  JENKINS-17663


Fail by publishing report will fail whole build















Code changed in jenkins
User: MihailMenev
Path:
http://jenkins-ci.org/commit/analysis-core-plugin/40ec0a84dfcdab2b88ad6a3ba28b2fed41b35285
Log:
  Merge branch 'JENKINS-17663' of github.com:mmenev/analysis-core-plugin into JENKINS-17663

Conflicts:
	src/main/java/hudson/plugins/analysis/core/GlobalSettings.java
	src/main/resources/hudson/plugins/analysis/core/GlobalSettings/global.jelly
	src/main/resources/hudson/plugins/analysis/core/GlobalSettings/global.properties





























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







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

[JIRA] [analysis-core] (JENKINS-17663) Fail by publishing report will fail whole build















































SCM/JIRA link daemon
 commented on  JENKINS-17663


Fail by publishing report will fail whole build















Code changed in jenkins
User: Ulli Hafner
Path:
 src/main/java/hudson/plugins/analysis/core/GlobalSettings.java
 src/main/java/hudson/plugins/analysis/core/HealthAwarePublisher.java
 src/main/resources/hudson/plugins/analysis/core/GlobalSettings/global.jelly
 src/main/resources/hudson/plugins/analysis/core/GlobalSettings/global.properties
http://jenkins-ci.org/commit/analysis-core-plugin/309403780b6425e3f2a1ca2907e82d082a991a46
Log:
  Merge pull request #18 from mmenev/JENKINS-17663

FIXED JENKINS-17663 Added global fail on error checkbox.


Compare: https://github.com/jenkinsci/analysis-core-plugin/compare/7a18edf6769a...309403780b64




























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







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

[JIRA] [analysis-core] (JENKINS-17663) Fail by publishing report will fail whole build
















































SCM/JIRA link daemon
 resolved  JENKINS-17663 as Fixed


Fail by publishing report will fail whole build
















Change By:


SCM/JIRA link daemon
(02/Jul/13 2:14 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/groups/opt_out.

[JIRA] [email-ext] (JENKINS-18517) Content token reference help bubble evaluated multiple times on Job Configuration page

2013-07-02 Thread frederik.fr...@gmail.com (JIRA)















































Frederik Fromm
 commented on  JENKINS-18517


Content token reference help bubble evaluated multiple times on Job Configuration page















We have the same problem. The monitoring plugin shows the following thread dump:


Handling GET /ci/job/INT-autoinst-umg08/configure : RequestHandlerThread[#12568]
java.lang.String.intern(Native Method)
groovy.xml.QName.init(QName.java:74)
groovy.xml.QName.init(QName.java:63)
org.kohsuke.stapler.jelly.groovy.JellyBuilder.methodMissing(JellyBuilder.java:173)
sun.reflect.GeneratedMethodAccessor1065.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
groovy.lang.MetaClassImpl.invokeMissingMethod(MetaClassImpl.java:811)
groovy.lang.MetaClassImpl.invokePropertyOrMissing(MetaClassImpl.java:1103)
groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1056)
groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:884)
groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:704)
groovy.lang.GroovyObjectSupport.invokeMethod(GroovyObjectSupport.java:44)
org.kohsuke.stapler.jelly.groovy.GroovyClosureScript.invokeMethod(GroovyClosureScript.java:88)
org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeOnDelegationObjects(ClosureMetaClass.java:407)
org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:346)
groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:884)
org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.callCurrent(PogoMetaClassSite.java:66)
org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:141)
help$_run_closure1.doCall(help.groovy:3)
sun.reflect.GeneratedMethodAccessor3754.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:272)




























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







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

[JIRA] [jobgenerator] (JENKINS-17814) hudson.model.FreeStyleProject cannot be cast to org.jenkinsci.plugins.jobgenerator.JobGenerator

2013-07-02 Thread timor.rai...@gmail.com (JIRA)















































Timor Raiman
 commented on  JENKINS-17814


hudson.model.FreeStyleProject cannot be cast to org.jenkinsci.plugins.jobgenerator.JobGenerator















I'm hitting the same issue with a generator, whose generated job is supposed to trigger another job... (a parameterized trigger build step, forcing the execution of a worker job on all slaves)



























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







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

[JIRA] [jobgenerator] (JENKINS-17814) hudson.model.FreeStyleProject cannot be cast to org.jenkinsci.plugins.jobgenerator.JobGenerator

2013-07-02 Thread sylvain.ben...@gmail.com (JIRA)















































Sylvain Benner
 started work on  JENKINS-17814


hudson.model.FreeStyleProject cannot be cast to org.jenkinsci.plugins.jobgenerator.JobGenerator
















Change By:


Sylvain Benner
(02/Jul/13 2:23 PM)




Status:


Open
InProgress



























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







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

[JIRA] [jobgenerator] (JENKINS-17814) hudson.model.FreeStyleProject cannot be cast to org.jenkinsci.plugins.jobgenerator.JobGenerator

2013-07-02 Thread sylvain.ben...@gmail.com (JIRA)















































Sylvain Benner
 commented on  JENKINS-17814


hudson.model.FreeStyleProject cannot be cast to org.jenkinsci.plugins.jobgenerator.JobGenerator















Since it is big limitation I will look into this during the week.
Thank you for your reports.



























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







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

[JIRA] [coverity] (JENKINS-18559) Coverity plugin 1.2.5 is not working with Coverity IM 5.5.3















































Chris Wozny
 commented on  JENKINS-18559


Coverity plugin 1.2.5 is not working with Coverity IM 5.5.3















Unfortunately if you look at the plugin's release page. You'll see the following:

Beginning with version 1.2.5, this plugin is only compatible with Coverity Connect (aka Integrity Manager) versions 6.0.0 and higher. If you have a version of Connect earlier than 6.0.0, do not upgrade this plugin past version 1.2.4.
Version 1.2.4 and earlier of this plugin are compatible with Coverity Integrity Manager versions 5.4 to 6.5.

If you are using Coverity IM 5.5.3, then the last version you can use for this plugin in 1.2.4.



























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







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

[JIRA] [coverity] (JENKINS-14833) Jenkins variables are not expanded in Coverity plugin















































Chris Wozny
 commented on  JENKINS-14833


Jenkins variables are not expanded in Coverity plugin















Can we get an update as to whether this has been brought in yet? Also, I wonder if it would be possible to maintain a backported 1.2.4 branch for the folks who aren't using CIM v6 or greater...



























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







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

[JIRA] [core] (JENKINS-18569) Console log is blank when running a job on ZOS

2013-07-02 Thread jay.ha...@sas.com (JIRA)















































Jay Hayes
 updated  JENKINS-18569


Console log is blank when running a job on ZOS
















Change By:


Jay Hayes
(02/Jul/13 2:37 PM)




Description:


ThisissueaddressestheconsolelogfailingtodisplaythelogfromajobexecutedonaZ/OSslave.Ihavedebuggedjenkinsusingthe1.519srcanddiscoveredthephysicallogfileisbeingwrittentodiskandencodedasIBM1047.Ifthelogfileitselfisviewed,youwillfindCR(carriagereturn)charactersattheendofeachline.IfthosecharactersareconvertedtoeitherCR/LFpairsorjustLFcharactersthelogfileisonceagainview-ablebyclickingtheconsoleloglink.Fortestingpurposes,Iaddedamethodtoscrubthelogfile(modifytheCRsasnotedabove)iftheencodingissettoIBM1047andcallthemethodfromwithinonEndBuilding()inhudson.model.Run.Icannowviewthelogfileviatheconsolelogafterthebuildcompletes.Imattachingthebuild.xmlandlogfromaZ/OSjobrunforreference.
Also,seethispostforadditionalinfo:https://groups.google.com/forum/#!searchin/jenkinsci-users/EBCDIC/jenkinsci-users/OUdnqAaJjiE/hmvZBY9DUcYJ



























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







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

[JIRA] [msbuild] (JENKINS-18582) Handling of partially quoted arguments in MSBuild plugin broken

2013-07-02 Thread candrit...@java.net (JIRA)















































candritzky
 created  JENKINS-18582


Handling of partially quoted arguments in MSBuild plugin broken















Issue Type:


Bug



Affects Versions:


current



Assignee:


kdsweeney



Components:


msbuild



Created:


02/Jul/13 2:44 PM



Description:


MSBuild plugin version 1.18 doesn't handle "partially" quoted arguments correctly.

I am using /p:Configuration="Any CPU". This is converted to "/p:Configuration="Any CPU"" causing the MSBuild command line to fail.

As a workaround I can escape the space character using a backslash (e.g. /p:Configuration=Any\ CPU). This will be converted by the MSBuild plugin to "/p:Configuration=Any CPU" which is fine for MSBuild. But this is only a workaround requiring to change all my Jenkins build jobs.

This is a regression introduced by the fix for JENKINS-17876.




Project:


Jenkins



Labels:


msbuild




Priority:


Major



Reporter:


candritzky

























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







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

[JIRA] [email-ext] (JENKINS-18517) Content token reference help bubble evaluated multiple times on Job Configuration page

2013-07-02 Thread efuscia...@deltadentalmi.com (JIRA)















































Eric Fusciardi
 commented on  JENKINS-18517


Content token reference help bubble evaluated multiple times on Job Configuration page















@Alex - Yes, many times.  In fact, restarting is the only thing that helps the problem clean itself up after it piles up to be too unresponsive  



























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







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

[JIRA] [subversion] (JENKINS-9589) SSH sessions kept open by Subversion checkout

2013-07-02 Thread jesse.john...@silabs.com (JIRA)















































Jesse Johnson
 commented on  JENKINS-9589


SSH sessions kept open by Subversion checkout















I have this exact same problem. SVNKIT is supposed to time out open connections after 10 minutes by default but does not appear to be doing so, OR the subversion plugin is setting the connection close to something much higher.

I get an average of 30 open connections from svn commit trigger back to jenkins that just seem to hang around. 

SVN polling seems to login and out properly. 



























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







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

Re: [JIRA] [core] (JENKINS-18493) Users unable to copy jobs without global read permissions

2013-07-02 Thread bzlom

Same issue. In our case it's a necessity since we are configuring the Jenkins
so our Project Managers have the permission: to create and copy their jobs
as required, and manage project permissions by themselves.



--
View this message in context: 
http://jenkins-ci.361315.n4.nabble.com/JIRA-core-JENKINS-18493-Users-unable-to-copy-jobs-without-global-read-permissions-tp4670676p4671407.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/groups/opt_out.

[JIRA] [email-ext] (JENKINS-18517) Content token reference help bubble evaluated multiple times on Job Configuration page

2013-07-02 Thread slide.o....@gmail.com (JIRA)















































Alex Earl
 commented on  JENKINS-18517


Content token reference help bubble evaluated multiple times on Job Configuration page















Ah, my mistake, I was looking at my latest code, not what was released in 2.30.2, I will be doing a release soon that will have a different way of doing this completely.



























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







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

[JIRA] [core] (JENKINS-18493) Users unable to copy jobs without global read permissions

2013-07-02 Thread plescanstanis...@gmail.com (JIRA)















































Potroshitel Jack
 commented on  JENKINS-18493


Users unable to copy jobs without global read permissions















Same issue on our side. 

In our case this is a necessity - since we are configuring the Jenkins so our Project Managers have the permission: to create and copy their jobs as required, and manage project permissions by themselves.



























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







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

[JIRA] [cvs] (JENKINS-18522) Cannot check out CVS module using legacy mode

2013-07-02 Thread j...@assen.demon.co.uk (JIRA)















































John McCabe
 commented on  JENKINS-18522


Cannot check out CVS module using legacy mode















@Scott

You say your issue is resolved but I just wanted to be clear; the issue you found whilst downgrading to version 1.6 of the CVS plug-in is resolved, but it doesn't get round the issue that it's impossible to us SSPI protocol with the most up-to-date version of the CVS and you're forced to use a version that's no longer supported to achieve this.

Is that correct 

John



























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







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

[JIRA] [core] (JENKINS-18558) FilePath's copyRecursiveTo doesn't handle Chinese characters















































Kohsuke Kawaguchi
 commented on  JENKINS-18558


FilePaths copyRecursiveTo doesnt handle Chinese characters















When I read relevant part of the core source code, I think it handles the situation correctly where the encoding of the master and the slave are different.

During a recursive copy, files are packed into a tar format with what's known as "GNU-style long file name" extension, which stores file names in UTF-8. The master reads them back as such and then tries to create files of the same name.

I suspect the master JVM's default encoding is set to iso-8859-1 or something that cannot map some non-ASCII characters. I recommend you check the LANG environment variable on the master JVM.



























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







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

[JIRA] [core] (JENKINS-18558) FilePath's copyRecursiveTo doesn't handle Chinese characters

2013-07-02 Thread tobias.pet...@prisma-solutions.at (JIRA)
















































Kohsuke Kawaguchi
 assigned  JENKINS-18558 to Kohsuke Kawaguchi



FilePaths copyRecursiveTo doesnt handle Chinese characters
















Change By:


Kohsuke Kawaguchi
(02/Jul/13 3:41 PM)




Assignee:


mcrooney
KohsukeKawaguchi



























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







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

[JIRA] An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.

2013-07-02 Thread gm3...@gmail.com (JIRA)

Details:
---
org.apache.velocity.exception.MethodInvocationException:
 Invocation of method #39;next#39; in  class java.util.AbstractList$Itr
 threw exception class java.util.NoSuchElementException : null
at
 org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:251)

at
 
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175)

at
 
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220)

at
 org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)

at
 org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:300)

at
 org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:202)

at
 
com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:143)

at
 
com.atlassian.jira.mail.MailingListCompiler$1.processRecipient(MailingListCompiler.java:295)

at
 
com.atlassian.jira.mail.NotificationRecipientProcessor.process(NotificationRecipientProcessor.java:39)

at
 
com.atlassian.jira.mail.MailingListCompiler.addMailsToQueue(MailingListCompiler.java:318)

at
 
com.atlassian.jira.mail.MailingListCompiler.access$400(MailingListCompiler.java:42)

at
 
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.addEmailsToQueue(MailingListCompiler.java:463)

at
 
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendLists(MailingListCompiler.java:433)

at
 
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendForEvent(MailingListCompiler.java:386)

at
 
com.atlassian.jira.mail.MailingListCompiler.sendLists(MailingListCompiler.java:135)

at
 com.atlassian.jira.mail.IssueMailQueueItem.send(IssueMailQueueItem.java:145)

at
 com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66)

at
 
com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:28)

at
 
com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)

at 
com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)

at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at
 
com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)

at
 org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 3c0fae591c90ba70494f35b895fc4b8f




























style
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and 
(-webkit-min-device-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
/style
div id=email-body
table id=email-wrap align=center border=0 cellpadding=0 
cellspacing=0 style=background-color:#f0f0f0;color:#00;width:100%;
tr valign=top
td id=email-page style=padding:16px !important;
table align=center border=0 cellpadding=0 cellspacing=0 
style=background-color:#ff;border:1px solid 
#bb;color:#00;width:100%;
tr valign=top
td bgcolor=#33 
style=background-color:#33;color:#ff;font-family:Arial,FreeSans,Helvetica,sans-serif;font-size:12px;line-height:1;img
 
src=https://issues.jenkins-ci.org/s/en_US-jh6o7l/733/41/_/jira-logo-scaled.png;
 alt= style=vertical-align:top; //td
/trtr valign=top
td id=email-banner style=padding:32px 32px 0 32px;




table align=left border=0 cellpadding=0 cellspacing=0 
width=100% style=width:100%;
tr valign=top
td 
style=color:#505050;font-family:Arial,FreeSans,Helvetica,sans-serif;padding:0;
img id=email-avatar 
src=https://issues.jenkins-ci.org/secure/useravatar?avatarId=10292; alt= 
height=48 width=48 border=0 align=left style=padding:0;margin: 0 16px 
16px 0; /
div id=email-action style=padding: 0 0 8px 
0;font-size:12px;line-height:18px;
a class=user-hover rel=davidmorris 
id=email_davidmorris 
href=https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=davidmorris; 
style=color:#355564;David Morris/a
 commented on img src=https://issues.jenkins-ci.org/images/icons/bug.gif; 
height=16 width=16 border=0 align=absmiddle alt=Bug a 
style='color:#355564;text-decoration:none;' 
href='https://issues.jenkins-ci.org/browse/JENKINS-5537'JENKINS-5537/a
/div

[JIRA] [xunit] (JENKINS-18575) xUnit failed to parse a JUnit .xml report without any debug in log

2013-07-02 Thread lo...@techsoft3d.com (JIRA)















































Louis Roché
 commented on  JENKINS-18575


xUnit failed to parse a JUnit .xml report without any debug in log















I have the same problem after the upgrade of the plugin from 1.57 or 1.58 (I don't remember). Performance plugin read the file without 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/groups/opt_out.

[JIRA] [subversion] (JENKINS-10628) SCM build trigger not working correctly with variables in SVN URL

2013-07-02 Thread kalai...@gmail.com (JIRA)















































kalaiventhan Annadurai
 commented on  JENKINS-10628


SCM build trigger not working correctly with variables in SVN URL















I am using Jenkins version 1.480.3 and quiet period feature is not working when i specify the parameterized variable. Please suggest on this.



























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







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

[JIRA] [junit] (JENKINS-18095) nose generated xunit reports are rejected by xunit 1.59

2013-07-02 Thread knure...@gmail.com (JIRA)













































 
Jeff K
 edited a comment on  JENKINS-18095


nose generated xunit reports are rejected by xunit 1.59
















same problem here as well (using xunit-file module: https://github.com/peerigon/xunit-file)

I noticed that a few of the things that are making it fail are the 'skip' attribute in the testsuite element, and 'message' attribute on the testcase element, and possibly the 'failure' child element to the testcase element (this last issue might be more specific to the format of the failure element and not just the failure element)

this became an issue when upgrading to v1.60 (haven't tried rolling back to v1.58 yet)



























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







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

[JIRA] [subversion] (JENKINS-10628) SCM build trigger not working correctly with variables in SVN URL

2013-07-02 Thread kalai...@gmail.com (JIRA)













































 
kalaiventhan Annadurai
 edited a comment on  JENKINS-10628


SCM build trigger not working correctly with variables in SVN URL
















I am using Jenkins version 1.480.3 and quiet period feature is not working when i specify the parameterized variable. Please anybody suggest on this.



























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







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

[JIRA] [junit] (JENKINS-18095) nose generated xunit reports are rejected by xunit 1.59

2013-07-02 Thread knure...@gmail.com (JIRA)















































Jeff K
 commented on  JENKINS-18095


nose generated xunit reports are rejected by xunit 1.59















same problem here as well (using xunit-file module: https://github.com/peerigon/xunit-file)

I noticed that a few of the things that are making it fail are the 'skip' attribute in the testsuite element, and 'message' attribute on the testcase element, and possibly the 'failure' child element to the testcase element (this last issue might be more specific to the format of the failure element and not just the failure element)



























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







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

[JIRA] [sonar] (JENKINS-4667) Need a user cause choice for running/not running Sonar

2013-07-02 Thread kalai...@gmail.com (JIRA)















































kalaiventhan Annadurai
 commented on  JENKINS-4667


Need a user cause choice for running/not running Sonar















Can you provide the release version number?



























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







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

[JIRA] [perforce] (JENKINS-18583) [MultipleSCM integration] - View Map is empty in case of multiple Perforce SCM instances

2013-07-02 Thread o.v.nenas...@gmail.com (JIRA)















































Oleg Nenashev
 created  JENKINS-18583


[MultipleSCM integration] - View Map is empty in case of multiple Perforce SCM instances















Issue Type:


Bug



Assignee:


Rob Petti



Components:


perforce



Created:


02/Jul/13 4:12 PM



Description:


Usage of Perforce plugin in the set-up of multiple SCM section leads to Java exception with no explanations of failure. 

Seems that Perforce plugin somehow ignores "View Map" parameters in "newInstance" handler.




Environment:


MultipleSCM




Project:


Jenkins



Labels:


MultipleSCM
Perforce




Priority:


Major



Reporter:


Oleg Nenashev

























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







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

[JIRA] [cvs] (JENKINS-18522) Cannot check out CVS module using legacy mode

2013-07-02 Thread srte...@gmail.com (JIRA)















































Scott Telle
 commented on  JENKINS-18522


Cannot check out CVS module using legacy mode















That is correct! 

I figured that your open JIRA issue encapsulated that problem better though. I created this issue, because I was having trouble with version 1.6 of the plugin, which I was able to work around in a satisfactory manner. 

Thanks John!



























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







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

[JIRA] [perforce] (JENKINS-18583) [MultipleSCM integration] - View Map is empty in case of multiple Perforce SCM instances

2013-07-02 Thread rob.pe...@gmail.com (JIRA)















































Rob Petti
 commented on  JENKINS-18583


[MultipleSCM integration] - View Map is empty in case of multiple Perforce SCM instances















Are you setting up more than one PerforceSCM? Does it happen when you only set up one under MultipleSCM?



























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







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

[JIRA] [cvs] (JENKINS-18522) Cannot check out CVS module using legacy mode

2013-07-02 Thread j...@assen.demon.co.uk (JIRA)















































John McCabe
 commented on  JENKINS-18522


Cannot check out CVS module using legacy mode















Thanks Scott,

I had just wanted to clarify on the basis that there is still a problem going forward (i.e. as described in https://issues.jenkins-ci.org/browse/JENKINS-18330) and that your eventual success was related to a rather nasty workaround of using an unsupported version of the plugin.

John



























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







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

[JIRA] [android-emulator] (JENKINS-18015) Breakage on Android SDK r22

2013-07-02 Thread tony.chuin...@gmail.com (JIRA)















































Tony Chuinard
 commented on  JENKINS-18015


Breakage on Android SDK r22















I'm still getting this issue on the 2.10 version of the plugin:

Waiting for Jenkins to finish collecting data
channel stopped
target $ /usr/local/android-sdk/platform-tools/aapt dump badging budgetplannerpro.apk
ERROR: Failed to parse POMs
java.io.IOException: Cannot run program "/usr/local/android-sdk/platform-tools/aapt" (in directory "/ebs/jenkins/workspace/Budget/target"): java.io.IOException: error=2, No such file or directory
	at java.lang.ProcessBuilder.start(ProcessBuilder.java:488)



























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







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

[JIRA] [android-emulator] (JENKINS-18584) Install Android package task doesn't find aapt with newer SDK

2013-07-02 Thread ch...@orr.me.uk (JIRA)















































Christopher Orr
 created  JENKINS-18584


Install Android package task doesnt find aapt with newer SDK















Issue Type:


Bug



Assignee:


Christopher Orr



Components:


android-emulator



Created:


02/Jul/13 5:29 PM



Description:


Calling "aapt dump badging" likely doesn't work as we're probably expecting it to be in platform-tools, rather in build-tools as it is on newer SDKs.




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/groups/opt_out.

[JIRA] [android-emulator] (JENKINS-14901) Emulator start failed on Ubuntu (SDK 20.0.3)

2013-07-02 Thread tony.chuin...@gmail.com (JIRA)















































Tony Chuinard
 commented on  JENKINS-14901


Emulator start failed on Ubuntu (SDK 20.0.3)















Adding the -noaudio emulator option fixed this for me



























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







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

[JIRA] [master-slave] (JENKINS-11992) Win7 x64: x86 Java runtime creates bad PATH on x64 OS causing ' \Java\jre6\bin was unexpected at this time.' error

2013-07-02 Thread davidriggle...@gmail.com (JIRA)













































 
David Riggleman
 edited a comment on  JENKINS-11992


Win7 x64: x86 Java runtime creates bad PATH on x64 OS causing  \Java\jre6\bin was unexpected at this time. error
















I found this issue quite frustrating. After wasting time wondering why my Powershell script worked if I ran it manually but not if it ran through Jenkins, I eventually came across this issue and determined the root cause. Yes, the issue may be listed as minor, but the headaches that it causes, it would seem to be worth the presumably minimal effort to fix this. My workaround was similar to what others have mentioned in manually fixing the path at the top of my script. Since I'm working with a Powershell script, here's the code I've got at the very top of my script to fix the problem:

Perforce Script
$env:PATH = $env:PATH -replace '"', ""




























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







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

[JIRA] [master-slave] (JENKINS-11992) Win7 x64: x86 Java runtime creates bad PATH on x64 OS causing ' \Java\jre6\bin was unexpected at this time.' error

2013-07-02 Thread davidriggle...@gmail.com (JIRA)















































David Riggleman
 commented on  JENKINS-11992


Win7 x64: x86 Java runtime creates bad PATH on x64 OS causing  \Java\jre6\bin was unexpected at this time. error















I found this issue quite frustrating. After wasting time wondering why my Powershell script worked if I ran it manually but not if it ran through Jenkins, I eventually came across this issue and determined the root cause. Yes, the issue may be listed as minor, but the headaches that it causes, it would seem to be worth the presumably minimal effort to fix this. My workaround was similar to what others have mentioned in manually fixing the path at the top of my script. Since I'm working with a Powershell script, here's the code I've got at the very top of my script to fix the problem:

Perforce Script
$env:PATH = $env:PATH -replace '"', ""




























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







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

[JIRA] [master-slave] (JENKINS-11992) Win7 x64: x86 Java runtime creates bad PATH on x64 OS causing ' \Java\jre6\bin was unexpected at this time.' error

2013-07-02 Thread davidriggle...@gmail.com (JIRA)













































 
David Riggleman
 edited a comment on  JENKINS-11992


Win7 x64: x86 Java runtime creates bad PATH on x64 OS causing  \Java\jre6\bin was unexpected at this time. error
















I found this issue quite frustrating. After wasting time wondering why my Powershell script worked if I ran it manually but not if it ran through Jenkins, I eventually came across this issue and determined the root cause. Yes, the issue may be listed as minor, but the considering headaches that it causes, it would seem to be worth the presumably minimal effort to fix this. My workaround was similar to what others have mentioned in manually fixing the path at the top of my script. Since I'm working with a Powershell script, here's the code I've got at the very top of my script to fix the problem:

Perforce Script
$env:PATH = $env:PATH -replace '"', ""




























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







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

[JIRA] [subversion] (JENKINS-13835) E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request

2013-07-02 Thread ghansen...@gmail.com (JIRA)















































Greg Hansen
 commented on  JENKINS-13835


E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request















Jenkins version 1.519
Jenkins Subversion plugin version 1.50
CentOS 6.3 x86_64

ERROR: Failed to check out https://gigasrc.gigamon.com/repos/gv_g/branches/gv_8300/gs
org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT /repos/!svn/vcc/default failed
	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:379)
	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:364)
	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:352)
	at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:708)
	at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:335)
	at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1289)
	at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:837)
	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.updateInternal(SvnNgAbstractUpdate.java:192)
	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.update(SvnNgAbstractUpdate.java:76)
	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.checkout(SvnNgAbstractUpdate.java:752)
	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:14)
	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:9)
	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20)
	at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20)
	at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1235)
	at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:291)
	at org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:777)
	at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:99)
	at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:153)
	at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:903)
	at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:884)
	at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:867)
	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2388)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:326)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Caused by: svn: E175002: REPORT /repos/!svn/vcc/default failed
	at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208)
	at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154)
	at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97)
	... 32 more
Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT request failed on '/repos/!svn/vcc/default'
svn: E175002: SSL peer shut down incorrectly
	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:754)
	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373)
	... 31 more
Caused by: svn: E175002: REPORT request failed on '/repos/!svn/vcc/default'
	at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208)
	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:752)
	... 32 more
Caused by: svn: E175002: SSL peer shut down incorrectly
	at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:109)
	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:505)
	... 32 more
Caused by: javax.net.ssl.SSLException: SSL peer shut down incorrectly
	at com.sun.net.ssl.internal.ssl.InputRecord.readV3Record(Unknown Source)
	at

[JIRA] [subversion] (JENKINS-18414) Jenkins Subversion plugin checkouts in something NON-UTF-8















































Tobias Peters
 commented on  JENKINS-18414


Jenkins Subversion plugin checkouts in something NON-UTF-8















I had the same problem and the issue was with environment variables
the slave was running on a linux machine, started via ssh from master but the jvm process on the slave didn't get the environment parameter set up for the slave
you can check by doing

sudo cat /proc/slave_pid/environ

so I added 'Prefix Start Slave Command' of

export LANG=en_US.UTF-8;

restarted slave, and checked to see if it was set in /proc/?/environ

after that it did do the svn co correctly




























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







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

Re: [JIRA] [build-pipeline] (JENKINS-18553) configuration is lost, and no new configuration possible

2013-07-02 Thread rbracewell

Having the same issues as a result of the upgrade.
I tried rolling back to the previous plugin but had no luck.

Is there a workaround that will bring pipeline's back to life?

--
Robert



--
View this message in context: 
http://jenkins-ci.361315.n4.nabble.com/JIRA-build-pipeline-JENKINS-18553-configuration-is-lost-and-no-new-configuration-possible-tp4671177p4671448.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/groups/opt_out.

[JIRA] [core] (JENKINS-18585) Error: TypeError: e.up(...).on is not a function on job-configuration screen, which never finishes loading/has broken Save button

2013-07-02 Thread stephen.don...@gmail.com (JIRA)















































Stephen Donner
 created  JENKINS-18585


Error: TypeError: e.up(...).on is not a function on job-configuration screen, which never finishes loading/has broken Save button















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


core



Created:


02/Jul/13 7:58 PM



Description:


We upgraded just this morning to version 1.521, and when going into the job-configuration page, the following two things happen:

1) the "Save" button isn't correctly styled (it's small) and throws an error on click
2) we see the Configuration-Loading overlay, and see this in the Error Console:

Timestamp: 7/2/2013 12:52:16 PM
Error: TypeError: e.up(...).on is not a function
Source File: http://qa-selenium-stage.mv.mozilla.com:8080/adjuncts/562581b0/lib/form/textarea/textarea.js
Line: 18




Environment:


Im on Windows 7, with latest versions of Firefox and Chrome, and see this on Mac OS X 10.8.4, too.




Project:


Jenkins



Priority:


Major



Reporter:


Stephen Donner

























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







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

[JIRA] [core] (JENKINS-18585) Error: TypeError: e.up(...).on is not a function on job-configuration screen, which never finishes loading/has broken Save button

2013-07-02 Thread stephen.don...@gmail.com (JIRA)















































Stephen Donner
 updated  JENKINS-18585


Error: TypeError: e.up(...).on is not a function on job-configuration screen, which never finishes loading/has broken Save button
















Change By:


Stephen Donner
(02/Jul/13 7:59 PM)




Attachment:


error-loading.png



























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







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

[JIRA] [weblogic-deployer] (JENKINS-18586) weblogic deployer plugin - unable to load configuration file

2013-07-02 Thread r...@orange.fr (JIRA)















































Raphael CHAUMIER
 created  JENKINS-18586


weblogic deployer plugin - unable to load configuration file















Issue Type:


Bug



Assignee:


Raphael CHAUMIER



Components:


weblogic-deployer



Created:


02/Jul/13 8:12 PM



Description:


Attributes set in config tag occurs an XStream parsing

p:config xmlns="http://org.jenkinsci.plugins/WeblogicDeploymentPlugin" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://org.jenkinsci.plugins/WeblogicDeploymentPlugin plugin-configuration.xsd "

Specifying namespace prefix occurs the same problem






Project:


Jenkins



Priority:


Major



Reporter:


Raphael CHAUMIER

























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







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

[JIRA] [tfs] (JENKINS-18587) History command causes authenticate exception

2013-07-02 Thread cjasprom...@yahoo.com (JIRA)

CJ Aspromgos
created JENKINS-18587

History command causes authenticate exception

Issue Type:

Bug

Affects Versions:

current

Assignee:

redsolo

Components:

tfs

Created:

02/Jul/13 8:58 PM

Description:

The following exception is thrown when the plugin is used in HUDSON (not sure about Jenkins...yet)

An error occurred: com.microsoft.tfs.core.exceptions.TFSUnauthorizedException: Access denied connecting to TFS server http://company_build_server.com:8080/ (authenticating as company_domain\company_userId)
FATAL: Executable returned an unexpected result code [100]
ERROR: null

...where the company_domain\company_userId is something like "abc\xyz". The other commands used earlier in the build process ("tf workspace", "tf get", etc) work fine using the "company_domain\company_userId" format.

I think an extra slash "\" is not being inserted. In other words the slashed is not being escaped.

For giggles I tried switching the format of the userId to "company_user@company_domain" the "tf workspace" command (at the beginning of the build) fails. I get an authentication failure.

Environment:

Hudson running on Linux x86_64, TFS plugin 1.20, TEE 11.0.0.1306

Project:

Jenkins

Priority:

Major

Reporter:

CJ Aspromgos

[JIRA] [tfs] (JENKINS-18587) TFS Plugin - History command causes authenticate exception

2013-07-02 Thread cjasprom...@yahoo.com (JIRA)















































CJ Aspromgos
 updated  JENKINS-18587


TFS Plugin - History command causes authenticate exception
















Change By:


CJ Aspromgos
(02/Jul/13 9:00 PM)




Summary:


TFSPlugin-
Historycommandcausesauthenticateexception



























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







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

[JIRA] [core] (JENKINS-18585) Error: TypeError: e.up(...).on is not a function on job-configuration screen, which never finishes loading/has broken Save button

2013-07-02 Thread s.sog...@gmail.com (JIRA)















































sogabe
 commented on  JENKINS-18585


Error: TypeError: e.up(...).on is not a function on job-configuration screen, which never finishes loading/has broken Save button















already fixed. see https://github.com/jenkinsci/jenkins/commit/0256f0a74e9b3373fa9fa14ba32bf9cb99dd5ec3



























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







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

[JIRA] [core] (JENKINS-17863) -Xrs switch missing on Windows slaves















































Kohsuke Kawaguchi
 commented on  JENKINS-17863


-Xrs switch missing on Windows slaves















We need more info. Our slave installers do set the -Xrs option to JVM launch options. You can verify this with the Task manager or Process Exploer.



























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







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

[JIRA] [git] (JENKINS-18588) Git polling builds same branch multiple times when 'Execute concurrent builds if necessary' turned on

2013-07-02 Thread jskj...@rei.com (JIRA)















































Jeff Skjonsby
 created  JENKINS-18588


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















Issue Type:


Bug



Affects Versions:


current



Assignee:


Nicolas De Loof



Components:


git



Created:


02/Jul/13 10:32 PM



Description:


We have a job setup to build pull request branches based on a naming convention on the branches. The branch specifier is /pr/. We have 'Execute concurrent builds if necessary' turned on for this job and sometimes Jenkins will kick off 4-5 builds for the same branch at the same time and fill up the executors. I've tried adding a quiet period but that didn't seem to help.




Environment:


RHEL 6




Project:


Jenkins



Priority:


Major



Reporter:


Jeff Skjonsby

























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







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

[JIRA] [core] (JENKINS-18589) Deadlock















































Kohsuke Kawaguchi
 created  JENKINS-18589


Deadlock















Issue Type:


Bug



Assignee:


Kohsuke Kawaguchi



Components:


core



Created:


02/Jul/13 10:39 PM



Description:


The following two threads cause a dead lock:


	at hudson.model.AbstractProject.save(AbstractProject.java:268)
	-  blocked on hudson.maven.MavenModuleSet@57164bd1
	at hudson.plugins.copyartifact.CopyArtifact$ListenerImpl.onRenamed(CopyArtifact.java:331)
	at hudson.model.AbstractItem.renameTo(AbstractItem.java:296)
	-  locked hudson.model.FreeStyleProject@29a74e2b
	-  locked com.cloudbees.hudson.plugins.folder.Folder@29a1da29
	at hudson.model.Job.renameTo(Job.java:577)
	at hudson.model.Job.doDoRename(Job.java:1311)
	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:601)
	at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288)
	at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:29)
	at org.kohsuke.stapler.Function$InterceptedFunction.invoke(Function.java:389)




	at hudson.model.Project.getPublishersList(Project.java:114)
	-  blocked on hudson.model.FreeStyleProject@29a74e2b
	at hudson.model.Project.buildDependencyGraph(Project.java:172)
	at hudson.model.DependencyGraph.build(DependencyGraph.java:90)
	at jenkins.model.Jenkins.rebuildDependencyGraph(Jenkins.java:3563)
	at hudson.model.AbstractItem.delete(AbstractItem.java:515)
	-  locked hudson.maven.MavenModuleSet@57164bd1
	at hudson.model.Job.delete(Job.java:587)
	-  locked hudson.maven.MavenModuleSet@57164bd1
	at com.cloudbees.hudson.plugins.folder.Folder.performDelete(Folder.java:505)
	at hudson.model.AbstractItem.delete(AbstractItem.java:507)
	-  locked com.cloudbees.hudson.plugins.folder.Folder@44bf68c1
	at hudson.model.AbstractItem.doDoDelete(AbstractItem.java:484)






Project:


Jenkins



Priority:


Major



Reporter:


Kohsuke Kawaguchi

























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







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

[JIRA] [core] (JENKINS-18589) Deadlock















































Kohsuke Kawaguchi
 commented on  JENKINS-18589


Deadlock















To generally reduce the likelihood of dead locks like this, we should prefer lock-less code wherever possible. I'm changing Project.getPublishersList() to not to require a locking by using a volatile field.

I experimented a little with using AtomicReference, which looks cleaner, but making this work transparently with XStream turns out to be very difficult, especially when the element in XML may not be present.

The other obvious approach is to the instantiation code in onLoad, but this method is getting complex enough that we need to worry about fixing up fields in the correct order, and IIRC the reason we moved the initializer into the getter method in the first place was because we had such an ordering issue.



























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







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

[JIRA] [core] (JENKINS-18589) Deadlock
















































SCM/JIRA link daemon
 resolved  JENKINS-18589 as Fixed


Deadlock
















Change By:


SCM/JIRA link daemon
(02/Jul/13 10:45 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/groups/opt_out.

[JIRA] [core] (JENKINS-18589) Deadlock

SCM/JIRA link daemon
commented on JENKINS-18589

Deadlock

Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
changelog.html
core/src/main/java/hudson/matrix/MatrixProject.java
core/src/main/java/hudson/model/AbstractProject.java
core/src/main/java/hudson/model/Project.java
maven-plugin/src/main/java/hudson/maven/AbstractMavenProject.java
test/src/test/groovy/hudson/model/AbstractProjectTest.groovy
test/src/test/resources/hudson/model/AbstractProjectTest/vectorTriggers.xml
http://jenkins-ci.org/commit/jenkins/7facc7733c7040536d4074a2c5805b75ee1d8f35
Log:
FIXED JENKINS-18589

Use DescribableList to handle the copy-on-write semantics correctly. The vector class just doesn't cut it, and we've been setting a new value to this field, which will violates all sorts of the concurrent programming practice.

This change has the nice side effect of removing class="vector" from the persisted XML. A test is added to make sure we can still read back such an XML.

Compare: https://github.com/jenkinsci/jenkins/compare/6ceafac2cd6b...7facc7733c70

[JIRA] [dashboard-view] (JENKINS-15858) Jenkinks UI blocking on some calls / DEADLOCK















































Kohsuke Kawaguchi
 commented on  JENKINS-15858


Jenkinks UI blocking on some calls / DEADLOCK















PermGen space out of space should be tracked separately. If you think you've given sufficient perm gen heap size and Jenkins is overusing permgen space, please follow this guide and obtain the heap dump and send it to us offline.



























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







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

[JIRA] [dashboard-view] (JENKINS-15858) Jenkinks UI blocking on some calls / DEADLOCK

Kohsuke Kawaguchi
commented on JENKINS-15858

Jenkinks UI blocking on some calls / DEADLOCK

I looked at the additional thread dumps vmassol-20130625*.txt and I think Jesse's earlier analysis still applies they are showing that while the UI thread is stuck, it's busy loading records from the disk.

I see that three thread dumps involve two jobs "xwiki-platform Quality Checks" and "xwiki-platform". They are both Maven projects with lots of modules, so I can imagine that if the cache is cold, this can result in a considerable delay. When I access this instance, I experience that the first page load time of those two jobs are considerable, yet if I reload the page it renders quickly enough.

Between these and the perm gen problem, I suspect that JVM in question simplify doesn't have enough heap size to keep the cache warm enough. Again, I'd love to see the heap dump that I requested above to see if there's something wasting the heap.

Another thought that occurred to me is if it helps to provide an option to make the build records a strong reference, instead of the weak reference. It shifts the memory pressure from build records to other soft references, but for some users it might be an useful trade off.

[JIRA] [dashboard-view] (JENKINS-15858) Jenkinks UI slow due to constant build record loading















































Kohsuke Kawaguchi
 updated  JENKINS-15858


Jenkinks UI slow due to constant build record loading
















Updated the title of the ticket to reflect the status.

There's no dead lock involved.





Change By:


Kohsuke Kawaguchi
(02/Jul/13 11:20 PM)




Summary:


JenkinksUI
blockingonsomecalls/DEADLOCK
slowduetoconstantbuildrecordloading



























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







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

[JIRA] [jclouds] (JENKINS-15929) Visiting Configure System page in Jenkins causes deadlock in JClouds plugin, freezing entire system