date:20120628















































SCM/JIRA link daemon
 commented on  JENKINS-14170


[Warnings] FxCopParser NotSerializableException when executing job on remote node















Code changed in jenkins
User: Ulli Hafner
Path:
 src/main/java/hudson/plugins/warnings/parser/ViolationsRegistry.java
 src/main/java/hudson/plugins/warnings/parser/fxcop/FxCopParser.java
http://jenkins-ci.org/commit/warnings-plugin/770d405abafb8122433a069dafc543b6b7c0337a
Log:
  JENKINS-14170 Removed FxCop parser from violations registry.





























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

[JIRA] (JENKINS-14172) [Warnings] Content is not allowed in prolog exception when parsing FxCop warnings















































SCM/JIRA link daemon
 commented on  JENKINS-14172


[Warnings] Content is not allowed in prolog exception when parsing FxCop warnings















Code changed in jenkins
User: Ulli Hafner
Path:
 pom.xml
 src/main/java/hudson/plugins/warnings/parser/ParserRegistry.java
 src/test/java/hudson/plugins/warnings/parser/FxcopParserTest.java
 src/test/resources/hudson/plugins/warnings/parser/issue14172.xml
http://jenkins-ci.org/commit/warnings-plugin/48042929bde52cf39abc60a3140b86dd193a0272
Log:
  FIXED JENKINS-14172 Remove BOM header from XML files before parsing.


Compare: https://github.com/jenkinsci/warnings-plugin/compare/b648d22c3d57...48042929bde5




























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

[JIRA] (JENKINS-14172) [Warnings] Content is not allowed in prolog exception when parsing FxCop warnings
















































SCM/JIRA link daemon
 resolved  JENKINS-14172 as Fixed


[Warnings] Content is not allowed in prolog exception when parsing FxCop warnings
















Change By:


SCM/JIRA link daemon
(28/Jun/12 7:41 AM)




Status:


InProgress
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

[JIRA] (JENKINS-14225) Bring back BugInstance Reviews (Classifications and Comments) from Cloud in Details
















































SCM/JIRA link daemon
 resolved  JENKINS-14225 as Fixed


Bring back BugInstance Reviews (Classifications and Comments) from Cloud in Details
















Change By:


SCM/JIRA link daemon
(28/Jun/12 7:48 AM)




Status:


InProgress
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

[JIRA] (JENKINS-14225) Bring back BugInstance Reviews (Classifications and Comments) from Cloud in Details

2012-06-28 Thread hunkeler.sebastian+jenk...@gmail.com (JIRA)















































SCM/JIRA link daemon
 commented on  JENKINS-14225


Bring back BugInstance Reviews (Classifications and Comments) from Cloud in Details















Code changed in jenkins
User: Ulli Hafner
Path:
 plugin/src/main/java/hudson/plugins/findbugs/parser/FindBugsParser.java
http://jenkins-ci.org/commit/findbugs-plugin/f3d98a64ed07bb54831d2033a7a6a5f3c8874f9f
Log:
  FIXED JENKINS-14225 Fixed cloud details URL using the new 2.0.0. API.































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

[JIRA] (JENKINS-13631) Can't manually promote build with approval parameter

2012-06-28 Thread maxime....@gmail.com (JIRA)















































Maxime Lemanissier
 commented on  JENKINS-13631


Cant manually promote build with approval parameter















Problem reproducible with version 2.6, and confirming that it works with 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

[JIRA] (JENKINS-14237) Icons are not dhown

2012-06-28 Thread albert.mirzo...@gmail.com (JIRA)















































Albert Mirzoyan
 created  JENKINS-14237


Icons are not dhown















Issue Type:


Bug



Assignee:


gbossert



Components:


perfpublisher



Created:


28/Jun/12 10:30 AM



Description:


The icon paths in PerfPublisher report look like.
/plugin/PerfPublisher/icons/bullet_green.png

1. the folder /var/lib/jenkins/plugin/perfpublisher is created lowercase, so the icon path should also be lowercase /plugin/perfpublisher/icons/bullet_green.png

2. Jenkins path look like www.example.com/jenkins and it runs with flag --prefix=/jenkins
so please consider --prefix.

Expected Path: /jenkins/plugin/perfpublisher/icons/bullet_green.png




Environment:


Ubuntu Linux




Project:


Jenkins



Priority:


Minor



Reporter:


Albert Mirzoyan

























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

[JIRA] (JENKINS-14238) Use Local module directory instead Use custom workspace

2012-06-28 Thread victormartinezru...@gmail.com (JIRA)















































Victor Martinez
 created  JENKINS-14238


Use 	Local module directory instead Use custom workspace















Issue Type:


Bug



Assignee:


stephenconnolly



Components:


cobertura



Created:


28/Jun/12 10:41 AM



Description:


Error:
Publishing Cobertura coverage report...
No coverage results were found using the pattern '**/coverage.xml' relative to '/storage/jenkins/refactor/AP_TR69_M3/scripts'.  Did you enter a pattern relative to the correct directory?  Did you generate the XML report(s) for Cobertura?
Build step 'Publish Cobertura Coverage Report' changed build result to FAILURE


Config:

?xml version='1.0' encoding='UTF-8'?
project
  actions/
  description/description
  logRotator
daysToKeep-1/daysToKeep
numToKeep14/numToKeep
artifactDaysToKeep-1/artifactDaysToKeep
artifactNumToKeep3/artifactNumToKeep
  /logRotator
  keepDependenciesfalse/keepDependencies
  properties
hudson.security.AuthorizationMatrixProperty
  permissionhudson.model.Item.Read:sh5/permission
  permissionhudson.model.Item.Workspace:sh5/permission
  permissionhudson.model.Item.Build:sh5/permission
/hudson.security.AuthorizationMatrixProperty
hudson.model.ParametersDefinitionProperty
  parameterDefinitions
hudson.model.StringParameterDefinition
  nameBRANCH/name
  description/description
  defaultValueDEV_3GAP_TR69_M3/defaultValue
/hudson.model.StringParameterDefinition   
  /parameterDefinitions
/hudson.model.ParametersDefinitionProperty
  /properties
  scm class="hudson.scm.SubversionSCM"
locations
  hudson.scm.SubversionSCM_-ModuleLocation
remotehttp://camsvnpin01.ipaccess.com/repos/build_cm/trunk/jenkins/builds/scripts/remote
localscripts/local
  /hudson.scm.SubversionSCM_-ModuleLocation
/locations
excludedRegions/excludedRegions
includedRegions/includedRegions
excludedUsers/excludedUsers
excludedRevprop/excludedRevprop
excludedCommitMessages/excludedCommitMessages
workspaceUpdater class="hudson.scm.subversion.UpdateUpdater"/
  /scm
  assignedNoderhel4/assignedNode
  canRoamfalse/canRoam
  disabledfalse/disabled
  blockBuildWhenDownstreamBuildingfalse/blockBuildWhenDownstreamBuilding
  blockBuildWhenUpstreamBuildingfalse/blockBuildWhenUpstreamBuilding
  jdk(Default)/jdk
  triggers class="vector"
  /triggers
  concurrentBuildfalse/concurrentBuild
  customWorkspace/storage/jenkins/refactor/${JOB_NAME}/customWorkspace
  builders
hudson.tasks.Shell
  command. ./scripts/ap_tr69_m3.sh
/hudson.tasks.Shell
  /builders
  publishers
hudson.plugins.cobertura.CoberturaPublisher
  coberturaReportFile**/coverage.xml/coberturaReportFile
  onlyStablefalse/onlyStable
  healthyTarget
targets class="enum-map" enum-type="hudson.plugins.cobertura.targets.CoverageMetric"
  entry
hudson.plugins.cobertura.targets.CoverageMetricCONDITIONAL/hudson.plugins.cobertura.targets.CoverageMetric
int70/int
  /entry
  entry
hudson.plugins.cobertura.targets.CoverageMetricLINE/hudson.plugins.cobertura.targets.CoverageMetric
int80/int
  /entry
  entry
hudson.plugins.cobertura.targets.CoverageMetricMETHOD/hudson.plugins.cobertura.targets.CoverageMetric
int80/int
  /entry
/targets
  /healthyTarget
  unhealthyTarget
targets class="enum-map" enum-type="hudson.plugins.cobertura.targets.CoverageMetric"
  entry
hudson.plugins.cobertura.targets.CoverageMetricCONDITIONAL/hudson.plugins.cobertura.targets.CoverageMetric
int0/int
  /entry
  entry
hudson.plugins.cobertura.targets.CoverageMetricLINE/hudson.plugins.cobertura.targets.CoverageMetric
int0/int
  /entry
  entry
hudson.plugins.cobertura.targets.CoverageMetricMETHOD/hudson.plugins.cobertura.targets.CoverageMetric
int0/int
  /entry
/targets
  /unhealthyTarget
  failingTarget
targets

[JIRA] (JENKINS-14239) Sometimes CCUCM finds baselines in other masterships

2012-06-28 Thread c...@praqma.net (JIRA)















































Christian Wolfgang
 created  JENKINS-14239


Sometimes CCUCM finds baselines in other masterships















Issue Type:


Bug



Assignee:


Christian Wolfgang



Components:


clearcase-ucm



Created:


28/Jun/12 10:54 AM



Description:


When the previous build has posted deliveries, the next build can accidentally use that previous stream. Which is wrong. 




Project:


Jenkins



Priority:


Critical



Reporter:


Christian Wolfgang

























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

[JIRA] (JENKINS-14240) Changlelog is missing user names

2012-06-28 Thread c...@praqma.net (JIRA)















































Christian Wolfgang
 created  JENKINS-14240


Changlelog is missing user names















Issue Type:


Bug



Assignee:


Christian Wolfgang



Components:


clearcase-ucm



Created:


28/Jun/12 10:55 AM



Description:


This also affects the mail plugins, which does not have the names for email addresses.




Project:


Jenkins



Priority:


Critical



Reporter:


Christian Wolfgang

























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

[JIRA] (JENKINS-14241) CCUCM mistreats deliver error

2012-06-28 Thread c...@praqma.net (JIRA)















































Christian Wolfgang
 created  JENKINS-14241


CCUCM mistreats deliver error















Issue Type:


Bug



Assignee:


Christian Wolfgang



Components:


clearcase-ucm



Created:


28/Jun/12 11:02 AM



Description:


In non-modifiable components, CCUCM cannot deliver to integration stream. This error is misinterpreted. 




Project:


Jenkins



Priority:


Critical



Reporter:


Christian Wolfgang

























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

[JIRA] (JENKINS-14242) Jenkins 1.467 with Subversion plugin 1.42 won't allow you to update certificate

2012-06-28 Thread pav...@gmail.com (JIRA)















































Pau Paches
 created  JENKINS-14242


Jenkins 1.467 with Subversion plugin 1.42 wont allow you to update certificate















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


subversion



Created:


28/Jun/12 11:50 AM



Description:


We click the help link in the Subversion URL of a job and choose the link present in the text to change the credentials. When we do the change, we get:
Attempting an SSL client certificate authentcation
FAILED: svn: E175002: OPTIONS /svn/ipg-djrip/djrip/trunk failed
org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS /svn/ipg-djrip/djrip/trunk failed
	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:304)
	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:289)
	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:277)
	at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:696)
	at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:619)
	at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:103)
	at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1018)
	at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.testConnection(DAVRepository.java:99)
	at hudson.scm.SubversionSCM$DescriptorImpl.postCredential(SubversionSCM.java:1968)
	at hudson.scm.SubversionSCM$DescriptorImpl.doPostCredential(SubversionSCM.java:1913)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288)
	at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151)
	at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90)
	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:574)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:162)
	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 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:47)
	at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
	at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
	at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)

[JIRA] (JENKINS-14244) virtualenv builder:cannot download requirements from behind a firewall from pypi.python.org

2012-06-28 Thread kars...@einfach-schwarz.de (JIRA)















































Karsten Schwarz
 created  JENKINS-14244


virtualenv builder:cannot download requirements from behind a firewall from pypi.python.org















Issue Type:


Bug



Assignee:


Unassigned


Components:


shiningpanda



Created:


28/Jun/12 12:27 PM



Description:


Using shiningpanda in a jenkins installation behind a firewell.

When configuring an virtualenv builder the bootstrap file will download the requirements from pypi server instead from local files like in normal virtualenv installations.
(errors see below)

copying the virtualenv_support directory from a local virtualenv installation into the directory where the shiningpanda virtualenv.py is located solves the problem for the current installation.

The virtualenv_support directory and its content should be included into the shiningpanda installation.

Kind regards
Karsten


workspace $ /nfs/seu_tools/sol/python/2.6.7-64bit/bin/python /var/hudson/8282/work/plugins/shiningpanda/WEB-INF/classes/jenkins/plugins/shiningpanda/workspace/virtualenv.py --system-site-packages /var/hudson/8282/work/shiningpanda/jobs/7613aa0d/virtualenvs/7613aa0d
PYTHONHOME is set.  You must activate the virtualenv before using it
New python executable in /var/hudson/8282/work/shiningpanda/jobs/7613aa0d/virtualenvs/7613aa0d/bin/python
Installing setuptools...
  Complete output from command /var/hudson/8282/wor.../7613aa0d/bin/python -c "#!python
\"\"\"Bootstra...sys.argv1:)






" --always-copy -U setuptools:
  Searching for distribute
Reading http://pypi.python.org/simple/distribute/
Download error on http://pypi.python.org/simple/distribute/: Errno 128 Network is unreachable  Some packages may not be found!
Reading http://pypi.python.org/simple/distribute/
Download error on http://pypi.python.org/simple/distribute/: Errno 128 Network is unreachable  Some packages may not be found!
Couldn't find index page for 'distribute' (maybe misspelled?)
Scanning index of all packages (this may take a while)
Reading http://pypi.python.org/simple/
Download error on http://pypi.python.org/simple/: Errno 128 Network is unreachable  Some packages may not be found!
Skipping development or system egg: distribute 0.6.27
No local packages or download links found for distribute
error: Could not find suitable distribution for Requirement.parse('distribute') (--always-copy skips system and development eggs)

...Installing setuptools...done.
Traceback (most recent call last):
  File "/var/hudson/8282/work/plugins/shiningpanda/WEB-INF/classes/jenkins/plugins/shiningpanda/workspace/virtualenv.py", line 2275, in module
main()
  File "/var/hudson/8282/work/plugins/shiningpanda/WEB-INF/classes/jenkins/plugins/shiningpanda/workspace/virtualenv.py", line 937, in main
never_download=options.never_download)
  File "/var/hudson/8282/work/plugins/shiningpanda/WEB-INF/classes/jenkins/plugins/shiningpanda/workspace/virtualenv.py", line 1049, in create_environment
search_dirs=search_dirs, never_download=never_download)
  File "/var/hudson/8282/work/plugins/shiningpanda/WEB-INF/classes/jenkins/plugins/shiningpanda/workspace/virtualenv.py", line 593, in install_setuptools
search_dirs=search_dirs, never_download=never_download)
  File "/var/hudson/8282/work/plugins/shiningpanda/WEB-INF/classes/jenkins/plugins/shiningpanda/workspace/virtualenv.py", line 567, in _install_req
cwd=cwd)
  File "/var/hudson/8282/work/plugins/shiningpanda/WEB-INF/classes/jenkins/plugins/shiningpanda/workspace/virtualenv.py", line 1015, in call_subprocess
% (cmd_desc, proc.returncode))
OSError: Command /var/hudson/8282/wor.../7613aa0d/bin/python -c "#!python
\"\"\"Bootstra...sys.argv1:)




Environment:


Solaris, Python 2.6.7




Project:


Jenkins



Labels:


plugin




Priority:


Minor

[JIRA] (JENKINS-12792) Violation Plugin display [no report] for FxCop

2012-06-28 Thread jenk...@atrip.sk (JIRA)















































Martin Adam
 commented on  JENKINS-12792


Violation Plugin display [no report] for FxCop















to the original description: you can force fxCop to generate file even with no messages (/fo switch), it could solve your problem (but I haven't tried that)

to alexlombardi: I don't think your situation is really related to this bug - situation you are describing was working correctly with older jenkins. I've upgraded jenkins last week (had about 6 month old version before) and only then the messages near the exclamation mark dissapeared - so I'm quite sure that's another problem and it's most likely caused by some change in jenkins itself



























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

[JIRA] (JENKINS-14246) Keychain cannot be unlocked if no user session is created















































Sebastian Hunkeler
 created  JENKINS-14246


Keychain cannot be unlocked if no user session is created















Issue Type:


Bug



Assignee:


Unassigned


Components:


xcode



Created:


28/Jun/12 2:13 PM



Description:


The OsX Keychain cannot be unlocked if jenkins runs as a daemon and no user session is created. Therefore the org.jenkins-ci.plist file needs an additional key/value pair:
keySessionCreate/key
true /




Project:


Jenkins



Priority:


Blocker



Reporter:


Sebastian Hunkeler

























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

[JIRA] (JENKINS-13814) java.lang.OutOfMemoryError exception when getting the remote log

2012-06-28 Thread gene....@alcatel-lucent.com (JIRA)















































Gene Liu
 commented on  JENKINS-13814


java.lang.OutOfMemoryError exception when getting the remote log















More inputs of cvs rlog stuck (for ever) 

Executed method:
java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3366)

Executor #1 for sambstage : executing MAIN_DEV #13
java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3366)
java.util.regex.Pattern$Curly.match(Pattern.java:3737)
java.util.regex.Pattern$GroupTail.match(Pattern.java:4227)
java.util.regex.Pattern$Curly.match1(Pattern.java:3797)
java.util.regex.Pattern$Curly.match(Pattern.java:3746)
java.util.regex.Pattern$GroupHead.match(Pattern.java:4168)
java.util.regex.Pattern$Curly.match0(Pattern.java:3782)
java.util.regex.Pattern$Curly.match(Pattern.java:3744)
java.util.regex.Pattern$Start.match(Pattern.java:3055)
java.util.regex.Matcher.search(Matcher.java:1105)
java.util.regex.Matcher.find(Matcher.java:535)
hudson.scm.CvsChangeLogHelper.mapCvsLog(CvsChangeLogHelper.java:169)
hudson.scm.CVSSCM.calculateChangeLog(CVSSCM.java:419)
hudson.scm.CVSSCM.checkout(CVSSCM.java:831)
hudson.model.AbstractProject.checkout(AbstractProject.java:1193)
hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:565)
hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:453)
hudson.model.Run.run(Run.java:1376)
hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
hudson.model.ResourceController.execute(ResourceController.java:88)
hudson.model.Executor.run(Executor.java:175)



























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

[JIRA] (JENKINS-12792) Violation Plugin display [no report] for FxCop

2012-06-28 Thread jenk...@atrip.sk (JIRA)













































 
Martin Adam
 edited a comment on  JENKINS-12792


Violation Plugin display [no report] for FxCop
















to the original description: you can force fxCop to generate file even with no messages (/fo switch), it could solve your problem (but I haven't tried that)

to alexlombardi: I don't think your situation is really related to this bug - situation you are describing was working correctly with older jenkins. I've upgraded jenkins last week (had about 6 month old version before) and only then the messages near the exclamation mark dissapeared - so I'm quite sure that's another problem and it's most likely caused by some change in jenkins itself
EDIT: see JENKINS-12764



























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

[JIRA] (JENKINS-13030) Canceling subversion checkout fails a build















































kutzi
 commented on  JENKINS-13030


Canceling subversion checkout fails a build















Should be fixed in Jenkins 1.439+



























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

[JIRA] (JENKINS-14247) Master Executor Needed for SCM polling even with slaves

2012-06-28 Thread steve.eckerl...@socgen.com (JIRA)















































Steve Eckerlein
 created  JENKINS-14247


Master Executor Needed for SCM polling even with slaves















Issue Type:


Bug



Assignee:


Vincent Latombe



Components:


clearcase



Created:


28/Jun/12 2:52 PM



Description:


At work, in my configuration, the master only do balancing stuff. The master as no executor, but many slaves do the builds.

When the plugin do a scm-polling, if no executor was set to the master (0 executor) the plugin does not append path to cleartool command. In my configuration, it fail because cleartool is not in the PATH. (i have not the rights to define env variable in the system)

If i set an executor on the master, the path set in the clearcase installation field is taken. (even if the job is forced to run on a slave)

Even if i try to manualy set clearcase path on slaves, in clearcase installation field, or in PATH variable, it does not work.

Here the trace when an executor is setted :

Started on Jun 28, 2012 4:37:12 PM
im_test_ass_build $ /produits/clearcase/opt_ibm/RationalSDLC/clearcase/bin/cleartool desc -fmt %found_blsXp\n stream:IM_Ass@/vobs/pvob_ati
baseline:intg-metier_INITIAL@/vobs/pvob_ati
im_test_ass_build $ /produits/clearcase/opt_ibm/RationalSDLC/clearcase/bin/cleartool desc -fmt %componentXp\n baseline:intg-metier_INITIAL@/vobs/pvob_ati
component:intg-metier@/vobs/pvob_ati
jenkins_im_test-ass_dyn $ /produits/clearcase/opt_ibm/RationalSDLC/clearcase/bin/cleartool pwv -root
/view/jenkins_im_test-ass_dyn
im_test_ass_build $ /produits/clearcase/opt_ibm/RationalSDLC/clearcase/bin/cleartool lsview jenkins_im_test-ass_dyn

	jenkins_im_test-ass_dyn /Clearcase/views/siciceda/jenkins_im_test-ass_dyn.vws
im_test_ass_build $ /produits/clearcase/opt_ibm/RationalSDLC/clearcase/bin/cleartool startview jenkins_im_test-ass_dyn
jenkins_im_test-ass_dyn $ /produits/clearcase/opt_ibm/RationalSDLC/clearcase/bin/cleartool lshistory -all -since 28-jun-12.14:12:10utc+ -fmt '\"%Nd\" \"%u\" \"%En\" \"%Vn\" \"%e\" \"%o\" \"%activityXp\" \n%c\n' -branch brtype:IM_Ass -nco vobs/vob_ati/intg-metier
im_test_ass_build $ /produits/clearcase/opt_ibm/RationalSDLC/clearcase/bin/cleartool desc -fmt %found_blsXp\n stream:IM_Ass@/vobs/pvob_ati
baseline:intg-metier_INITIAL@/vobs/pvob_ati
im_test_ass_build $ /produits/clearcase/opt_ibm/RationalSDLC/clearcase/bin/cleartool desc -fmt %componentXp\n baseline:intg-metier_INITIAL@/vobs/pvob_ati
component:intg-metier@/vobs/pvob_ati
Done. Took 2.2 sec
No changes




Here a trace when no master executor is set :

Started on Jun 28, 2012 4:39:12 PM
im_test_ass_build $ cleartool desc -fmt %found_blsXp\n stream:IM_Ass@/vobs/pvob_ati
FATAL: Cannot run program "cleartool" (in directory "/applis/iced/jenkins/shared/slave0001/workspace/im_test_ass_build"): java.io.IOException: error=2, No such file or directory
java.io.IOException: Cannot run program "cleartool" (in directory "/applis/iced/jenkins/shared/slave0001/workspace/im_test_ass_build"): java.io.IOException: error=2, No such file or directory
	at java.lang.ProcessBuilder.start(ProcessBuilder.java:460)
	at hudson.Proc$LocalProc.init(Proc.java:244)
	at hudson.Proc$LocalProc.init(Proc.java:216)
	at hudson.Launcher$LocalLauncher.launch(Launcher.java:709)
	at hudson.Launcher$ProcStarter.start(Launcher.java:338)
	at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:934)
	at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:901)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:287)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:619)
Caused by: java.io.IOException: java.io.IOException: error=2, No such file or directory
	at

[JIRA] (JENKINS-5093) Subversion: checkout consistent snapshot when multiple sources are specified
















































kutzi
 resolved  JENKINS-5093 as Fixed


Subversion: checkout consistent snapshot when multiple sources are specified
















Jenkins uses the timestamp of the build to check out all modules. So this is consistent.





Change By:


kutzi
(28/Jun/12 2:53 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

[JIRA] (JENKINS-13800) Subversion Plugin deletes private Maven repository when using Always checkout a fresh copy, Emulate clean checkout by first... or Use svn update... with 'svn revert' before
















































kutzi
 resolved  JENKINS-13800 as Wont Fix


Subversion Plugin deletes private Maven repository when using Always checkout a fresh copy, Emulate clean checkout by first... or Use svn update... with svn revert before update
















This works as designed.
I've seen various other issues requesting to change this behaviour, so please search for them, vote and comment on them, if you want it changed.





Change By:


kutzi
(28/Jun/12 2:57 PM)




Status:


Open
Resolved





Resolution:


WontFix



























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

[JIRA] (JENKINS-10105) subversion plugin to slow
















































kutzi
 resolved  JENKINS-10105 as Duplicate


subversion plugin to slow
















Change By:


kutzi
(28/Jun/12 2:59 PM)




Status:


Reopened
Resolved





Resolution:


Duplicate



























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

[JIRA] (JENKINS-6940) subversion updates by hudson are three time slower than from commandline
















































kutzi
 resolved  JENKINS-6940 as Duplicate


subversion updates by hudson are three time slower than from commandline
















Change By:


kutzi
(28/Jun/12 3:00 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























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

[JIRA] (JENKINS-12165) Jenkins throws SVNException
















































kutzi
 resolved  JENKINS-12165 as Incomplete


Jenkins throws SVNException
















Change By:


kutzi
(28/Jun/12 3:04 PM)




Status:


Open
Resolved





Resolution:


Incomplete



























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

[JIRA] (JENKINS-14233) NPE when using the [Choice] option of the [This build is parameterized] functionality















































domi
 commented on  JENKINS-14233


NPE when using the [Choice] option of the [This build is parameterized] functionality 















why do you think this is a problem of the nodelabel parameter plugin?
...what you are creating is a normal "choice" parameter, this has nothing to do with a node or label parameter.



























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

[JIRA] (JENKINS-14234) RuntimeException when using [Label] option in [This build is parameterized]















































domi
 commented on  JENKINS-14234


RuntimeException when using [Label] option in [This build is parameterized]















which version of...

	Jenkins?
	nodelabel plugin?
	subversion plugin?



what other parameters do you have configured in this job? which order do these paramaters have?
can you provide a screenshot just of the parameters just before trying to save it?



























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

[JIRA] (JENKINS-242) Make path to cvs configurable

2012-06-28 Thread fenol...@gmail.com (JIRA)















































Mauricio Fenoglio
 reopened  JENKINS-242


Make path to cvs configurable
















This is not fixed.

I have a ubuntu with timezone BRT(jenkyns) and a solaris with BRT (cvs) and the update is not syncronized.

The time is set cvs update -d -r HEAD -D 28 Jun 2012 11:53:50 -0300
I really cant understand why you dont add an option to conf the -D option ..

If I cant fix it soon I will have to change to apache C. 












Change By:


Mauricio Fenoglio
(28/Jun/12 3:22 PM)




Resolution:


Fixed





Status:


Closed
Reopened



























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

[JIRA] (JENKINS-14248) DiskUsage dont show values.

2012-06-28 Thread fenol...@gmail.com (JIRA)















































Mauricio Fenoglio
 created  JENKINS-14248


DiskUsage dont show values.















Issue Type:


Bug



Affects Versions:


current



Assignee:


vjuranek



Attachments:


err.png



Components:


disk-usage



Created:


28/Jun/12 3:46 PM



Description:


No values are showed.

On log 

Jun 28, 2012 12:41:14 PM hudson.model.AsyncPeriodicWork$1 run
INFO: Started Project disk usage
Jun 28, 2012 12:41:20 PM hudson.model.AsyncPeriodicWork$1 run
INFO: Finished Project disk usage. 729 ms






Environment:


Ubuntu 

Jenkins ver. 1.472



With w7 the same problem




Project:


Jenkins



Labels:


plugin




Priority:


Major



Reporter:


Mauricio Fenoglio

























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

[JIRA] (JENKINS-14230) Node parameter value can't be passed by HTTP GET















































SCM/JIRA link daemon
 commented on  JENKINS-14230


Node parameter value cant be passed by HTTP GET















Code changed in jenkins
User: imod
Path:
 src/main/java/org/jvnet/jenkins/plugins/nodelabelparameter/NodeParameterDefinition.java
http://jenkins-ci.org/commit/nodelabelparameter-plugin/4181f676118f9ec7727ba69ac5227f93210d965f
Log:
  FIXED JENKINS-14230 Node parameter value can't be passed by HTTP GET





























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

[JIRA] (JENKINS-14230) Node parameter value can't be passed by HTTP GET
















































SCM/JIRA link daemon
 resolved  JENKINS-14230 as Fixed


Node parameter value cant be passed by HTTP GET
















Change By:


SCM/JIRA link daemon
(28/Jun/12 4:30 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

[JIRA] (JENKINS-14230) Node parameter value can't be passed by HTTP GET















































domi
 commented on  JENKINS-14230


Node parameter value cant be passed by HTTP GET















great catch, thank you!!!



























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

[JIRA] (JENKINS-14230) Node parameter value can't be passed by HTTP GET

2012-06-28 Thread yury.mikhaile...@gmail.com (JIRA)
















































Yury Mikhailenko
 closed  JENKINS-14230 as Fixed


Node parameter value cant be passed by HTTP GET
















Thanks for quick update





Change By:


Yury Mikhailenko
(28/Jun/12 5:12 PM)




Status:


Resolved
Closed



























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

[JIRA] (JENKINS-14250) E-mail field is not automatically populated when a git plugin creates new user.

2012-06-28 Thread tke...@sugarcrm.com (JIRA)















































Thomas Kelly
 created  JENKINS-14250


E-mail field is not automatically populated when a git plugin creates new user.















Issue Type:


Bug



Affects Versions:


current



Assignee:


Nicolas De Loof



Components:


git, plugin



Created:


28/Jun/12 5:17 PM



Description:


Create a job that polls a git repo and emails committers

Commit to repo using some git-config name and email address

Check "People" page. A new user is created. Checking the user configure page shows that:

	Their username is the git-config email without the @domain.com
	Everything else is left blank (the email field is not automatically populated)






Environment:


Jenkins 1.472 running in Ubuntu 11.04 on VMWare Fusion.




Fix Versions:


current



Project:


Jenkins



Labels:


git
plugin
jenkins




Priority:


Major



Reporter:


Thomas Kelly

























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

[JIRA] (JENKINS-14249) Build Flow throws excepion on Build Now

2012-06-28 Thread li...@exroot.org (JIRA)















































Tomasz Melcer
 created  JENKINS-14249


Build Flow throws excepion on Build Now















Issue Type:


Bug



Assignee:


Nicolas De Loof



Components:


build-flow



Created:


28/Jun/12 5:16 PM



Description:


Output of my job:


Started by user anonymous
FATAL: java.util.Collections$UnmodifiableRandomAccessList cannot be cast to java.io.File
java.lang.ClassCastException: java.util.Collections$UnmodifiableRandomAccessList cannot be cast to java.io.File
	at org.codehaus.groovy.runtime.dgm$162.invoke(Unknown Source)
	at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoMetaMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:271)
	at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:53)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
	at com.cloudbees.plugins.flow.FlowDSL.executeFlowScript(FlowDSL.groovy:44)
	at com.cloudbees.plugins.flow.FlowRun$RunnerImpl.doRun(FlowRun.java:130)
	at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:467)
	at hudson.model.Run.run(Run.java:1404)
	at com.cloudbees.plugins.flow.FlowRun.run(FlowRun.java:112)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:238)
	at hudson.model.OneOffExecutor.run(OneOffExecutor.java:66)



My build flow is very simple for now:


build("Run tests")






Environment:


Jenkins 1.447.1, Build Flow 0.3, Debian Wheezy




Project:


Jenkins



Priority:


Major



Reporter:


Tomasz Melcer

























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

[JIRA] (JENKINS-14249) Build Flow throws excepion on Build Now

2012-06-28 Thread li...@exroot.org (JIRA)
















































Tomasz Melcer
 closed  JENKINS-14249 as Fixed


Build Flow throws excepion on Build Now
















Oh, just noticed there was a release today fixing this problem.





Change By:


Tomasz Melcer
(28/Jun/12 5:18 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

[JIRA] (JENKINS-13972) Concurrent matrix builds abort

2012-06-28 Thread trba...@adobe.com (JIRA)















































Trevor Baker
 commented on  JENKINS-13972


Concurrent matrix builds abort















Arg, I just wanted to starting using concurrent matrix builds and ran into this.  I am heartened to see that the bug is open and hope we can see resolution soon!



























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

[JIRA] (JENKINS-14135) NPE

2012-06-28 Thread spam_schluc...@web.de (JIRA)
















































Karsten Brandt
 assigned  JENKINS-14135 to Karsten Brandt



NPE
















Change By:


Karsten Brandt
(28/Jun/12 5:51 PM)




Assignee:


sogabe
KarstenBrandt



























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

[JIRA] (JENKINS-14251) Parent injected env properties not propagated to child build jobs

2012-06-28 Thread bruce.e...@gmail.com (JIRA)















































Bruce Edge
 created  JENKINS-14251


Parent injected env properties not propagated to child build jobs















Issue Type:


Bug



Affects Versions:


current



Assignee:


Gregory Boissinot



Components:


envinject, parameterized-trigger



Created:


28/Jun/12 5:56 PM



Description:


A job that uses "Prepare an environment for the run" and defines some variables either in a properties file, or inline properties, does not pass these variables to child job executions.

I'm using "Trigger/call builds on other projects" and specifying a list of child jobs, and "Current build parameters" is checked.

I added an 'env' at the top of the scripts for both parent and child jobs and all of the properties defined in the parent via env injected properties are not present in the child env.

I also compared the build's "Injected environment variables" and they confirm that the parent injected properties are missing from the child env.




Environment:


Ubuntu 12.04.

ii  jenkins  1.472   Continuous integration system written in Jav






Project:


Jenkins



Priority:


Major



Reporter:


Bruce Edge

























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

[JIRA] (JENKINS-14135) NPE

2012-06-28 Thread spam_schluc...@web.de (JIRA)















































Karsten Brandt
 commented on  JENKINS-14135


NPE















I've created a similar test environment.
But I wasn't able to reproduce this reported error.

Therefore, I need more information.

1.) jenkins server environment: WINDOWS or UNIX/LINUX ?
2.) detailed configuration settings, especially the search pattern for your sloccount input file
3.) Please send us a example of a workspace, which leads to this error. This will be very useful.

Then I will fix this error as soon as possible.

Regards,
kbrandt



























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

[JIRA] (JENKINS-13814) java.lang.OutOfMemoryError exception when getting the remote log















































SCM/JIRA link daemon
 commented on  JENKINS-13814


java.lang.OutOfMemoryError exception when getting the remote log















Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
 src/main/java/hudson/scm/CVSChangeLogSet.java
 src/main/java/hudson/scm/CVSSCM.java
 src/main/java/hudson/scm/CvsChangeLogHelper.java
 src/main/java/hudson/scm/CvsLog.java
 src/test/java/hudson/scm/CvsChangeLogHelperTest.java
http://jenkins-ci.org/commit/cvs-plugin/2565a8f550f61bbca9311aff60293806f4d6f67b
Log:
  JENKINS-13814 don't buffer the entire rlog output in memory.

The size of the data "cvs rlog" produces is roughtly O(N*M) where
N is the # of files in the directory and M is the amount of changes.

So even when a delta is small, on a large repository this can produce
significant amount of data. Use of ByteArrayOutputStream causes a large
spike that can kill a VM, so spill the data over to disk if we are
getting large output.





























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

[JIRA] (JENKINS-13814) java.lang.OutOfMemoryError exception when getting the remote log

2012-06-28 Thread k...@kohsuke.org (JIRA)

Kohsuke Kawaguchi
commented on JENKINS-13814

java.lang.OutOfMemoryError exception when getting the remote log

I went ahead and made some performance improvements. I hope this didn't step on the toe of Michael.

My CVS knowledge is rusty, but there's inherent problem in retaining the entire "cvs rlog" output in memory. CVS rlog returns some data for every file in the repository, so on a large repository, it'll produce huge data even if there haven't been many files that have changed. I fixed this.

I'm also bit disappointed that the optimization we had in the CVS plugin 1.x appears to be gone, where we observed what files have changed during update and use that list to reduce the target of the log command. This was very useful for typical CI situation where your changes between builds are small. I suspect this also has a performance implication.

Finally, I'd like to advise against relying regular _expression_ matching on entire "cvs log" output block, as it is both error prone and fragile.

When I look at https://github.com/jenkinsci/cvs-plugin/blob/master/src/main/java/hudson/scm/CvsLog.java#L273 I spot a number of problems right away for example,
[\r|\n]+
is a mistake of
[\r\n]+
and there are various
.+?
that can incorrectly match multiple lines when the commit message contains stuff that looks suspiciously like cvs log output.

And in some cases regular _expression_ matching will result in very inefficient backtracking, which is what I suspect to be the cause when people report "cvs rlog stuck".

I thought we used to bundle package-renamed CVS log parsing code taken from Ant, which I thought did the job better. I'm curious what the motivation is for replacing that with a custom parsing code.

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

[JIRA] (JENKINS-14135) NPE

2012-06-28 Thread o...@informatik.rwth-aachen.de (JIRA)















































Carsten Otto
 commented on  JENKINS-14135


NPE















1) Linux. 
2) dist/report.sc
3) http://aprove.informatik.rwth-aachen.de/~cotto/workspace.zip (I deleted everything but the dist/ directory. If you need more, we need to fine tune - I cannot give you the source of our project.)



























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

[JIRA] (JENKINS-12037) CLI - I/O error in channel Chunked connection/Unexpected termination of the channel - still occurring in Jenkins 1.449















































SCM/JIRA link daemon
 commented on  JENKINS-12037


CLI - I/O error in channel Chunked connection/Unexpected termination of the channel - still occurring in Jenkins 1.449















Code changed in jenkins
User: Richard Mortimer
Path:
 src/main/java/hudson/remoting/PingThread.java
http://jenkins-ci.org/commit/remoting/463b5427d272f5d0c2c97eb6c41ef95757eb6c15
Log:
  Do not attempt to retry a channel get after an ExecutionException.
Without this the pinger busy waits retrying the same operation for the
timeout period. The timeout/retry mechanism was only intended to retry
pings that were interrupted.

This is part of the failure seen in JENKINS-12037 where the PingThread
busy waits for 4 minutes when the Ping class fails to execute on a restricted
channel.





























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

[JIRA] (JENKINS-12610) java.io.IOException: Unable to delete - Deleting Project

2012-06-28 Thread dan.stan...@hp.com (JIRA)















































Dan Stangel
 commented on  JENKINS-12610


java.io.IOException: Unable to delete - Deleting Project















Just wanted to confirm that I'm also seeing this behavior when attempting to clean up a workspace with files named with non-standard characters.  Also I have LANG=en_US.UTF-8 set in my Jenkins environment.

Started by upstream project "Fossology_Installation" build number 99
Building on master
Cleaning local Directory .
java.io.IOException: Unable to delete /home/jenkins/jobs/Fossology_Unit_Tests/workspace/./src/ununpack/agent_tests/Unit/test-result/threezip.zip.dir/Desktop.zip.dir - files in dir: /home/jenkins/jobs/Fossology_Unit_Tests/workspace/./src/ununpack/agent_tests/Unit/test-result/threezip.zip.dir/Desktop.zip.dir/�-�� +-��+-��.txt
	at hudson.Util.deleteFile(Util.java:265)
	at hudson.Util.deleteRecursive(Util.java:316)
	at hudson.Util.deleteContentsRecursive(Util.java:227)
	at hudson.Util.deleteRecursive(Util.java:307)
	at hudson.Util.deleteContentsRecursive(Util.java:227)
	at hudson.Util.deleteRecursive(Util.java:307)
	at hudson.Util.deleteContentsRecursive(Util.java:227)
	at hudson.Util.deleteRecursive(Util.java:307)
	at hudson.Util.deleteContentsRecursive(Util.java:227)
	at hudson.Util.deleteRecursive(Util.java:307)
	at hudson.Util.deleteContentsRecursive(Util.java:227)
	at hudson.Util.deleteRecursive(Util.java:307)
	at hudson.Util.deleteContentsRecursive(Util.java:227)
	at hudson.Util.deleteRecursive(Util.java:307)
	at hudson.Util.deleteContentsRecursive(Util.java:227)
	at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:71)
	at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:136)
	at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:788)
	at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:769)
	at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:753)
	at hudson.FilePath.act(FilePath.java:758)
	at hudson.FilePath.act(FilePath.java:740)
	at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:743)
	at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:685)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1193)
	at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:565)
	at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:453)
	at hudson.model.Run.run(Run.java:1376)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:175)



























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

[JIRA] (JENKINS-11884) Cannot create temporary file















































SCM/JIRA link daemon
 commented on  JENKINS-11884


Cannot create temporary file















Code changed in jenkins
User: imod
Path:
 src/main/java/hudson/remoting/RemoteClassLoader.java
http://jenkins-ci.org/commit/remoting/52d19a9771688658b2df56b4f43424f433811841
Log:
  add some hints to ease enduser debuging (JENKINS-11884)





























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

[JIRA] (JENKINS-242) Make path to cvs configurable

2012-06-28 Thread fenol...@gmail.com (JIRA)













































 
Mauricio Fenoglio
 edited a comment on  JENKINS-242


Make path to cvs configurable
















This is not fixed.

I have a ubuntu with timezone BRT(jenkins) and a solaris with BRT (cvs) and the update is not syncronized.

The time is set cvs update -d -r HEAD -D 28 Jun 2012 11:53:50 -0300
I really cant understand why you dont add an option to conf the -D option ..

If I cant fix it soon I will have to change to apache C. 


































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

[JIRA] (JENKINS-14135) NPE

2012-06-28 Thread o...@informatik.rwth-aachen.de (JIRA)















































Carsten Otto
 commented on  JENKINS-14135


NPE















What kind of details reg. 2 do you need?



























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

[JIRA] (JENKINS-9142) Add Build Step button broken in job configure page

2012-06-28 Thread jsamp...@namemedia.com (JIRA)















































jaron Sampson
 commented on  JENKINS-9142


Add Build Step button broken in job configure page















I am using Jenkins own DB for security, with project-specific matrix permissions. During job configuration (for new or existing jobs), the add build step failed for all options, OSX/Chrome19.0.1084.56 and OSX/Firefox12.0  (about 270 yui "expected declaration but found '*' per page load in the FF error logs). I disabled the "Prevent Cross Site Request Forgery exploits" property in the Jenkins configuration (I had the crumb algo enabled as well), and the add build step started working again.



























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

[JIRA] (JENKINS-9142) Add Build Step button broken in job configure page

2012-06-28 Thread jsamp...@namemedia.com (JIRA)













































 
jaron Sampson
 edited a comment on  JENKINS-9142


Add Build Step button broken in job configure page
















I am using Jenkins own DB for security, with project-specific matrix permissions. During job configuration (for new or existing jobs), the add build step failed for all options, using OSX/Chrome19.0.1084.56 and OSX/Firefox12.0  (about 270 yui "expected declaration but found '*'" per page loads appeared in the FF error logs). I disabled the "Prevent Cross Site Request Forgery exploits" property in the Jenkins configuration (I had the crumb algo enabled as well), and the add build step started working again.



























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

[JIRA] (JENKINS-13552) Provide extended 'injected environment variables' view

2012-06-28 Thread gregory.boissi...@gmail.com (JIRA)















































Gregory Boissinot
 commented on  JENKINS-13552


Provide extended injected environment variables view















I have difficulty providing this feature at the moment due to the plugin design.
Regarding the ability to override the WORKSPACE variable for matrix projects, it is maybe a bug, please report a new bug.
Moreover, would you like also to have the detail of injected environment variables at each job step (before checkout, after checkout, build steps, publishers)?



























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

[JIRA] (JENKINS-14252) Ignore time spent waiting for locks

2012-06-28 Thread danki...@java.net (JIRA)















































dankirkd
 created  JENKINS-14252


Ignore time spent waiting for locks















Issue Type:


Bug



Affects Versions:


current



Assignee:


Kohsuke Kawaguchi



Components:


build-timeout



Created:


28/Jun/12 8:46 PM



Description:


This plugin is useful, but we often have situations when the plugin times out well before a job has actually been running for the period set.

We use the "Locks and Latches" plugin, and sometimes a lock cause the build to have to wait for a while.

What would be really nice is if the timeout countdown didn't start until the job actually obtained the lock it was waiting for.




Environment:


Jenkins, using a pre-build lock sharing plugin such as 




Project:


Jenkins



Priority:


Minor



Reporter:


dankirkd

























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

[JIRA] (JENKINS-12014) Jenkins Free-form Project Execute SSH build step default timeout not obvious

2012-06-28 Thread edmund_wag...@java.net (JIRA)















































edmund_wagner
 updated  JENKINS-12014


Jenkins Free-form Project Execute SSH build step default timeout not obvious
















Change By:


edmund_wagner
(28/Jun/12 9:19 PM)




Component/s:


publish-over-ssh





Component/s:


ssh



























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

[JIRA] (JENKINS-13814) java.lang.OutOfMemoryError exception when getting the remote log

2012-06-28 Thread gene....@alcatel-lucent.com (JIRA)















































Gene Liu
 commented on  JENKINS-13814


java.lang.OutOfMemoryError exception when getting the remote log















We expect an upgrade of cvs plugin with a shorter interval of changelog. However the result is that the upgraded version (2.x) takes much longer. If we want to use the upgraded one, we have to turn off the changelog feature.



























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

[JIRA] (JENKINS-6463) Builds hanging right before e-mail notifications are sent out

2012-06-28 Thread cron...@gmail.com (JIRA)















































Robert Cronk
 reopened  JENKINS-6463


Builds hanging right before e-mail notifications are sent out
















We see this all the time and it's killing us.  Here's the threadDump of the executor that's hung.  Let me know if you need the whole dump:


Executor #-1 for master : executing driver-smoketest.linux #1235

"Executor #-1 for master : executing driver-smoketest.linux #1235" Id=374602 Group=main BLOCKED on winstone.classLoader.WebappClassLoader@77ce3fc5 owned by "pool-3-thread-1820" Id=406115
	at winstone.classLoader.WebappClassLoader.loadClass(WebappClassLoader.java:48)
	-  blocked on winstone.classLoader.WebappClassLoader@77ce3fc5
	at java.lang.ClassLoader.loadClass(ClassLoader.java:266)
	at javax.xml.parsers.FactoryFinder.getProviderClass(FactoryFinder.java:109)
	at javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:144)
	at javax.xml.parsers.FactoryFinder.find(FactoryFinder.java:231)
	at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:125)
	at org.apache.commons.digester.Digester.getFactory(Digester.java:490)
	at org.apache.commons.digester.Digester.getParser(Digester.java:693)
	at org.apache.commons.digester.Digester.getXMLReader(Digester.java:899)
	at org.apache.commons.digester.Digester.parse(Digester.java:1631)
	at hudson.plugins.mercurial.MercurialChangeLogParser.parse(MercurialChangeLogParser.java:49)
	at hudson.plugins.mercurial.MercurialChangeLogParser.parse(MercurialChangeLogParser.java:24)
	at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:832)
	at hudson.model.AbstractBuild.getChangeSet(AbstractBuild.java:806)
	at hudson.model.AbstractBuild.hasParticipant(AbstractBuild.java:358)
	at hudson.model.AbstractProject.hasParticipant(AbstractProject.java:1419)
	at hudson.model.User.getProjects(User.java:409)
	at hudson.scm.MailAddressResolverImpl.findMailAddressFor(MailAddressResolverImpl.java:21)
	at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:100)
	at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:530)
	at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:396)
	at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:273)
	at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:265)
	at hudson.plugins.emailext.ExtendedEmailPublisher.access$100(ExtendedEmailPublisher.java:69)
	at hudson.plugins.emailext.ExtendedEmailPublisher$1.endBuild(ExtendedEmailPublisher.java:600)
	at hudson.matrix.MatrixBuild$MatrixBuildExecution.post2(MatrixBuild.java:381)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639)
	at hudson.model.Run.execute(Run.java:1513)
	at hudson.matrix.MatrixBuild.run(MatrixBuild.java:287)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:236)
	at hudson.model.OneOffExecutor.run(OneOffExecutor.java:66)







Change By:


Robert Cronk
(28/Jun/12 10:40 PM)




Resolution:


Fixed





Status:


Closed
Reopened



























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

[JIRA] (JENKINS-6463) Builds hanging right before e-mail notifications are sent out

2012-06-28 Thread cron...@gmail.com (JIRA)















































Robert Cronk
 commented on  JENKINS-6463


Builds hanging right before e-mail notifications are sent out















A few minutes later, the stack trace for that thread looks a little different but it's still hung sending email:


Executor #-1 for master : executing driver-smoketest.linux #1235

"Executor #-1 for master : executing driver-smoketest.linux #1235" Id=374602 Group=main RUNNABLE
	at java.lang.Throwable.getStackTraceElement(Native Method)
	at java.lang.Throwable.getOurStackTrace(Throwable.java:608)
	-  locked java.lang.Throwable@7b0035af
	at java.lang.Throwable.getStackTrace(Throwable.java:599)
	at org.apache.commons.logging.impl.Jdk14Logger.log(Jdk14Logger.java:89)
	at org.apache.commons.logging.impl.Jdk14Logger.debug(Jdk14Logger.java:114)
	at org.apache.commons.beanutils.BeanUtilsBean.populate(BeanUtilsBean.java:814)
	at org.apache.commons.beanutils.BeanUtils.populate(BeanUtils.java:433)
	at org.apache.commons.digester.SetPropertiesRule.begin(SetPropertiesRule.java:251)
	at org.apache.commons.digester.Rule.begin(Rule.java:152)
	at org.apache.commons.digester.Digester.startElement(Digester.java:1361)
	at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:504)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1340)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2732)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:625)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:488)
	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:812)
	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:741)
	at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123)
	at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1208)
	at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:525)
	at org.apache.commons.digester.Digester.parse(Digester.java:1631)
	at hudson.plugins.mercurial.MercurialChangeLogParser.parse(MercurialChangeLogParser.java:49)
	at hudson.plugins.mercurial.MercurialChangeLogParser.parse(MercurialChangeLogParser.java:24)
	at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:832)
	at hudson.model.AbstractBuild.getChangeSet(AbstractBuild.java:806)
	at hudson.model.AbstractBuild.hasParticipant(AbstractBuild.java:358)
	at hudson.model.AbstractProject.hasParticipant(AbstractProject.java:1419)
	at hudson.model.User.getProjects(User.java:409)
	at hudson.scm.MailAddressResolverImpl.findMailAddressFor(MailAddressResolverImpl.java:21)
	at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:100)
	at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:530)
	at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:396)
	at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:273)
	at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:265)
	at hudson.plugins.emailext.ExtendedEmailPublisher.access$100(ExtendedEmailPublisher.java:69)
	at hudson.plugins.emailext.ExtendedEmailPublisher$1.endBuild(ExtendedEmailPublisher.java:600)
	at hudson.matrix.MatrixBuild$MatrixBuildExecution.post2(MatrixBuild.java:381)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639)
	at hudson.model.Run.execute(Run.java:1513)
	at hudson.matrix.MatrixBuild.run(MatrixBuild.java:287)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:236)
	at hudson.model.OneOffExecutor.run(OneOffExecutor.java:66)



The log looks like this (hung forever - or for an hour, or for 9 hours). And yes, ours is intermittent too, so it's not just a bad email addresses:

.
.
.
Email was triggered for: Failure
Sending email for trigger: Failure





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.

[JIRA] (JENKINS-6463) Builds hanging right before e-mail notifications are sent out

2012-06-28 Thread cron...@gmail.com (JIRA)















































Robert Cronk
 commented on  JENKINS-6463


Builds hanging right before e-mail notifications are sent out















One more for good measure.  I'm hoping someone familiar with the stack traces will see in one of these a clue to where it's hanging:


Executor #-1 for master : executing driver-smoketest.linux #1235

"Executor #-1 for master : executing driver-smoketest.linux #1235" Id=374602 Group=main RUNNABLE
	at java.lang.Throwable.getStackTraceElement(Native Method)
	at java.lang.Throwable.getOurStackTrace(Throwable.java:608)
	-  locked java.lang.Throwable@1c5b510e
	at java.lang.Throwable.getStackTrace(Throwable.java:599)
	at org.apache.commons.logging.impl.Jdk14Logger.log(Jdk14Logger.java:89)
	at org.apache.commons.logging.impl.Jdk14Logger.debug(Jdk14Logger.java:114)
	at org.apache.commons.digester.Digester.startDocument(Digester.java:1283)
	at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startDocument(AbstractSAXParser.java:287)
	at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.startDocument(XMLDTDValidator.java:666)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.startEntity(XMLDocumentScannerImpl.java:565)
	at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.startDocumentParsing(XMLVersionDetector.java:175)
	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:790)
	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:741)
	at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123)
	at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1208)
	at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:525)
	at org.apache.commons.digester.Digester.parse(Digester.java:1631)
	at hudson.plugins.mercurial.MercurialChangeLogParser.parse(MercurialChangeLogParser.java:49)
	at hudson.plugins.mercurial.MercurialChangeLogParser.parse(MercurialChangeLogParser.java:24)
	at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:832)
	at hudson.model.AbstractBuild.getChangeSet(AbstractBuild.java:806)
	at hudson.model.AbstractBuild.hasParticipant(AbstractBuild.java:358)
	at hudson.model.AbstractProject.hasParticipant(AbstractProject.java:1419)
	at hudson.model.User.getProjects(User.java:409)
	at hudson.scm.MailAddressResolverImpl.findMailAddressFor(MailAddressResolverImpl.java:21)
	at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:100)
	at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:530)
	at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:396)
	at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:273)
	at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:265)
	at hudson.plugins.emailext.ExtendedEmailPublisher.access$100(ExtendedEmailPublisher.java:69)
	at hudson.plugins.emailext.ExtendedEmailPublisher$1.endBuild(ExtendedEmailPublisher.java:600)
	at hudson.matrix.MatrixBuild$MatrixBuildExecution.post2(MatrixBuild.java:381)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639)
	at hudson.model.Run.execute(Run.java:1513)
	at hudson.matrix.MatrixBuild.run(MatrixBuild.java:287)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:236)
	at hudson.model.OneOffExecutor.run(OneOffExecutor.java:66)





























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

[JIRA] (JENKINS-6463) Builds hanging right before e-mail notifications are sent out

2012-06-28 Thread rob.pe...@gmail.com (JIRA)















































Rob Petti
 commented on  JENKINS-6463


Builds hanging right before e-mail notifications are sent out















Robert, this ticket is specifically referring to the Perforce Plugin. It looks like your issue is with the Mercurial plugin. I'd recommend opening up a new ticket.



























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

[JIRA] (JENKINS-14107) Unable to monitor external job in 1.470 (IllegalAccessError)

2012-06-28 Thread da...@gamehouse.com (JIRA)















































Dave Kelsey
 commented on  JENKINS-14107


Unable to monitor external job in 1.470 (IllegalAccessError)















I'm using version 1.472 and get the same error.
I'm running ls -l as described in https://wiki.jenkins-ci.org/display/JENKINS/Monitoring+external+jobs


sudo apt-get install jenkins-external-tool-monitor
# obviously you should replace localhost with a FQDN if you want to run jobs from other machines.
export JENKINS_HOME=http://@sorins.uk.xensource.com:8080/export JENKINS_HOME=http://@localhost:8080/
java -jar /usr/share/jenkins/external-job-monitor/java/jenkins-core-*.jar "external-build-job-name" command-to-run
java -jar /usr/share/jenkins/external-job-monitor/java/jenkins-core-*.jar "external-build-test" ls -l


The stack trace is:

Started
FATAL: tried to access field hudson.model.Run.charset from class hudson.model.ExternalRun$2
java.lang.IllegalAccessError: tried to access field hudson.model.Run.charset from class hudson.model.ExternalRun$2
	at hudson.model.ExternalRun$2.run(ExternalRun.java:121)
	at hudson.model.Run.execute(Run.java:1488)
	at hudson.model.ExternalRun.acceptRemoteSubmission(ExternalRun.java:100)
	at hudson.model.ExternalJob.doPostBuildResult(ExternalJob.java:102)
	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:288)
	at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151)
	at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90)
	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:574)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:162)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
	at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
	at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:470)
	at

[JIRA] (JENKINS-14178) Add an SCM poll listener















































SCM/JIRA link daemon
 commented on  JENKINS-14178


Add an SCM poll listener















Code changed in jenkins
User: wolfgarnet
Path:
 core/src/main/java/hudson/model/AbstractProject.java
 core/src/main/java/hudson/model/listeners/SCMPollListener.java
http://jenkins-ci.org/commit/jenkins/f3ddb2856eb94b06ee1c95ed603e65170d782af5
Log:
  JENKINS-14178 Adding SCM poll listener





























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

[JIRA] (JENKINS-14178) Add an SCM poll listener
















































SCM/JIRA link daemon
 resolved  JENKINS-14178 as Fixed


Add an SCM poll listener
















Change By:


SCM/JIRA link daemon
(29/Jun/12 1:15 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

[JIRA] (JENKINS-14178) Add an SCM poll listener















































SCM/JIRA link daemon
 commented on  JENKINS-14178


Add an SCM poll listener















Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
 changelog.html
 core/src/main/java/hudson/model/AbstractProject.java
 core/src/main/java/hudson/model/listeners/SCMPollListener.java
http://jenkins-ci.org/commit/jenkins/f5d378f22915f00e34783043624ce7e8dc3ec793
Log:
  FIXED JENKINS-14178 Merge branch 'pull-505'

Conflicts:
	core/src/main/java/hudson/model/AbstractProject.java


Compare: https://github.com/jenkinsci/jenkins/compare/d1d66fee144e...f5d378f22915




























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

[JIRA] (JENKINS-5986) Bzr polling continuously launches build for launchpad urls
















































Stewart Smith
 assigned  JENKINS-5986 to Stewart Smith



Bzr polling continuously launches build for launchpad urls
















Change By:


Stewart Smith
(29/Jun/12 1:34 AM)




Assignee:


trondn
StewartSmith



























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

[JIRA] (JENKINS-5986) Bzr polling continuously launches build for launchpad urls
















































Stewart Smith
 resolved  JENKINS-5986 as Cannot Reproduce


Bzr polling continuously launches build for launchpad urls
















Change By:


Stewart Smith
(29/Jun/12 1:35 AM)




Status:


Open
Resolved





Resolution:


CannotReproduce



























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

[JIRA] (JENKINS-5986) Bzr polling continuously launches build for launchpad urls















































Stewart Smith
 commented on  JENKINS-5986


Bzr polling continuously launches build for launchpad urls















I think this is no longer a problem. I have not seen this behaviour with my use of Bazaar plugin and Launchpad URLs without having SSH keys.

Perhaps a problem with very old BZR versions (2.0)?



























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

[JIRA] (JENKINS-8221) Use bzr branch --lightweight branch instead of bzr branch when creating repository first time.
















































Stewart Smith
 resolved  JENKINS-8221 as Fixed


Use bzr branch --lightweight branch instead of bzr branch when creating repository first time.
















We have this in recent versions (it's an option).

Although in the future we may go to using stacked repositories instead, due to the performance issues associated with lightweight checkouts.





Change By:


Stewart Smith
(29/Jun/12 1:46 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

[JIRA] (JENKINS-8221) Use bzr branch --lightweight branch instead of bzr branch when creating repository first time.
















































Stewart Smith
 closed  JENKINS-8221 as Fixed


Use bzr branch --lightweight branch instead of bzr branch when creating repository first time.
















Change By:


Stewart Smith
(29/Jun/12 1:46 AM)




Status:


Resolved
Closed



























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

[JIRA] (JENKINS-7952) Share Bazaar history in a shared repository to improve performances
















































Stewart Smith
 closed  JENKINS-7952 as Wont Fix


Share Bazaar history in a shared repository to improve performances
















Change By:


Stewart Smith
(29/Jun/12 1:48 AM)




Status:


Resolved
Closed



























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

[JIRA] (JENKINS-7952) Share Bazaar history in a shared repository to improve performances
















































Stewart Smith
 resolved  JENKINS-7952 as Wont Fix


Share Bazaar history in a shared repository to improve performances
















There are some BZR bugs/problems with doing this with concurrent builds.

Two bzr processes trying to create the same pack at the same time can conflict, leading to a not particularly happy state.

I think it will be better to instead use stacked repositories to solve this problem.

(I wish that shared repositories really did work... but it's not nearly reliable enough yet).





Change By:


Stewart Smith
(29/Jun/12 1:47 AM)




Status:


Open
Resolved





Resolution:


WontFix



























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

[JIRA] (JENKINS-10335) bazaar plugin: complile error
















































Stewart Smith
 resolved  JENKINS-10335 as Fixed


bazaar plugin: complile error
















This appears to have been merged in a previous release.





Change By:


Stewart Smith
(29/Jun/12 1:49 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

[JIRA] (JENKINS-10004) Pull/checkout of a specific tag/revision















































Stewart Smith
 commented on  JENKINS-10004


Pull/checkout of a specific tag/revision















A workaround is to do something like the following:

bzr branch -r1234 lp:foo foo-1234
cd foo-1234
bzr push lp:~user/foo/foo-1234

and ask Jenkins to build lp:~user/foo/foo-1234 in a parameterised build.



























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

[JIRA] (JENKINS-10335) bazaar plugin: complile error
















































Stewart Smith
 closed  JENKINS-10335 as Fixed


bazaar plugin: complile error
















Change By:


Stewart Smith
(29/Jun/12 1:49 AM)




Status:


Resolved
Closed



























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

[JIRA] (JENKINS-6475) Bazaar plugin requires write access to the master Hudson home path on SSH slaves















































Stewart Smith
 commented on  JENKINS-6475


Bazaar plugin requires write access to the master Hudson home path on SSH slaves















I don't think this has anything to do with the bzr plugin specifically as bzr will just take the HOME environment variable.



























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

[JIRA] (JENKINS-14178) Add an SCM poll listener

2012-06-28 Thread dogf...@java.net (JIRA)















































dogfood
 commented on  JENKINS-14178


Add an SCM poll listener















Integrated in  jenkins_main_trunk #1790
 JENKINS-14178 Adding SCM poll listener (Revision f3ddb2856eb94b06ee1c95ed603e65170d782af5)

 Result = SUCCESS
wolfgarnet : f3ddb2856eb94b06ee1c95ed603e65170d782af5
Files : 

	core/src/main/java/hudson/model/AbstractProject.java
	core/src/main/java/hudson/model/listeners/SCMPollListener.java





























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

[JIRA] (JENKINS-11884) Cannot create temporary file
















































domi
 resolved  JENKINS-11884 as Fixed


Cannot create temporary file
















Kohsuke now also added an option to redirect the slaves log via commandline option: https://github.com/jenkinsci/remoting/commit/597a7ac878b3d1b236fd55ea72470dd2f8e6c15c this should help to fix such issues too.
Therefore I think this can now be closed now.





Change By:


domi
(29/Jun/12 4:20 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

[JIRA] (JENKINS-9761) Add ACL to scriptler to authorize some non Jenkins admins to launch scriptlers scripts.















































domi
 updated  JENKINS-9761


Add ACL to scriptler to authorize some non Jenkins admins to launch scriptlers scripts.
















Change By:


domi
(29/Jun/12 4:46 AM)




Assignee:


KohsukeKawaguchi
domi





Component/s:


scriptler





Component/s:


script-realm



























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

[JIRA] (JENKINS-13662) Maven job Pre Step properties are not getting right















































domi
 updated  JENKINS-13662


Maven job Pre Step properties are not getting right
















basically you can use parameters and reference these in your maven build step configuration like this:

MY_VERSION=${MY_PARAM}





Change By:


domi
(29/Jun/12 4:51 AM)




Component/s:


script-realm



























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

[JIRA] (JENKINS-12250) Critical block can not be added into conditional step















































domi
 commented on  JENKINS-12250


Critical block can not be added into conditional step















ping, Oleksandr... is this working now, can I do a release?



























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

[JIRA] (JENKINS-13469) Prototype.Selector is undefined















































domi
 commented on  JENKINS-13469


Prototype.Selector is undefined















is this still an issue with a more recent jenkins and plugin version?



























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

[JIRA] (JENKINS-13792) Support for conditional post-build actions















































domi
 updated  JENKINS-13792


Support for conditional post-build actions
















the reason for the cvs-tag plugin not to show up in the list, is most probably the same as mention for missing builders here: https://wiki.jenkins-ci.org/display/JENKINS/Conditional+BuildStep+Plugin#ConditionalBuildStepPlugin-Conditions





Change By:


domi
(29/Jun/12 4:59 AM)




Description:


Itwouldbegreatifthe
conditional-buildstep
plugincouldalsobeusedfor*post*-buildactions.Ourusecaseisthatwehaveaparameterizedbuild,and,dependingontheinputparametersofabuild,wewouldliketotagtheworkspace,ornot.Sowewouldaddarun-conditionfortheTagpost-buildactioncheckingwhetheraspecificinputparameterwasset.





Component/s:


cvs-tag





Component/s:


conditional-buildstep



























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

[JIRA] (JENKINS-13392) Config File Management shows broken icon and missing section descriptions

2012-06-28 Thread vasilena.tren...@softwareag.com (JIRA)















































domi
 commented on  JENKINS-13392


Config File Management shows broken icon and missing section descriptions















Is this still an 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

[JIRA] (JENKINS-14233) NPE when using the [Choice] option of the [This build is parameterized] functionality















































Vassilena Treneva
 commented on  JENKINS-14233


NPE when using the [Choice] option of the [This build is parameterized] functionality 















Okay, which subcomponent do you think I should move this issue to?
Thanks



























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

[JIRA] (JENKINS-14234) RuntimeException when using [Label] option in [This build is parameterized]

2012-06-28 Thread vasilena.tren...@softwareag.com (JIRA)















































Vassilena Treneva
 commented on  JENKINS-14234


RuntimeException when using [Label] option in [This build is parameterized]















Jenkins ver. 1.472
NodeLabel Parameter Plugin 1.1.4
Subversion Plugin 1.9



























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

[JIRA] (JENKINS-14233) NPE when using the [Choice] option of the [This build is parameterized] functionality















































domi
 commented on  JENKINS-14233


NPE when using the [Choice] option of the [This build is parameterized] functionality 















this would be core...
please also include some information about:

	which other parameters are added at the same time?
	how many parameters do you add?
	does the issue persist if you have nothing else configured the this parameter?





























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

[JIRA] (JENKINS-14234) RuntimeException when using [Label] option in [This build is parameterized]