date:20130614

Oleg Nenashev
created JENKINS-18346

Corruption of workspace due to unfull parameters substitution (no validation)

Issue Type:

Bug

Affects Versions:

current

Assignee:

Rob Petti

Components:

perforce

Created:

14/Jun/13 8:58 AM

Description:

Hello,

We have experienced several issues with substitution of parameters during execution of operation.

For example, ${EXECUTOR_NUMBER} works well for checkout(), but this parameter is not accessible during execution processWorkspaceBeforeDeletion(). It causes corruption of job, which requires manual fix at server’s side. Reproduction steps:
• We start job, and checkout() successfully creates workspace.
• Cleanup workspace…
• getWorkspace() in processWorkspaceBeforeDeletion() creates new workspace at Perforce server (name contains unsubstituted EXECUTOR_NUMBER parameter) and then deletes it. BTW, it deletes local folders as well.
• Run job again…
• Checkout() completes successfully, because P4 server thinks that workspace is up to date
• Job fails, because there’s no data in job’s workspace after p4 checkout

Best regards,
Oleg Nenashev

Project:

Jenkins

Labels:

job
workspace_corruption

Priority:

Critical

Reporter:

Oleg Nenashev

[JIRA] [perforce] (JENKINS-18346) Corruption of workspace due to unfull parameters substitution (no validation)















































Oleg Nenashev
 started work on  JENKINS-18346


Corruption of workspace due to unfull parameters substitution (no validation)
















Change By:


Oleg Nenashev
(14/Jun/13 8:59 AM)




Status:


Open
InProgress



























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







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

[JIRA] [perforce] (JENKINS-18346) Corruption of workspace due to unfull parameters substitution (no validation)
















































Oleg Nenashev
 assigned  JENKINS-18346 to Oleg Nenashev



Corruption of workspace due to unfull parameters substitution (no validation)
















Change By:


Oleg Nenashev
(14/Jun/13 8:59 AM)




Assignee:


RobPetti
OlegNenashev



























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







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

[JIRA] [copyartifact] (JENKINS-18347) Deadlock when renaming 2 jobs at the same time

2013-06-14 Thread vinc...@latombe.net (JIRA)















































Vincent Latombe
 created  JENKINS-18347


Deadlock when renaming 2 jobs at the same time















Issue Type:


Bug



Assignee:


Unassigned


Attachments:


copyartifact-deadlock.txt



Components:


copyartifact



Created:


14/Jun/13 9:09 AM



Description:


When a user renames a job, the plugin loops on all jobs to determine if it is using the plugin. However Project#getBuildersList is synchronized, so if several job renames happen, they deadlock each other because each thread already locks the jobs that is being renamed.




Project:


Jenkins



Priority:


Blocker



Reporter:


Vincent Latombe

























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







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

[JIRA] [rebuild] (JENKINS-18348) Failed to use rebuild function - Class not found

2013-06-14 Thread joey.jia...@gmail.com (JIRA)















































Joey Jiao
 created  JENKINS-18348


Failed to use rebuild function - Class not found















Issue Type:


Bug



Assignee:


ragesh_nair



Components:


rebuild



Created:


14/Jun/13 9:25 AM



Description:


Rebuild not show up.

Error log as below:
WARNING: Failed to load com.sonyericsson.rebuild.RebuildProjectActionFactory
java.lang.InstantiationException: file:/var/lib/jenkins/plugins/rebuild/WEB-INF/classes/META-INF/annotations/hudson.Extension might need to be rebuilt: java.lang.ClassNotFoundException: com.sonyericsson.rebuild.RebuildProjectActionFactory
	at net.java.sezpoz.IndexItem.element(IndexItem.java:144)
	at hudson.ExtensionFinder$GuiceFinder$SezpozModule.configure(ExtensionFinder.java:504)
	at com.google.inject.AbstractModule.configure(AbstractModule.java:62)
	at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:229)
	at com.google.inject.spi.Elements.getElements(Elements.java:103)
	at com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:136)
	at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104)
	at com.google.inject.internal.InjectorImpl.createChildInjector(InjectorImpl.java:216)
	at hudson.ExtensionFinder$GuiceFinder.refresh(ExtensionFinder.java:336)
	at jenkins.model.Jenkins.refreshExtensions(Jenkins.java:2123)
	at hudson.PluginManager.dynamicLoad(PluginManager.java:410)
	at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1310)
	at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
	at java.util.concurrent.FutureTask.run(FutureTask.java:123)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
	at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.ClassNotFoundException: com.sonyericsson.rebuild.RebuildProjectActionFactory
	at hudson.PluginManager$UberClassLoader.findClass(PluginManager.java:964)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
	at net.java.sezpoz.IndexItem.element(IndexItem.java:134)
	... 18 more

Jun 14, 2013 5:10:20 PM hudson.ExtensionFinder$GuiceFinder$SezpozModule configure
WARNING: Failed to load com.sonyericsson.rebuild.RebuildActionFactory
java.lang.InstantiationException: file:/var/lib/jenkins/plugins/rebuild/WEB-INF/classes/META-INF/annotations/hudson.Extension might need to be rebuilt: java.lang.ClassNotFoundException: com.sonyericsson.rebuild.RebuildActionFactory
	at net.java.sezpoz.IndexItem.element(IndexItem.java:144)
	at hudson.ExtensionFinder$GuiceFinder$SezpozModule.configure(ExtensionFinder.java:504)
	at com.google.inject.AbstractModule.configure(AbstractModule.java:62)
	at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:229)
	at com.google.inject.spi.Elements.getElements(Elements.java:103)
	at com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:136)
	at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104)
	at com.google.inject.internal.InjectorImpl.createChildInjector(InjectorImpl.java:216)
	at hudson.ExtensionFinder$GuiceFinder.refresh(ExtensionFinder.java:336)
	at jenkins.model.Jenkins.refreshExtensions(Jenkins.java:2123)
	at hudson.PluginManager.dynamicLoad(PluginManager.java:410)
	at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1310)
	at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
	at java.util.concurrent.FutureTask.run(FutureTask.java:123)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
	at java.lang.Thread.run(Thread.java:595)
Caused by:

[JIRA] [integrity-plugin] (JENKINS-18335) PTC Integrity Plugin throws SQL Exception: Der Datenstrom- oder LOB-Wert kann nicht mehrmals abgerufen werden

2013-06-14 Thread cletusdso...@hotmail.com (JIRA)















































Cletus DSouza
 commented on  JENKINS-18335


PTC Integrity Plugin throws SQL Exception: Der Datenstrom- oder LOB-Wert kann nicht mehrmals abgerufen werden















Reproduce the error on a new job and send the 'full' debug log output.

With regard to the transition from 1.12 to 1.13 there was an architectural change in caching.  From a serialized file system object to a database.  Unfortunately, there's nothin I could do to maintain backward compatibility.



























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







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

[JIRA] [gerrit-trigger] (JENKINS-12690) JenkinsTrigger does not understand SSH Key with a password

2013-06-14 Thread nii...@java.net (JIRA)















































niiico
 commented on  JENKINS-12690


JenkinsTrigger does not understand SSH Key with a password















Same problem here. This is a major security issue!



























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







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

[JIRA] [groovy] (JENKINS-18349) Allow to use @Grab in a Script Console

2013-06-14 Thread msz...@wp.pl (JIRA)















































Marcin Zajączkowski
 created  JENKINS-18349


Allow to use @Grab in a Script Console















Issue Type:


Bug



Affects Versions:


current



Assignee:


vjuranek



Components:


groovy



Created:


14/Jun/13 10:24 AM



Description:


Currently @Grab works only in Groovy scripts run on a forked JVM. In a Script Console and System Groovy Scripts it ends with:

FATAL: org/apache/ivy/core/report/ResolveReport
java.lang.NoClassDefFoundError: org/apache/ivy/core/report/ResolveReport


It is sometimes useful to be able to extend script abilities with external libs (like HTTP Builder).




Project:


Jenkins



Priority:


Minor



Reporter:


Marcin Zajączkowski

























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







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

[JIRA] [clone-workspace] (JENKINS-18350) Add option for skipping copying / restoring old builds of workspaces

2013-06-14 Thread lukas.goorm...@dlr.de (JIRA)















































Lukas Goormann
 created  JENKINS-18350


Add option for skipping copying / restoring old builds of workspaces















Issue Type:


Improvement



Assignee:


abayer



Components:


clone-workspace, clone-workspace-scm



Created:


14/Jun/13 11:48 AM



Description:


A project using a cloned workspace as input allways restores / copies the workspace, no matter, if it has changed or not.

It would be nice to be able to skip that step, in case the input-workspace has not changed / was not rebuild.

In our case I have a prebuild slow-changing workspace as start environment for testing some rapidly changing modules (using some scripts to update them). Here it would be usefull, if the workspace would be restored only, if it has changed.




Project:


Jenkins



Priority:


Major



Reporter:


Lukas Goormann

























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







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

[JIRA] [fingerprint] (JENKINS-18351) Fingerprinting seems to leak Files

2013-06-14 Thread da...@dasz.at (JIRA)















































David Schmitt
 created  JENKINS-18351


Fingerprinting seems to leak Files















Issue Type:


Bug



Assignee:


Marc Sanfacon



Components:


fingerprint



Created:


14/Jun/13 12:01 PM



Description:


When fingerprinting large projects, jenkins fails with the following error message:


Recording fingerprints
ERROR: Failed to record fingerprints
hudson.util.IOException2: Failed to compute digest for /var/lib/jenkins/workspace/zetbox-develop-Linux-Build-3-0/packages/NHibernate-dasz.3.3.3-DASZ2/src/Cfg/MappingSchema/HbmProperty.cs
	at hudson.tasks.Fingerprinter$2.invoke(Fingerprinter.java:243)
	at hudson.tasks.Fingerprinter$2.invoke(Fingerprinter.java:225)
	at hudson.FilePath.act(FilePath.java:905)
	at hudson.FilePath.act(FilePath.java:878)
	at hudson.tasks.Fingerprinter.record(Fingerprinter.java:225)
	at hudson.tasks.Fingerprinter.perform(Fingerprinter.java:121)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726)
	at hudson.model.Run.execute(Run.java:1601)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:241)
Caused by: java.io.FileNotFoundException: /var/lib/jenkins/workspace/zetbox-develop-Linux-Build-3-0/packages/NHibernate-dasz.3.3.3-DASZ2/src/Cfg/MappingSchema/HbmProperty.cs (Too many open files)
	at java.io.FileInputStream.open(Native Method)
	at java.io.FileInputStream.init(FileInputStream.java:137)
	at hudson.FilePath$30.invoke(FilePath.java:1667)
	at hudson.FilePath$30.invoke(FilePath.java:1664)
	at hudson.FilePath.act(FilePath.java:905)
	at hudson.FilePath.act(FilePath.java:878)
	at hudson.FilePath.digest(FilePath.java:1664)
	at hudson.tasks.Fingerprinter$2.invoke(Fingerprinter.java:241)
	... 14 more
Build step 'Record fingerprints of files to track usage' changed build result to FAILURE
Finished: FAILURE





Environment:


jenkins 1.5.18; debian squeeze; jenkins package




Project:


Jenkins



Labels:


fingerprints




Priority:


Major



Reporter:


David Schmitt

























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







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

[JIRA] [perforce] (JENKINS-18346) Corruption of workspace due to unfull parameters substitution (no validation)















































Oleg Nenashev
 commented on  JENKINS-18346


Corruption of workspace due to unfull parameters substitution (no validation)















Pull request, which partially resolves issue:
https://github.com/jenkinsci/perforce-plugin/pull/29



























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







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

[JIRA] [jquery] (JENKINS-17310) URL in the project description without https:// don't work

2013-06-14 Thread vander...@mail.ru (JIRA)















































Andrey Sorokovikov
 commented on  JENKINS-17310


URL in the project description without https:// dont work















version "Jenkins ver. 1.518" is now established,the link without http doesn't work . in version 1.4xx worked



























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







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

[JIRA] [ruby-runtime] (JENKINS-18311) Jenkins 1.518 fails to load plugin ruby-runtime

2013-06-14 Thread peek824545...@gmail.com (JIRA)















































Yuu Yamashita
 commented on  JENKINS-18311


Jenkins 1.518 fails to load plugin ruby-runtime















Updating ruby-runtime of jenkins.rb to the lastest development (+my patch) version fixes the problem on my installation of 1.518. I created issues on github for this.


	https://github.com/jenkinsci/jenkins.rb/pull/81
	https://github.com/jenkinsci/jenkins.rb/issues/82





























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







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

[JIRA] [crowd2] (JENKINS-16703) Too many periodic requests to Crowd server















































rzanner
 commented on  JENKINS-16703


Too many periodic requests to Crowd server















Somehow this is related to my newly opened issue JENKINS-18253 which I will close as a duplicate now. 

Anyway - this is a serious issue. We needed to switch the crowd2 plugin off since our Crowd server was not able to handle all the requests coming from Jenkins. Using tcpdump we measured up to 4000 requests per minute!!!



























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







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

[JIRA] [crowd2] (JENKINS-18253) Jenkins runs slow after crowd2 integration, Session validation interval is not stored/used?
















































rzanner
 closed  JENKINS-18253 as Duplicate


Jenkins runs slow after crowd2 integration, 	Session validation interval is not stored/used?
















duplicate of JENKINS-16703





Change By:


rzanner
(14/Jun/13 12:37 PM)




Status:


Open
Closed





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







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

[JIRA] [favorite] (JENKINS-14916) Stackoverflow in annonymous mode















































Walter Kacynski
 commented on  JENKINS-14916


Stackoverflow in annonymous mode















I have confirmed that adding READ-View Permissions fixes this problem for me.  I don't use the favorite plugin.



























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







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

[JIRA] [core] (JENKINS-14916) Stackoverflow in annonymous mode















































Walter Kacynski
 updated  JENKINS-14916


Stackoverflow in annonymous mode
















Change By:


Walter Kacynski
(14/Jun/13 12:57 PM)




Component/s:


core





Component/s:


favorite



























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







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

[JIRA] [crowd2] (JENKINS-16703) Too many periodic requests to Crowd server















































rzanner
 updated  JENKINS-16703


Too many periodic requests to Crowd server
















I attached the log file of a single  login after a Jenkins restart. However, it is still incomplete and contains the last 760 or so lines!

(I used the "System Log" facility in "Manage Jenkins" to turn on "ALL" logging for "de.theit.jenkins.crowd" and "com.atlassian.crowd.integration" loggers.)

The requests from Jenkins to the Crowd server just won't stop - the plugin implementation seems to login on every HTTP request to Jenkins! 
Since Jenkins is AJAX featured and authentication is realized by the CrowdServletFilter, it really should be performant and avoid any superfluous requests to the Crowd server...





Change By:


rzanner
(14/Jun/13 12:57 PM)




Attachment:


jenkins.log



























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







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

[JIRA] [extensible-choice-parameter] (JENKINS-18295) how to execute ct lsbl from unix Extensible choice build parameter groovy script

2013-06-14 Thread de...@ikedam.jp (JIRA)















































ikedam
 commented on  JENKINS-18295


how to execute ct lsbl from unix Extensible choice build parameter groovy script















You should return an array of strings like this:

return [ "choice1", "choice2", "choice3" ]


I did not test, but what you want can be done like this:

def list = 'lsbl -stream Strem@/vob/pvob -short'.execute().text
def ret = []
list.eachLine{ ret.add(it) }
return ret




























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







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

[JIRA] [core] (JENKINS-14916) Stackoverflow in annonymous mode















































Walter Kacynski
 updated  JENKINS-14916


Stackoverflow in annonymous mode
















Change By:


Walter Kacynski
(14/Jun/13 1:11 PM)




Component/s:


role-strategy



























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







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

[JIRA] [core] (JENKINS-14916) Stackoverflow in annonymous mode















































Walter Kacynski
 updated  JENKINS-14916


Stackoverflow in annonymous mode
















Change By:


Walter Kacynski
(14/Jun/13 1:09 PM)




Attachment:


jenkins.err.log



























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







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

[JIRA] [core] (JENKINS-14916) Stackoverflow in annonymous mode















































Walter Kacynski
 updated  JENKINS-14916


Stackoverflow in annonymous mode
















Change By:


Walter Kacynski
(14/Jun/13 1:28 PM)




Assignee:


DanielPetisme





Component/s:


view-job-filters



























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







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

[JIRA] [crowd2] (JENKINS-16703) Too many periodic requests to Crowd server















































rzanner
 commented on  JENKINS-16703


Too many periodic requests to Crowd server















It seems that the CrowdServletFilter sometimes recreates the Authentication using autoLogin(), although it should already be available in the Spring SecurityContext. Shouldn't the SecurityContext be stored in the HttpSession? Otherwise every AJAX request of Jenkins may end up creating a new Spring SecurityContext, since its default strategy is "ThreadLocal"...



























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







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

[JIRA] [core] (JENKINS-14916) Stackoverflow in annonymous mode















































Walter Kacynski
 commented on  JENKINS-14916


Stackoverflow in annonymous mode















I found that by using the Unclassified job filter and not having  READ View Permission this problem occurs.



























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







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

[JIRA] [android-emulator] (JENKINS-8373) Unable to locate sdk for newer android configurations (r07, r08)

2013-06-14 Thread martin.krisc...@noser.com (JIRA)















































Martin Krischik
 commented on  JENKINS-8373


Unable to locate sdk for newer android configurations (r07, r08)















Super. Does not work is not a defect. What do you consider then a defect? When the planet implodes?



























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







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

[JIRA] [integrity-plugin] (JENKINS-18335) PTC Integrity Plugin throws SQL Exception: Der Datenstrom- oder LOB-Wert kann nicht mehrmals abgerufen werden

2013-06-14 Thread tobias.we...@itac.de (JIRA)















































Tobias Weier
 commented on  JENKINS-18335


PTC Integrity Plugin throws SQL Exception: Der Datenstrom- oder LOB-Wert kann nicht mehrmals abgerufen werden















I have found the point, that obviously produces the error in the updated plugin: We operate in an JEE Application Server - GlassFish Server Open Source Edition (3.1.2.2).

If I start Jenkins as a normal java process, the upgraded plugin is working (after deletion of prior builds).

Do you have any ideas, why the environment of the application server produces this error?



























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







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

[JIRA] [integrity-plugin] (JENKINS-18335) PTC Integrity Plugin throws SQL Exception: Der Datenstrom- oder LOB-Wert kann nicht mehrmals abgerufen werden

2013-06-14 Thread tobias.we...@itac.de (JIRA)













































 
Tobias Weier
 edited a comment on  JENKINS-18335


PTC Integrity Plugin throws SQL Exception: Der Datenstrom- oder LOB-Wert kann nicht mehrmals abgerufen werden
















I have found the point, that obviously produces the error in the updated plugin: We operate in an JEE Application Server - GlassFish Server Open Source Edition (3.1.2.2).

If I start Jenkins as a normal java process, the upgraded plugin is working (after deletion of prior builds).

Do you have any ideas, why the environment of the application server leads to this error in the plugin?



























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







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

[JIRA] [thinBackup] (JENKINS-18093) thinBackup stops if there's no unstable build

2013-06-14 Thread tofuatj...@java.net (JIRA)
















































Thomas Fürer
 resolved  JENKINS-18093 as Duplicate


thinBackup stops if theres no unstable build
















Change By:


Thomas Fürer
(14/Jun/13 2:54 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







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

[JIRA] [core] (JENKINS-18352) hpi:run does not work on a bundled plugin

Jesse Glick
created JENKINS-18352

hpi:run does not work on a bundled plugin

Issue Type:

Bug

Assignee:

Unassigned

Components:

core

Created:

14/Jun/13 2:58 PM

Description:

Retroactively filing so as to be considered for backport.

mvn -f subversion-plugin/pom.xml hpi:run does not work: you will not get the version under development, but rather 1.26. (Via jenkins-test-harness; not even the 1.34 bundled in Jenkins 1.466 WAR!) The console shows:

... hudson.PluginManager$1$3$1 isDuplicate
INFO: Ignoring .../subversion-plugin/./work/plugins/subversion.hpl because .../subversion-plugin/./work/plugins/subversion.jpi is already loaded

If you change the parent POM to 1.513, it works, because this regression (from https://github.com/jenkinsci/jenkins/commit/32d5c23 in 1.448) was fixed in https://github.com/jenkinsci/jenkins/commit/7547681a24fadab2a909729413b9f16da90b2d16 in 1.512 then https://github.com/jenkinsci/jenkins/commit/5aa4af75c2c4c66541f1fd24ef82c5d46a79940d in 1.513.

Project:

Jenkins

Labels:

plugin
lts-candidate

Priority:

Major

Reporter:

Jesse Glick

[JIRA] [deploy] (JENKINS-18243) Cannot Download plugins.

2013-06-14 Thread sandeep.bhano...@gmail.com (JIRA)















































Sandeep Bhanoori
 commented on  JENKINS-18243


Cannot Download plugins.















Yes i have tried to update the URL too but for some reason it stays pending Via Jnekins GUI. But i was able to download from home. I'm not sure what is blocking it. You can close this 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







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

[JIRA] [ldap] (JENKINS-17281) Please add a config option for groupSearchFilter

SCM/JIRA link daemon
commented on JENKINS-17281

Please add a config option for groupSearchFilter

Code changed in jenkins
User: Stephen Connolly
Path:
src/main/java/hudson/security/LDAPSecurityRealm.java
src/main/resources/hudson/security/LDAPSecurityRealm/config.jelly
src/main/resources/hudson/security/LDAPSecurityRealm/help-cache.html
src/main/webapp/help-cache.html
src/main/webapp/help-groupMembershipFilter.html
src/main/webapp/help-groupSearchFilter.html
http://jenkins-ci.org/commit/ldap-plugin/72a91027abbc544f11020ec8e20d8717451da4d7
Log:
FIXES JENKINS-17281 Adding configuration options for the filters used to search for groups.

It is somewhat confusing that there are two `group search filters` so I have decided to rename one.
The new name for the `groupSearchFilter` that is controlled from `LDAPBindSecurityRealm.groovy` is the
`groupMembershipFilter` as this filter is used to determine what groups a specific user is a member of
That leaves `groupSearchFilter` as a nice clean name for the filter to search for named groups.
This should still respect any existing configuration, i.e. leaving these fields blank will leave the
existing defaults or existing overrides in place... but it will make life easier for users going forward
Took quite some digging to figure out exactly what these filters were for... hopefully I have left things
in a more obvious framing for anyone else following
I would like a better way to apply the `groupMembershipFilter` override, but this was the cleanest way
I could maintain backwards compatibility

[JIRA] [ldap] (JENKINS-17281) Please add a config option for groupSearchFilter

SCM/JIRA link daemon
commented on JENKINS-17281

Please add a config option for groupSearchFilter

Code changed in jenkins
User: Stephen Connolly
Path:
src/main/java/hudson/security/LDAPSecurityRealm.java
src/main/resources/hudson/security/LDAPSecurityRealm/config.jelly
src/main/resources/hudson/security/LDAPSecurityRealm/help-cache.html
src/main/webapp/help-cache.html
src/main/webapp/help-groupMembershipFilter.html
src/main/webapp/help-groupSearchFilter.html
http://jenkins-ci.org/commit/ldap-plugin/50ab44128e55f73dd14d347ea2c890df784a54e4
Log:
FIXES JENKINS-17281 Adding configuration options for the filters used to search for groups.

It is somewhat confusing that there are two 'group search filters' so I have decided to rename one.
The new name for the 'groupSearchFilter' that is controlled from is the
as this filter is used to determine what groups a specific user is a member of
That leaves as a nice clean name for the filter to search for named groups.
This should still respect any existing configuration, i.e. leaving these fields blank will leave the
existing defaults or existing overrides in place... but it will make life easier for users going forward
Took quite some digging to figure out exactly what these filters were for... hopefully I have left things
in a more obvious framing for anyone else following
I would like a better way to apply the override, but this was the cleanest way
I could maintain backwards compatibility

[JIRA] [core] (JENKINS-18352) hpi:run does not work on a bundled plugin
















































SCM/JIRA link daemon
 resolved  JENKINS-18352 as Fixed


hpi:run does not work on a bundled plugin
















Change By:


SCM/JIRA link daemon
(14/Jun/13 3:33 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [core] (JENKINS-18352) hpi:run does not work on a bundled plugin















































SCM/JIRA link daemon
 commented on  JENKINS-18352


hpi:run does not work on a bundled plugin















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
http://jenkins-ci.org/commit/jenkins/0e1bc560ae7f066a2fb366bc78771224df07d278
Log:
  FIXED JENKINS-18352 Retroactively filing.






























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







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

[JIRA] [ldap] (JENKINS-17281) Please add a config option for groupSearchFilter

2013-06-14 Thread stephenconno...@java.net (JIRA)
















































stephenconnolly
 resolved  JENKINS-17281 as Fixed


Please add a config option for groupSearchFilter
















Fixed in 1.5 release





Change By:


stephenconnolly
(14/Jun/13 3:35 PM)




Status:


Open
Resolved





Assignee:


KohsukeKawaguchi
stephenconnolly





Resolution:


Fixed



























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







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

[JIRA] [core] (JENKINS-18354) Status page popup an Error 330 (net::ERR_CONTENT_DECODING_FAILED)

2013-06-14 Thread thouda...@ludia.com (JIRA)

T. Houdayer
created JENKINS-18354

Status page popup an Error 330 (net::ERR_CONTENT_DECODING_FAILED)

Issue Type:

Bug

Assignee:

Unassigned

Attachments:

1.515-fix-ChangesInDependencies.patch, GlobalSecurity-setting.png, ProjectB-security.png

Components:

core

Created:

14/Jun/13 3:34 PM

Description:

We have an issue with the Status page of some projects build in Jenkins (v1.515). Some of my users, which don't have access to all Jenkins projects but a part of them, cannot display correctly some status page, they receive an "Error 330 (net::ERR_CONTENT_DECODING_FAILED)".
After some investiguation, I found that this issue came from the "Changes in dependencies" part of the status page: As soon as an artifact copied into the current build came from another build that user doesn't have acces, the error popup.

How to reproduce:

In "Configure Global Security" page of Jenkins, the "Project-based Matrix Authorization Strategy" is activated and the authorization are given by the image "GlobalSecurity-setting.png" in attachment.

Now imagine 2 projects A and B. The user, called Bob, had access to B but not A (via the project-base security feature in Jenkins). Project B security is given by the image "ProjectB-security.png" in attachment.

A font file (.ttf) is checked out from a build of project A, called A#1. Some other process are made in A#1, then it archive some file, including the .ttf file (which was not modified during the process).

The same font file is checked out from a build of project B, called B#1. Some process after, B#1 is also archiving the .ttf file.

Now Bob try to access the status page of the build B#1. The "Changes in dependencies" part of this page is trying to make some dependency links between projects based on the fingerprint of used artifacts. It found the .ttf font with a fingerprint which lead it to the build A#1, so it try to retrieve some info from this A#1 build. Because Bob cannot access any builds of project A, an error occure: " Error 330 (net::ERR_CONTENT_DECODING_FAILED)".

Patch:
I patch the source of Jenkins 1.515 by just removing the "Changes in dependencies" part in the file "core/src/main/resources/hudson/model/AbstractBuild/index.jelly".

Environment:

Jenkins 1.515, jenkins server under Lunix (Debian 6.0.7)

Project:

Jenkins

Labels:

jenkins

Priority:

Major

Reporter:

T. Houdayer

[JIRA] [ldap] (JENKINS-17661) LDAPBindSecurityRealm.groovy not included on jenkins.war file

2013-06-14 Thread stephenconno...@java.net (JIRA)
















































stephenconnolly
 resolved  JENKINS-17661 as Fixed


LDAPBindSecurityRealm.groovy not included on jenkins.war file
















Version 1.5 of the plugin allows configuration of the primary setting that 99% of people needed to modify this file in order to get LDAP working... so the presence of the file is no longer critical.

Also the default template for the file is now in $JENKINS_HOME/plugins/ldap/WEB-INF/classes/hudson/security/LDAPBindSecurityRealm.groovy (as documented on the wiki page)

Closing this issue on that basis





Change By:


stephenconnolly
(14/Jun/13 3:38 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [ldap] (JENKINS-18355) LDAP does not populate Your Name field















































Walter Kacynski
 created  JENKINS-18355


LDAP does not populate Your Name field















Issue Type:


Bug



Assignee:


Kohsuke Kawaguchi



Components:


ldap



Created:


14/Jun/13 3:56 PM



Description:


I have noticed that since switching from the AD plugin to the LDAP plugin full user names are no longer populated in the user profiles when users first login.

Is there something that I don't have configured correctly.




Project:


Jenkins



Priority:


Minor



Reporter:


Walter Kacynski

























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







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

[JIRA] [token-macro] (JENKINS-18271) TokenMacro.expand() duplicates private macros when called multiple times

2013-06-14 Thread tth...@free.fr (JIRA)















































T Thery
 commented on  JENKINS-18271


TokenMacro.expand() duplicates private macros when called multiple times















Same issue here.
Everytime the expand() function is called by the email-ext plugin, the all() list is extended with the provided private variables.

One visible impact is the access time to the configure of jenkins jobs using this plugin. Indeed the configure contains the list of all available tokens in the 'Content Token Reference' help. In our context, it might takes up to 2 minutes to access the configure page, the 'Content Token Reference' help being as big as 5 lines, and of course continue tho degrade over time with additional call to expand() function.



























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







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

[JIRA] [core] (JENKINS-18351) Fingerprinting seems to leak Files

2013-06-14 Thread ku...@gmx.de (JIRA)















































kutzi
 updated  JENKINS-18351


Fingerprinting seems to leak Files
















Change By:


kutzi
(14/Jun/13 4:10 PM)




Assignee:


MarcSanfacon
kutzi





Component/s:


core





Component/s:


fingerprint



























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







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

[JIRA] [core] (JENKINS-18351) Fingerprinting seems to leak Files

2013-06-14 Thread ku...@gmx.de (JIRA)















































kutzi
 commented on  JENKINS-18351


Fingerprinting seems to leak Files















Yeah, looks like you're right. FilePath#digest opens a new FileInputstream but never closes it explicitly
https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/FilePath.java#L1663



























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







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

[JIRA] [core] (JENKINS-18352) hpi:run does not work on a bundled plugin















































dogfood
 commented on  JENKINS-18352


hpi:run does not work on a bundled plugin















Integrated in  jenkins_main_trunk #2609
 FIXED JENKINS-18352 Retroactively filing. (Revision 0e1bc560ae7f066a2fb366bc78771224df07d278)

 Result = SUCCESS
Jesse Glick : 0e1bc560ae7f066a2fb366bc78771224df07d278
Files : 

	changelog.html





























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







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

[JIRA] [git] (JENKINS-18303) Cannot do checkout of a git repository in BitBucket in Jenkins

2013-06-14 Thread gregory.boissi...@gmail.com (JIRA)















































Gregory Boissinot
 updated  JENKINS-18303


Cannot do checkout of a git repository in BitBucket in Jenkins
















Change By:


Gregory Boissinot
(14/Jun/13 4:22 PM)




Component/s:


git





Component/s:


buildcontext-capture



























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







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

[JIRA] [viewVC] (JENKINS-18283) Wrong URL in diff

2013-06-14 Thread ducquoc...@gmail.com (JIRA)















































Duc Quoc
 commented on  JENKINS-18283


Wrong URL in diff















I've opened a pull request for this issue
https://github.com/jenkinsci/viewVC-plugin/pull/4



























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







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

[JIRA] [android-emulator] (JENKINS-8373) Unable to locate sdk for newer android configurations (r07, r08)

2013-06-14 Thread ch...@orr.me.uk (JIRA)















































Christopher Orr
 commented on  JENKINS-8373


Unable to locate sdk for newer android configurations (r07, r08)















Hi Martin, thank you for your level-headed comment on this 2.5 year-old issue. Indeed, this was not a defect in version 1.5 of the plugin, which was the current version at the time.

If you are having problems, please open a new bug with exact details of what does not work, and in which environment.

Thanks.



























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







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

[JIRA] [core] (JENKINS-18351) Fingerprinting seems to leak Files















































SCM/JIRA link daemon
 commented on  JENKINS-18351


Fingerprinting seems to leak Files















Code changed in jenkins
User: Christoph Kutzinski
Path:
 changelog.html
 core/src/main/java/hudson/FilePath.java
http://jenkins-ci.org/commit/jenkins/93c31be1b75940dfd2e8a3c5954a4d57f4c8e6d5
Log:
  FIXED JENKINS-18351 file descriptor leak while fingerprinting






























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







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

[JIRA] [core] (JENKINS-18351) Fingerprinting seems to leak Files
















































SCM/JIRA link daemon
 resolved  JENKINS-18351 as Fixed


Fingerprinting seems to leak Files
















Change By:


SCM/JIRA link daemon
(14/Jun/13 5:02 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [build-pipeline] (JENKINS-18356) Incompatible signature change in 1.489: AbstractProject.doBuild















































Jesse Glick
 created  JENKINS-18356


Incompatible signature change in 1.489: AbstractProject.doBuild















Issue Type:


Bug



Assignee:


Jesse Glick



Components:


build-pipeline, core



Created:


14/Jun/13 5:05 PM



Description:


https://github.com/jenkinsci/jenkins/commit/15ba345 was incompatible. au.com.centrumsystems.hudson.plugin.buildpipeline.DownstreamProjectGridBuilder.doBuild is uncompilable against newer cores as a result.




Project:


Jenkins



Labels:


lts-candidate




Priority:


Critical



Reporter:


Jesse Glick

























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







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

[JIRA] [deploy] (JENKINS-18357) Glassfish re-deployment of an EAR fails

2013-06-14 Thread sne...@gmail.com (JIRA)















































Derek E
 created  JENKINS-18357


Glassfish re-deployment of an EAR fails















Issue Type:


Bug



Assignee:


Unassigned


Components:


deploy



Created:


14/Jun/13 5:12 PM



Description:


Using the Deploy to Container plugin for a multi-module Maven job works fine for deploying the EAR files to Glassfish on the first run, but subsequent runs fail due to the previous ear not being undeployed first.

14:40:55 Deploying /var/lib/jenkins/workspace/mycoservices-TRUNK-install/mycoservicesear/target/mycoservicesear-1.2.1-SNAPSHOT.ear to container GlassFish 3.x Remote
14:40:55 ERROR: Publisher hudson.plugins.deploy.DeployPublisher aborted due to exception
14:40:55 org.codehaus.cargo.util.CargoException: Deployment has failed: Action failed Deploying application to target server failed; Error occurred during deployment: Application with name mycoservicesear is already registered. Either specify that redeployment must be forced, or redeploy the application. Or if this is a new deployment, pick a different name. Please see server.log for more details.
14:40:55 
14:40:55   at org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.waitForProgressObject(AbstractJsr88Deployer.java:220)
14:40:55   at org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.deploy(AbstractJsr88Deployer.java:76)
14:40:55   at org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.redeploy(AbstractJsr88Deployer.java:142)
14:40:55   at hudson.plugins.deploy.CargoContainerAdapter.deploy(CargoContainerAdapter.java:64)
14:40:56   at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:90)
14:42:15   at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:77)
14:42:15   at hudson.FilePath.act(FilePath.java:904)
14:42:15   at hudson.FilePath.act(FilePath.java:877)
14:42:15   at hudson.plugins.deploy.CargoContainerAdapter.redeploy(CargoContainerAdapter.java:77)
14:42:15   at hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:47)
14:42:15   at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
14:42:15   at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:802)
14:42:15   at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:774)
14:42:15   at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:949)
14:42:15   at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:724)
14:42:15   at hudson.model.Run.execute(Run.java:1600)
14:42:15   at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477)
14:42:15   at hudson.model.ResourceController.execute(ResourceController.java:88)
14:42:15   at hudson.model.Executor.run(Executor.java:237)




Environment:


Jenkins ver. 1.509.1; Deploy to Container 1.9; GF 3.1.2.2




Project:


Jenkins



Priority:


Major



Reporter:


Derek E

























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







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

[JIRA] [build-pipeline] (JENKINS-18356) Incompatible signature change in 1.489: AbstractProject.doBuild















































SCM/JIRA link daemon
 commented on  JENKINS-18356


Incompatible signature change in 1.489: AbstractProject.doBuild















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
 core/src/main/java/hudson/model/AbstractProject.java
 core/src/main/java/hudson/model/ParametersDefinitionProperty.java
http://jenkins-ci.org/commit/jenkins/fa47981c071bf8c11041d4f11b2be0c73ab0b270
Log:
  FIXED JENKINS-18356 Restored deprecated AbstractProject.doBuild{,WithParameters} overloads.





























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







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

[JIRA] [build-pipeline] (JENKINS-18356) Incompatible signature change in 1.489: AbstractProject.doBuild
















































SCM/JIRA link daemon
 resolved  JENKINS-18356 as Fixed


Incompatible signature change in 1.489: AbstractProject.doBuild
















Change By:


SCM/JIRA link daemon
(14/Jun/13 5:31 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [core] (JENKINS-18351) Fingerprinting seems to leak Files















































dogfood
 commented on  JENKINS-18351


Fingerprinting seems to leak Files















Integrated in  jenkins_main_trunk #2610
 FIXED JENKINS-18351 file descriptor leak while fingerprinting (Revision 93c31be1b75940dfd2e8a3c5954a4d57f4c8e6d5)

 Result = SUCCESS
Christoph Kutzinski : 93c31be1b75940dfd2e8a3c5954a4d57f4c8e6d5
Files : 

	changelog.html
	core/src/main/java/hudson/FilePath.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







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

[JIRA] [jenkinswalldisplay] (JENKINS-18358) Saving system configuration with walldisplay plugin installed throws 500 error on save

2013-06-14 Thread mi...@bullhorn.com (JIRA)















































Michael Chmielewski
 updated  JENKINS-18358


Saving system configuration with walldisplay plugin installed throws 500 error on save
















Change By:


Michael Chmielewski
(14/Jun/13 7:04 PM)




Environment:


CentOS6.3Linux,Tomcat7.0,Jenkins1.514,jenkinswalldisplay
plguin
plugin
0.6.17



























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







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

[JIRA] [jenkinswalldisplay] (JENKINS-18358) Saving system configuration with walldisplay plugin installed throws 500 error on save

2013-06-14 Thread mi...@bullhorn.com (JIRA)















































Michael Chmielewski
 created  JENKINS-18358


Saving system configuration with walldisplay plugin installed throws 500 error on save















Issue Type:


Bug



Assignee:


Unassigned


Components:


jenkinswalldisplay



Created:


14/Jun/13 7:03 PM



Description:


With the wall display plugin enabled, when I save the system configuration for Jenkins (Jenkins - Manage Jenkins - Configure System) I get the following stack trace:


Status Code: 500

Exception: org.apache.commons.beanutils.ConversionException: no protocol: 
Stacktrace:
javax.servlet.ServletException: org.apache.commons.beanutils.ConversionException: no protocol: 
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:719)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:214)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
	at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
	at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
	at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
	at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
	at

[JIRA] [maven] (JENKINS-18359) Pre/postbuild Maven task loses settings configuration on save

2013-06-14 Thread pdavies-jenkin...@karn.co.uk (JIRA)















































Phil Davies
 created  JENKINS-18359


Pre/postbuild Maven task loses settings configuration on save















Issue Type:


Bug



Assignee:


Unassigned


Components:


maven



Created:


14/Jun/13 7:17 PM



Description:


When attempting to set the Settings file or Global Settings file for a Invoke top-level Maven target pre or post-build step, the selected value is never persisted to the job config.xml.

Regardless of what setting I select, I always end up with the following stanza in my config.xml:

prebuilders
hudson.tasks.Maven
  targetsclean package antrun:run/targets
  mavenNamesys-mvn-3.0.4/mavenName
  pom../db-conf/pom.xml/pom
  usePrivateRepositorytrue/usePrivateRepository
  settings class="jenkins.mvn.DefaultSettingsProvider"/
  globalSettings class="jenkins.mvn.DefaultGlobalSettingsProvider"/
/hudson.tasks.Maven
  /prebuilders


If I modify it to the correct configuration as follows


prebuilders
hudson.tasks.Maven
  targetsclean package antrun:run/targets
  mavenNamesys-mvn-3.0.4/mavenName
  pom../db-conf/pom.xml/pom
  usePrivateRepositorytrue/usePrivateRepository
  settings class="org.jenkinsci.plugins.configfiles.maven.job.MvnSettingsProvider" plugin="config-file-provider@2.5.1"
settingsConfigIdorg.jenkinsci.plugins.configfiles.maven.MavenSettingsConfig1371233015754/settingsConfigId
  /settings
  globalSettings class="jenkins.mvn.DefaultGlobalSettingsProvider"/
/hudson.tasks.Maven
  /prebuilders


The job works as expected but will revert to the default provider if I resave the configuration (in the event I need to make additional changes).




Project:


Jenkins



Priority:


Major



Reporter:


Phil Davies

























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







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

[JIRA] [build-pipeline] (JENKINS-18356) Incompatible signature change in 1.489: AbstractProject.doBuild















































dogfood
 commented on  JENKINS-18356


Incompatible signature change in 1.489: AbstractProject.doBuild















Integrated in  jenkins_main_trunk #2611
 FIXED JENKINS-18356 Restored deprecated AbstractProject.doBuild{,WithParameters} overloads. (Revision fa47981c071bf8c11041d4f11b2be0c73ab0b270)

 Result = SUCCESS
Jesse Glick : fa47981c071bf8c11041d4f11b2be0c73ab0b270
Files : 

	core/src/main/java/hudson/model/ParametersDefinitionProperty.java
	core/src/main/java/hudson/model/AbstractProject.java
	changelog.html





























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







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

[JIRA] [maven] (JENKINS-15846) Deadlock during Maven builds Parsing POM step

2013-06-14 Thread abrid...@blackberry.com (JIRA)















































Tony Bridges
 commented on  JENKINS-15846


Deadlock during Maven builds Parsing POM step















For the record, the HashTable workaround does not solve the problem.



























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







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

[JIRA] [jenkinswalldisplay] (JENKINS-18358) Saving system configuration with walldisplay plugin installed throws 500 error on save

2013-06-14 Thread mi...@bullhorn.com (JIRA)
















































Michael Chmielewski
 closed  JENKINS-18358 as Duplicate


Saving system configuration with walldisplay plugin installed throws 500 error on save
















Looks unrelated. Appears to be a jira plugin issue.





Change By:


Michael Chmielewski
(14/Jun/13 7:41 PM)




Status:


Open
Closed





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







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

[JIRA] [teamconcert] (JENKINS-18293) Team Concert plugin cannot cope with symbolic links

2013-06-14 Thread heath...@ca.ibm.com (JIRA)

Heather Fraser-Dube
commented on JENKINS-18293

Team Concert plugin cannot cope with symbolic links

RTC support for symbolic links requires one or two libraries (.dll/.so files).

Eclipse file system natives
RTC file system natives

The reason is Java 6 and earlier don't have support for creating/looking at properties of symbolic links. So RTC uses some C code to manage symbolic links.

Java 7 has symbolic link support that works on linux, but on Windows it has some limitations when creating links when the target has not yet been created (type is defaulted to file which is not good if its a directory).

If you are running Linux and can use Java 7 then the only .so you need is for the Eclipse natives. Otherwise, you will need both.

I'll describe what has to happen on Windows, but the steps are similar for linux.

In the Build engine directory (buildengine\eclipse\plugins), look for the
com.ibm.team.filesystem.client_3.1.600.v20130415_0257.jar
org.eclipse.core.filesystem.win32.x86_1.1.201.R36x_v20100727-0745.jar or equivalent jars for your platform/release.

From the com.ibm.team.filesystem.client jar you want to extract the winfsnatives.dll (libfsnatives.so on linux). Take all the .dll/.so from the org.eclipse.core.filesystem jar. Place them directly in a directory (eg. c:\natives\winfsnatives.dll).

Now when you start Jenkins, we need to tell java about the directory so that it can load the libraries from it. This is done through the -Djava.library.path variable.
eg. java -Djava.library.path="c:\natives;%Path%" -jar jenkins-1.509.1.war

We are just adding to what the default would be for Java. You could also add the directory to your path instead.

I realize the setup is a little convoluted, we could probably help by packaging the toolkit a bit differently. But this might be simpler than trying to load the component through the CLI.

[JIRA] [teamconcert] (JENKINS-18293) Team Concert plugin cannot cope with symbolic links

2013-06-14 Thread heath...@ca.ibm.com (JIRA)















































Heather Fraser-Dube
 commented on  JENKINS-18293


Team Concert plugin cannot cope with symbolic links















Also, looking at the trace included leads me to think that your sandbox (place where the load is occurring) is corrupted. The lack of symbolic link support should have generated a nicer error message. So I would also recommend that you delete everything that has been loaded before you try it out.



























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







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

[JIRA] [copy-to-slave] (JENKINS-18360) Incorrect use of project.getWorkspace()

Jesse Glick
created JENKINS-18360

Incorrect use of project.getWorkspace()

Issue Type:

Bug

Assignee:

Daniel Petisme

Components:

copy-to-slave

Created:

14/Jun/13 8:15 PM

Description:

If you were on GitHub I would probably just file a pull request, but since you are not, the following code in https://svn.jenkins-ci.org/trunk/hudson/plugins/copy-to-slave/src/main/java/com/michelin/cio/hudson/plugins/copytoslave/CopyToMasterNotifier.java looks wrong:

public boolean perform(AbstractBuild build, Launcher launcher, BuildListener listener) throws InterruptedException, IOException {
...
FilePath projectWorkspaceOnSlave = build.getProject().getWorkspace();

This is likely wrong since the project can have many workspaces, and if there are concurrent builds this one may be from a different build. build.getWorkspace() is more correct, and simpler too.

Project:

Jenkins

Labels:

concurrent-build

Priority:

Major

Reporter:

Jesse Glick

[JIRA] [core] (JENKINS-18289) Detect repair out-of-order build records















































Jesse Glick
 commented on  JENKINS-18289


Detect  repair out-of-order build records















A script like the following can be useful for diagnosis:


CANONICAL_ID_FORMATTER = new java.text.SimpleDateFormat("-MM-dd_HH-mm-ss");
NUMBER_XPATH = "/node()/number";
xpath = javax.xml.xpath.XPathFactory.newInstance().newXPath();
for (j in Jenkins.instance.getAllItems(AbstractProject)) {
  d = new File(j.rootDir, 'builds');
  m = new TreeMap();
  for (b in d.listFiles()) {
xml = new File(b, 'build.xml');
if (!xml.file) {
  if (!b.getName().startsWith('last')) {
println("not a build dir: ${b}");
  }
  continue;
}
try {
  CANONICAL_ID_FORMATTER.parse(b.name);
  xpath.reset();
  number = xpath.evaluate(NUMBER_XPATH, new org.xml.sax.InputSource(new java.io.FileReader(xml)), javax.xml.xpath.XPathConstants.NODE);
  if (number) {
m.put(b.name, number.textContent);
  } else {
println("cannot parse ${xml}");
  }
} catch (java.text.ParseException e) {
  if (!Util.isSymlink(b)) {
println("${b} should be a symlink but is not");
  }
}
  }
  original = m.values().collect({Integer.parseInt(it)});
  if (!original.equals(original.sort(false))) {
println("out of order in ${d}: ${m}");
  }
}




























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







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

[JIRA] [teamconcert] (JENKINS-18293) Team Concert plugin cannot cope with symbolic links

2013-06-14 Thread heath...@ca.ibm.com (JIRA)















































Heather Fraser-Dube
 commented on  JENKINS-18293


Team Concert plugin cannot cope with symbolic links















Finally, if you are running on Windows, you need to be sure that you have permission to create symbolic links. The Symbolic links article in the jazz.net library https://jazz.net/library/article/970/ describes how.



























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







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

[JIRA] [core] (JENKINS-18351) Fingerprinting seems to leak Files

2013-06-14 Thread ku...@gmx.de (JIRA)















































kutzi
 commented on  JENKINS-18351


Fingerprinting seems to leak Files















Jesse, where did you see that Util.getDigestOf closes the passed InputStream? I cannot find such a place.
So this issue has probably already been there before https://github.com/jenkinsci/jenkins/commit/9d72311ba0222b9d0489605b8ec2cec711690993

It probably just manifests when fingerprinting a lot of files, since in that case the file descriptor run out, before the GC can discard and close the dangling FileOutputStreams



























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







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

[JIRA] [teamconcert] (JENKINS-18284) Team Concert plugin doesn't load components as root folders

2013-06-14 Thread n.a.ed...@gmail.com (JIRA)















































Nick Edgar
 commented on  JENKINS-18284


Team Concert plugin doesnt load components as root folders















I had made the same suggestion to Danny.  He responded by email with: 
 We’ve already switched to using the Build Definition setting. However it would have been nice if this limitation would have been mentioned somewhere. Or the description of the plugin would describe that for now you support “simple workspace-only config” when using the ‘Just accept and fetch from a build workspace’-setting.

 Expected solution: When you’re utilizing the scm commands, add the ‘-i’ option, as a choice in the Jenkins Job configuration, just as in the Jazz Build Definition: screen shot of Create Folders option.

We could perhaps add something to that effect in the ? help for the simple workspace option.



























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







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

[JIRA] [teamconcert] (JENKINS-18292) Team Concert plugin cannot resolve Jenkins path and Build Definition Jazz Source Control path

2013-06-14 Thread n.a.ed...@gmail.com (JIRA)















































Nick Edgar
 commented on  JENKINS-18292


Team Concert plugin cannot resolve Jenkins path and Build Definition Jazz Source Control path















I had made a similar suggestion by email:

	This is a defect which we'll investigate (it's supposed to use the full path if given, and only append to Jenkins workspace path if relative).
	For now, please specify a relative path in the build definition, or use "." if you want to use the Jenkins workspace directory directly.



Danny responded with:
 We’ve already switched to a relative path setting in the 'Load Directory'-setting of the 'Jazz Source Control'-tab in the Build Definition. Good suggestion to use the “.” here, thanks.



























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







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

[JIRA] [teamconcert] (JENKINS-18293) Team Concert plugin cannot cope with symbolic links

2013-06-14 Thread n.a.ed...@gmail.com (JIRA)

Nick Edgar
commented on JENKINS-18293

Team Concert plugin cannot cope with symbolic links

Danny had responded by email (before Heather's responses above):
This is a tricky one, since the ability to create a symbolic link can also be limited by the OS (Win 7 supports it, by requires updated user application security settings. Win XP requires a patch). However the system and userids I’m using are set-up to allow the creation of symbolic links. Therefore it stands to reason it’s either the application security settings, or the ‘inability’ of the application.
Regarding the ability of the application: If you’re utilizing the (l)scm load command, it usually does create the symbolic links when we start it from the command line in a CMD file ourselves. If run the same CMD file in a Jenkins Job, it usually doesn’t. We haven’t been able to figure out why…
Regarding the security settings to allow creation of symlinks: Can you indicate what the (user/application security) settings should be, to allow the plugin to create symbolic links on Win7?
You have a good suggestion, but it’s only a workaround. We’re currently looking into it.

Hopefully the article Heather linked to above helps with the question of settings.

[JIRA] [core] (JENKINS-18351) Fingerprinting seems to leak Files















































Jesse Glick
 reopened  JENKINS-18351


Fingerprinting seems to leak Files
















My mistake, regressed from another commit: https://github.com/jenkinsci/jenkins/commit/51fbd2d





Change By:


Jesse Glick
(14/Jun/13 10:08 PM)




Resolution:


Fixed





Status:


Resolved
Reopened





Assignee:


kutzi
JesseGlick



























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







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

[JIRA] [core] (JENKINS-18351) Fingerprinting seems to leak Files
















































SCM/JIRA link daemon
 resolved  JENKINS-18351 as Fixed


Fingerprinting seems to leak Files
















Change By:


SCM/JIRA link daemon
(14/Jun/13 10:11 PM)




Status:


Reopened
Resolved





Resolution:


Fixed



























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







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

[JIRA] [core] (JENKINS-18351) Fingerprinting seems to leak Files















































SCM/JIRA link daemon
 commented on  JENKINS-18351


Fingerprinting seems to leak Files















Code changed in jenkins
User: Jesse Glick
Path:
 core/src/main/java/hudson/FilePath.java
 core/src/main/java/hudson/Util.java
http://jenkins-ci.org/commit/jenkins/7f966f6f312f18bfc8a11166b1b2ebf474965ddb
Log:
  FIXED JENKINS-18351 Better fix for file handle leak.






























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







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

[JIRA] [twitter] (JENKINS-18302) TwitterException in Auth.jar















































Michael Irwin
 commented on  JENKINS-18302


TwitterException in Auth.jar















I'm getting the same exception.



























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







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

[JIRA] [jenkins-multijob-plugin] (JENKINS-18361) Provide build report API support

2013-06-14 Thread dkich...@gmail.com (JIRA)















































Dave Kichler
 created  JENKINS-18361


Provide build report API support















Issue Type:


Improvement



Affects Versions:


current



Assignee:


Unassigned


Components:


jenkins-multijob-plugin



Created:


14/Jun/13 11:19 PM



Description:


Standard jobs provide API endpoints for inspecting job statuses from other applications.  This would be extremely useful for multijobs as well, particularly if there were a way to retrieve the build numbers of the downstream project thats were triggered from a given multijob top level build.  

Ie http://jenkins/job/MultijobJob/5/api/json  would return a basic json report including the same that is displayed on the status web interface when visiting a build page.  

Should also work for /lastSuccessfulBuild, etc as well.




Project:


Jenkins



Labels:


api
json
multijob




Priority:


Major



Reporter:


Dave Kichler

























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







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

[JIRA] [jenkins-multijob-plugin] (JENKINS-18361) Provide build report API support

2013-06-14 Thread dkich...@gmail.com (JIRA)















































Dave Kichler
 updated  JENKINS-18361


Provide build report API support
















Change By:


Dave Kichler
(14/Jun/13 11:22 PM)




Description:


StandardjobsprovideAPIendpointsforinspectingjobstatusesfromotherapplications.Thiswouldbeextremelyusefulformultijobsaswell,particularlyiftherewereawaytoretrievethebuildnumbersofthedownstream
projectthats
projectsthat
weretriggeredfromagivenmultijobtoplevelbuild.Iehttp://jenkins/job/MultijobJob/5/api/jsonwouldreturnabasicjsonreportincludingthesame
info
thatisdisplayedonthestatuswebinterfacewhenvisitingabuildpage.Shouldalsoworkfor/lastSuccessfulBuild,etcaswell.



























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







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

[JIRA] [jenkins-multijob-plugin] (JENKINS-18361) Provide build report API support

2013-06-14 Thread dkich...@gmail.com (JIRA)















































Dave Kichler
 updated  JENKINS-18361


Provide build report API support
















Change By:


Dave Kichler
(14/Jun/13 11:23 PM)




Description:


StandardjobsprovideAPIendpointsforinspectingjobstatusesfromotherapplications.Thiswouldbeextremelyusefulformultijobsaswell,particularlyiftherewereawaytoretrievethebuildnumbersofthedownstreamprojectsthatweretriggeredfromagivenmultijobtoplevelbuild.Iehttp://jenkins/job/MultijobJob/5/api/jsonwouldreturnabasicjsonreportincludingthesameinfothatisdisplayed
on
in
the
status
webinterfacewhenvisitingabuild
status
page.Shouldalsoworkfor/lastSuccessfulBuild,etcaswell.



























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







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

[JIRA] [twitter] (JENKINS-18302) TwitterException in Auth.jar















































Michael Irwin
 updated  JENKINS-18302


TwitterException in Auth.jar
















Patch to update the plugin to use Twitter4J 3.0.3, which also fixes the exception here.





Change By:


Michael Irwin
(14/Jun/13 11:26 PM)




Attachment:


fix.diff



























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







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

[JIRA] [twitter] (JENKINS-18302) TwitterException in Auth.jar















































Michael Irwin
 commented on  JENKINS-18302


TwitterException in Auth.jar















Just committed the patch (didn't know I was able to commit directly to the SVN repo).



























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







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

[JIRA] [twitter] (JENKINS-18302) TwitterException in Auth.jar













































 
Michael Irwin
 edited a comment on  JENKINS-18302


TwitterException in Auth.jar
















Just committed the patch (didn't know I was able to commit directly to the SVN repo). Revision 40906



























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







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

[JIRA] [core] (JENKINS-18351) Fingerprinting seems to leak Files