[JIRA] (JENKINS-13855) Parallel deployment to Tomcat 7 with deploy plugin throws exception and fails the build

2012-07-24 Thread trex...@gmx.de (JIRA) 














































Daniel Barth
 commented on  JENKINS-13855


Parallel deployment to Tomcat 7 with deploy plugin throws exception and fails the build















I found an corresponding issue in the Cargo Jira:

https://jira.codehaus.org/browse/CARGO-1041

I'm also working on updating the deploy plugin to the latest Cargo version (1.2.3).
I forked the GitHub repo (username trexter) and did the changes to use Cargo 1.2.3,
the plugin is compiling and building fine in Eclipse. 

I get the .hpi and I can upload and install it in Jenkins 1.473. I can see it under
installed plugins with correct version number (used 1.10) but I cannot add it to a
(freestyle) job, it's not showing up in the post build action picker!? I found nothing
the logs so far regarding 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

[JIRA] (JENKINS-14095) RedHat RPM has different checksum than repository metadata

2012-07-24 Thread vgir...@tacitknowledge.com (JIRA) 














































Vladimir Girnet
 commented on  JENKINS-14095


RedHat RPM has different checksum than repository metadata















I've just updated to 1.475-1.1 using default Jenkins repository (baseurl=http://pkg.jenkins-ci.org/redhat/) without any issues. 
You may try to do a "yum clean all" before checking for updates.

So, I think Jenkins repository is ok.



























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

[JIRA] (JENKINS-14544) Allow user to disable checkout by date if changelog not needed

2012-07-24 Thread ylemoi...@javatic.fr (JIRA) 














































Yann Le Moigne
 created  JENKINS-14544


Allow user to disable checkout by date if changelog not needed















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


cvs



Created:


24/Jul/12 7:00 AM



Description:


I would like to perform a maven release, without m2release plugin.
I browse the source code, and, at this time, it seem there is really no way to disable the sticky tag.

It seem a regression of JENKINS-229




Project:


Jenkins



Labels:


maven
release
sticky
cvs




Priority:


Major



Reporter:


Yann Le Moigne

























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

[JIRA] (JENKINS-14526) NPE in greenballs

2012-07-24 Thread rsi...@gracenote.com (JIRA) 














































robsimon
 commented on  JENKINS-14526


NPE in greenballs















Manifest says version 1.11

It occurred already a month ago but back then a restart of the Jenkins service solved the issue. This time neither the restart of the Jenkins service nor upgrading Jenkins to the latest version solved the issue. The NPE still occurred, no graphic UI was displayed and the header with the login was missing. The only possible way to login and to work with Jenkins was by removing the plugin.

I'll try now version 1.12



























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

[JIRA] (JENKINS-14526) NPE in greenballs

2012-07-24 Thread rsi...@gracenote.com (JIRA) 












































 
robsimon
 edited a comment on  JENKINS-14526


NPE in greenballs
















Manifest says version 1.11

The plugin was the jpi version.

It occurred already a month ago but back then a restart of the Jenkins service solved the issue. This time neither the restart of the Jenkins service nor upgrading Jenkins to the latest version solved the issue. The NPE still occurred, no graphic UI was displayed and the header with the login was missing. The only possible way to login and to work with Jenkins was by removing the plugin.

I'll try now version 1.12



























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

[JIRA] (JENKINS-14526) NPE in greenballs

2012-07-24 Thread rsi...@gracenote.com (JIRA) 












































 
robsimon
 edited a comment on  JENKINS-14526


NPE in greenballs
















Manifest says version 1.11

The plugin was the jpi version.

It occurred already a month ago but back then a restart of the Jenkins service solved the issue. This time neither the restart of the Jenkins service nor upgrading Jenkins to the latest version solved the issue. The NPE still occurred, no graphic UI was displayed and the header with the login was missing. The only possible way to login and to work with Jenkins was by renaming the plugin file to bak and removing the plugin directory. Other options weren't possible due to the missing login which is required to access the settings. Without the plugin being active no more NPE occur.

I'll try now version 1.12



























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

[JIRA] (JENKINS-14545) Unusable environment variable TRIGGERED_BUILD_NUMBER_jobname

2012-07-24 Thread j.vdk...@zarafa.com (JIRA) 














































John van der Kamp
 created  JENKINS-14545


Unusable environment variable TRIGGERED_BUILD_NUMBER_jobname















Issue Type:


Bug



Affects Versions:


current



Assignee:


huybrechts



Components:


parameterized-trigger



Created:


24/Jul/12 8:55 AM



Description:


The plugin exports two environment variables named TRIGGERED_BUILD_NUMBER_jobname=buildnumber. However, if your job has characters outside the alphanumeric range, the variable exported is unusable. Example: my job is named project-builder, then the exported variable will be TRIGGERED_BUILD_NUMBER_project-builder=123. Because of the - character, this variable is unusable. ${TRIGGERED_BUILD_NUMBER_project-builder} does not work.

The copy artifact plugin does a sanitation of the project name in the same export like this for it's COPYARTIFACT_BUILD_NUMBER_jobname environment var:

projectName.toUpperCase().replaceAll("[^A-Z]+", "_")


I think the the regex can be extended with 0-9 as valid characters too actually, but this would be the fix for this problem too.




Project:


Jenkins



Priority:


Major



Reporter:


John van der Kamp

























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

[JIRA] (JENKINS-12804) Promote When the following upstream promotions are promoted does not happen

2012-07-24 Thread knackwurst2...@yahoo.de (JIRA) 














































David B
 commented on  JENKINS-12804


Promote When the following upstream promotions are promoted  does not happen















I have the same problem, is there a quick fix? I tried it with the normal trigger plugin (but I have the parameterized installed), a stable / unstable job as parent and a stable / unstable job as child. In the Child it always says:
This promotion has not happened.
Met Qualification
Unmet Qualification
 Upstream promotions
  groovyunst

Jenkins ver. 1.475
Promoted-builds-plugin 2.5



























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

[JIRA] (JENKINS-12804) Promote When the following upstream promotions are promoted does not happen

2012-07-24 Thread knackwurst2...@yahoo.de (JIRA) 












































 
David B
 edited a comment on  JENKINS-12804


Promote When the following upstream promotions are promoted  does not happen
















I have the same problem, is there a quick fix? I tried it with the normal trigger plugin (but I have the parameterized installed), a stable / unstable job as parent and a stable / unstable job as child. In the child it always says:

This promotion has not happened.
Met Qualification
Unmet Qualification
 Upstream promotions
  groovyunst


Jenkins ver. 1.475
Promoted-builds-plugin 2.5



























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

[JIRA] (JENKINS-14546) Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated

2012-07-24 Thread a-he...@smacl.fr (JIRA) 














































Anthony HERBÉ
 created  JENKINS-14546


Regular users (others than admin) cant see any nested-views (other than the default one) with role-based authorization strategy activated















Issue Type:


Bug



Affects Versions:


current



Assignee:


Alan Harder



Components:


nested-view, role-strategy



Created:


24/Jul/12 9:32 AM



Description:


When Role-based Authorization Strategy is applied to Jobs, users others than admin can see their jobs but can't see any Nested-Views (or sub-Nested-views) other than the default one. Only admin user can see all nested views.




Due Date:


24/Jul/12 12:00 AM




Environment:


- CentOS release 6.2 (Final) x86_64

- JDK 1.6.0_30

- Jenkins v1.464 (From Yum)

- Nested View Plugin v1.8

- Role-based Authorization Strategy Plugin v1.1.2




Fix Versions:


current



Project:


Jenkins



Labels:


user
plugin
jenkins
gui
matrix




Priority:


Major



Reporter:


Anthony HERBÉ

























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

[JIRA] (JENKINS-13693) Add DefaultExcludes boolean option to transfer set

2012-07-24 Thread scm_issue_l...@java.net (JIRA) 















































SCM/JIRA link daemon
 resolved  JENKINS-13693 as Fixed


Add DefaultExcludes boolean option to transfer set
















Change By:


SCM/JIRA link daemon
(24/Jul/12 9:36 AM)




Status:


Open
Resolved





Resolution:


Fixed



























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

[JIRA] (JENKINS-13693) Add DefaultExcludes boolean option to transfer set

2012-07-24 Thread scm_issue_l...@java.net (JIRA) 














































SCM/JIRA link daemon
 commented on  JENKINS-13693


Add DefaultExcludes boolean option to transfer set















Code changed in jenkins
User: bap2000
Path:
 pom.xml
 src/main/java/jenkins/plugins/publish_over_cifs/CifsTransfer.java
 src/main/java/jenkins/plugins/publish_over_cifs/descriptor/CifsPublisherPluginDescriptor.java
 src/main/java/jenkins/plugins/publish_over_cifs/options/CifsOverrideTransferDefaults.java
 src/main/resources/jenkins/plugins/publish_over_cifs/CifsPublisherPlugin/config.jelly
 src/main/resources/jenkins/plugins/publish_over_cifs/CifsPublisherPlugin/global.jelly
 src/main/resources/jenkins/plugins/publish_over_cifs/CifsPublisherPlugin/help-noDefaultExcludes.jelly
 src/main/resources/jenkins/plugins/publish_over_cifs/options/CifsOverrideTransferDefaults/config.jelly
 src/test/java/jenkins/plugins/publish_over_cifs/CifsClientTest.java
http://jenkins-ci.org/commit/publish-over-cifs-plugin/b07933909341ba95cbf5ca31c8b6b195c9383766
Log:
  FIXED JENKINS-13693 Add option to disable default excludes


Compare: https://github.com/jenkinsci/publish-over-cifs-plugin/compare/e92204b755ab...b07933909341




























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

[JIRA] (JENKINS-13693) Add DefaultExcludes boolean option to transfer set

2012-07-24 Thread scm_issue_l...@java.net (JIRA) 














































SCM/JIRA link daemon
 commented on  JENKINS-13693


Add DefaultExcludes boolean option to transfer set















Code changed in jenkins
User: bap2000
Path:
 src/main/java/jenkins/plugins/publish_over/BPTransfer.java
 src/main/java/jenkins/plugins/publish_over/options/GlobalDefaults.java
 src/main/java/jenkins/plugins/publish_over/options/TransferOptions.java
 src/main/resources/jenkins/plugins/publish_over/Messages.properties
 src/main/resources/jenkins/plugins/publish_over/Messages_no_BV.properties
 src/main/resources/jenkins/plugins/publish_over/view_defaults/BPTransfer/Messages.properties
 src/main/resources/jenkins/plugins/publish_over/view_defaults/BPTransfer/Messages_no_BV.properties
 src/test/java/jenkins/plugins/publish_over/BPTransferTest.java
http://jenkins-ci.org/commit/publish-over-plugin/9b8cd2d4e35188d5bd0e76f7928d0c563a96de8c
Log:
  FIXED JENKINS-13693 Add option to disable default excludes































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

[JIRA] (JENKINS-13693) Add DefaultExcludes boolean option to transfer set

2012-07-24 Thread scm_issue_l...@java.net (JIRA) 














































SCM/JIRA link daemon
 commented on  JENKINS-13693


Add DefaultExcludes boolean option to transfer set















Code changed in jenkins
User: bap2000
Path:
 pom.xml
 src/main/java/jenkins/plugins/publish_over_ftp/BapFtpTransfer.java
 src/main/java/jenkins/plugins/publish_over_ftp/descriptor/BapFtpTransferDescriptor.java
 src/main/java/jenkins/plugins/publish_over_ftp/options/FtpOverrideTransferDefaults.java
 src/main/resources/jenkins/plugins/publish_over_ftp/BapFtpTransfer/config.jelly
 src/main/resources/jenkins/plugins/publish_over_ftp/BapFtpTransfer/help-noDefaultExcludes.jelly
 src/main/resources/jenkins/plugins/publish_over_ftp/options/FtpOverrideTransferDefaults/config.jelly
 src/test/java/jenkins/plugins/publish_over_ftp/jenkins/CurrentConfigurationTest.java
 src/test/java/jenkins/plugins/publish_over_ftp/jenkins/IntegrationTest.java
 src/test/java/jenkins/plugins/publish_over_ftp/jenkins/LegacyConfigurationTest.java
http://jenkins-ci.org/commit/publish-over-ftp-plugin/75797f30281d4b502498f11a1f5c4577efee87a3
Log:
  FIXED JENKINS-13693 Add option to disable default excludes


Compare: https://github.com/jenkinsci/publish-over-ftp-plugin/compare/2bba237f3dea...75797f30281d




























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

[JIRA] (JENKINS-13693) Add DefaultExcludes boolean option to transfer set

2012-07-24 Thread scm_issue_l...@java.net (JIRA) 














































SCM/JIRA link daemon
 commented on  JENKINS-13693


Add DefaultExcludes boolean option to transfer set















Code changed in jenkins
User: bap2000
Path:
 pom.xml
 src/main/java/jenkins/plugins/publish_over_ssh/BapSshTransfer.java
 src/main/java/jenkins/plugins/publish_over_ssh/descriptor/BapSshTransferDescriptor.java
 src/main/java/jenkins/plugins/publish_over_ssh/options/SshOverrideTransferDefaults.java
 src/main/resources/jenkins/plugins/publish_over_ssh/BapSshTransfer/config.jelly
 src/main/resources/jenkins/plugins/publish_over_ssh/BapSshTransfer/help-noDefaultExcludes.jelly
 src/main/resources/jenkins/plugins/publish_over_ssh/options/SshOverrideTransferDefaults/config.jelly
 src/test/java/jenkins/plugins/publish_over_ssh/BapSshClientTest.java
 src/test/java/jenkins/plugins/publish_over_ssh/BapSshHostConfigurationTest.java
 src/test/java/jenkins/plugins/publish_over_ssh/jenkins/IntegrationTest.java
 src/test/java/jenkins/plugins/publish_over_ssh/jenkins/LegacyConfigurationTest.java
http://jenkins-ci.org/commit/publish-over-ssh-plugin/4595e8598952a17a471da44bbc225b02d3ba1bdb
Log:
  FIXED JENKINS-13693 Add option to disable default excludes


Compare: https://github.com/jenkinsci/publish-over-ssh-plugin/compare/241b2ca2c646...4595e8598952




























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

[JIRA] (JENKINS-14546) Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated

2012-07-24 Thread a-he...@smacl.fr (JIRA) 














































Anthony HERBÉ
 commented on  JENKINS-14546


Regular users (others than admin) cant see any nested-views (other than the default one) with role-based authorization strategy activated















I think upgrade Jenkins to version 1.467 or greater, will resolve this problem (like it will be mentionned into JENKINS-13429, can you confirm this ?



























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

[JIRA] (JENKINS-14509) PMD Plugin reporting existing warnings as new

2012-07-24 Thread scm_issue_l...@java.net (JIRA) 














































SCM/JIRA link daemon
 commented on  JENKINS-14509


PMD Plugin reporting existing warnings as new















Code changed in jenkins
User: Ulli Hafner
Path:
 src/main/java/hudson/plugins/pmd/parser/PmdParser.java
http://jenkins-ci.org/commit/pmd-plugin/bc7267d5b8eae0e8d741dcbbea5571afd8e8d174
Log:
  JENKINS-14509 Added debugging of exception to module name of bug.































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

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

2012-07-24 Thread mynewspamacco...@gmx.com (JIRA) 














































Hazel Nutt
 commented on  JENKINS-10628


SCM build trigger not working correctly with variables in SVN URL















I also applied Belas patch and with Spikes URL was able to build my own custom subversion-plugin which is able to expand the globally defined $variables correctly.

Propably the entries JENKINS-12287 and JENKINS-12450 are also revolving around this issue?

Two more things i would like to mention concerning this patch/fix in the svn-plugin: 


	Currently my SVN-polling disables the Job where svn-url contains a $variable (propably because it thinks the svn-url containing the $var is invalid)




	The GUI displays the svn-url containing the $var as invalid and wants to be helpful and tries to hint me to the regular /trunk svn-url





























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

[JIRA] (JENKINS-14547) Null pointer exception when using groovy script

2012-07-24 Thread tabasco...@gmail.com (JIRA) 














































Fabian Koch
 created  JENKINS-14547


Null pointer exception when using groovy script















Issue Type:


Bug



Affects Versions:


current



Assignee:


Gregory Boissinot



Components:


artifactdeployer



Created:


24/Jul/12 10:25 AM



Description:


When I try to use the deleteRemoteArtifactsByScript feature, I get a NULL pointer exception when trying to apply my changes to the config.

The JSON parser exits with NULL.

Looking at the source on GitHub I think this is because in 
https://github.com/jenkinsci/artifactdeployer-plugin/blob/master/src/main/java/org/jenkinsci/plugins/artifactdeployer/ArtifactDeployerPublisher.java#L282

you are using a Name that does not exist. I guess it should be "deleteRemoteArtifactsByScript", right?




Project:


Jenkins



Priority:


Major



Reporter:


Fabian Koch

























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

[JIRA] (JENKINS-14503) Error when using GRADLE wrapper

2012-07-24 Thread vasilena.tren...@softwareag.com (JIRA) 














































Vassilena Treneva
 updated  JENKINS-14503


Error when using GRADLE wrapper
















Change By:


Vassilena Treneva
(24/Jul/12 10:30 AM)




Attachment:


wrapper.jpg



























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

[JIRA] (JENKINS-14503) Error when using GRADLE wrapper

2012-07-24 Thread vasilena.tren...@softwareag.com (JIRA) 














































Vassilena Treneva
 commented on  JENKINS-14503


Error when using GRADLE wrapper















Seems that it works only when invoking gradle in the root dir where gradle wrapper lives.
When I tried to invoke it for a set of tests deeper in the directories I got:

Gradle - Launching build.
Gradle - ERROR Can't retrieve the Gradle executable.
Build step 'Invoke Gradle script' marked build as failure
Recording test results

What is the configuration passing for execution? I assume that instead gradle build it should be gradlew build. But the commands gradle or gradlew are passed from Jenkins, so I wonder what is passed in case of the wrapper?

Hope you can help me 



























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

[JIRA] (JENKINS-14544) Allow user to disable checkout by date if changelog not needed

2012-07-24 Thread michael.m.cla...@gmail.com (JIRA) 















































Michael Clarke
 resolved  JENKINS-14544 as Fixed


Allow user to disable checkout by date if changelog not needed
















This was fixed by JENKINS-13789 and will be in the next release.





Change By:


Michael Clarke
(24/Jul/12 10:43 AM)




Status:


InProgress
Resolved





Resolution:


Fixed



























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

[JIRA] (JENKINS-14549) Failure during test aggregation of multi-configuration build

2012-07-24 Thread ikat...@griddynamics.com (JIRA) 














































Ilya Katsov
 created  JENKINS-14549


Failure during test aggregation of multi-configuration build















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


matrix



Created:


24/Jul/12 11:02 AM



Description:


Preconditions:

	Create multi-configuration (matrix) build
	Configure User-defined label SLICEID with 3 values: 1 2 3
	Configure Aggregate downstream test results, provide jobs names explicitly like "MY_JOB/SLICEID=1", "MY_JOB/SLICEID=2", "MY_JOB/SLICEID=3"
	Configure Publish JUnit test result report as */surefire-reports/.xml
	Run build that produces junit resports (for example, using maven and surefire)



Result:
Aggregation fails with the following exception in the Jenkins log:

Jul 24, 2012 2:42:44 PM hudson.ExpressionFactory2$JexlExpression evaluate
WARNING: Caught exception evaluating: p.previousResult. Reason: java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor323.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)
at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)
at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)
at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)
at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:72)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81)
at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98)
at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
at

[JIRA] (JENKINS-14550) Checksum mismatch while updating with Subversion Plugin 1.42

2012-07-24 Thread ch...@simplistix.co.uk (JIRA) 














































Chris Withers
 created  JENKINS-14550


Checksum mismatch while updating with Subversion Plugin 1.42















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


subversion



Created:


24/Jul/12 11:04 AM



Description:


After upgrading to 1.42 of the plugin, using the "Emulate clean checkout by first deleting unversioned/ignored files, then 'svn update'" svn strategy intermittently results in errors that look like the following:

ERROR: Failed to update svn://path
org.tmatesoft.svn.core.SVNException: svn: E155017: Checksum mismatch while updating '/opt/jenkins/jobs/job/workspace/path to folder/.svn/text-base/filename.svn-base'; expected: '151afc3b6d79443cc57fd52080d5f4d7', actual: '97acf6bf0db0d86168866633488b1a93'
	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:85)
	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:69)
	at org.tmatesoft.svn.core.internal.io.svn.SVNEditModeReader.driveEditor(SVNEditModeReader.java:250)
	at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.update(SVNRepositoryImpl.java:1503)
	at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.update(SVNUpdateClient16.java:557)
	at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:414)
	at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:324)
	at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:27)
	at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:11)
	at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20)
	at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1221)
	at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:292)
	at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:315)
	at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:295)
	at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:391)
	at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:136)
	at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:144)
	at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:789)
	at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:770)
	at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:753)
	at hudson.FilePath.act(FilePath.java:842)
	at hudson.FilePath.act(FilePath.java:824)
	at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:743)
	at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:685)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1242)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494)
	at hudson.model.Run.execute(Run.java:1460)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:239)

I clicked the "Downgrade to 1.39" button in the installed plugins section, restarted Jenkins and the problem appears to be solved.

However, I notice the installed plugins section now says I have 1.34 installed, which is a little confusing.




Environment:


sles 11, Jenkins 1.470, subversion server is CollabNet Subversion Edge 1.3.1




Project:


Jenkins



Priority:


Major



Reporter:


Chris Withers

[JIRA] (JENKINS-14550) Checksum mismatch while updating with Subversion Plugin 1.42

2012-07-24 Thread ch...@simplistix.co.uk (JIRA) 












































 
Chris Withers
 updated  JENKINS-14550


Checksum mismatch while updating with Subversion Plugin 1.42
















Forgot to say, to make matters worse, when the checksum problem occurs, the Subversion Plugin doesn't fail the build, causing spurious failures in build steps later in the job.



























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

[JIRA] (JENKINS-14551) an update which contains added files merged from a branch results in those files having doubled content

2012-07-24 Thread ch...@simplistix.co.uk (JIRA) 














































Chris Withers
 created  JENKINS-14551


an update which contains added files merged from a branch results in those files having doubled content















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


subversion



Created:


24/Jul/12 12:08 PM



Description:


Using the "Emulate clean checkout by first deleting unversioned/ignored files, then 'svn update'" svn strategy, we recently had a branch merged into 
trunk that added some files. When the Jenkins jobs configured as above 
ran against trunk, those added files had their content duplicated. 

A quick google suggested it has happened before: 

http://grokbase.com/p/lucene/dev/126m8fpw9q/jenkins-lucene-solr-tests-only-4-x-build-137-still-failing 




Environment:


sles 11, Jenkins 1.470, subversion server is CollabNet Subversion Edge 1.3.1




Project:


Jenkins



Priority:


Major



Reporter:


Chris Withers

























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

[JIRA] (JENKINS-14552) Cannot plublish cobertura reports if org.codehaus.mojo:cobertura-maven-plugin is not invoked

2012-07-24 Thread drautur...@java.net (JIRA) 














































drautureau
 created  JENKINS-14552


Cannot plublish cobertura reports if org.codehaus.mojo:cobertura-maven-plugin is not invoked















Issue Type:


Bug



Affects Versions:


current



Assignee:


stephenconnolly



Components:


cobertura



Created:


24/Jul/12 12:41 PM



Description:


I'm building a project using grails and grails-maven-plugin.
Since version 1.4 of the plugin, the cobertura report is not published because the cobertura-maven-plugin is not invoked:

...
Cobertura: Loaded information on 293 classes.
Cobertura: Saved information on 293 classes.
Skipping Cobertura coverage report as mojo did not run.
...

Looking at the sources of the plugin, it's mandatory to execute the cobertura-maven-plugin to publish reports (and that's not the way grails work!).

I can't see why this test is done (as we need to provide the path of the report). Wouls it be possible to remove/adapt this check?

As a workaround: I'm using version 1.3 of the plugin.

thanks




Environment:


Jenkins cobertura plugin 1.4, 1.5

grails and grails maven plugin




Project:


Jenkins



Priority:


Major



Reporter:


drautureau

























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

[JIRA] (JENKINS-14552) Cannot plublish cobertura reports if org.codehaus.mojo:cobertura-maven-plugin is not invoked

2012-07-24 Thread drautur...@java.net (JIRA) 














































drautureau
 updated  JENKINS-14552


Cannot plublish cobertura reports if org.codehaus.mojo:cobertura-maven-plugin is not invoked
















Change By:


drautureau
(24/Jul/12 12:42 PM)




Description:


Imbuildingaprojectusinggrailsandgrails-maven-plugin.Sinceversion1.4oftheplugin,thecoberturareportisnotpublishedbecausethecobertura-maven-pluginisnotinvoked:{code}...Cobertura:Loadedinformationon293classes.Cobertura:Savedinformationon293classes.SkippingCoberturacoveragereportasmojodidnotrun{code}Lookingatthesourcesoftheplugin,itsmandatorytoexecutethecobertura-maven-plugintopublishreports(andthatsnotthewaygrailswork!).Icantseewhythistestisdone(asweneedtoprovidethepathofthereport).
Wouls
Would
itbepossibletoremove/adaptthischeck?Asaworkaround:Imusingversion1.3oftheplugin.thanks



























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

[JIRA] (JENKINS-14553) JIRA: no 'summary_report-plugin' component

2012-07-24 Thread deruy...@java.net (JIRA) 














































deruyter
 created  JENKINS-14553


JIRA: no summary_report-plugin component















Issue Type:


Task



Affects Versions:


current



Assignee:


Unassigned


Components:


jira



Created:


24/Jul/12 12:44 PM



Description:


The summary_report-plugin has no entry in JIRA.
Description is available here: https://wiki.jenkins-ci.org/display/JENKINS/Summary+Display+Plugin




Project:


Jenkins



Labels:


plugin




Priority:


Major



Reporter:


deruyter

























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

[JIRA] (JENKINS-14531) CAS1 and 'Trigger builds remotely' incompatibility

2012-07-24 Thread joao.antu...@tagus.ist.utl.pt (JIRA) 














































João Antunes
 commented on  JENKINS-14531


CAS1 and Trigger builds remotely incompatibility















Submitted a pull request with the code to fix this



























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

[JIRA] (JENKINS-14394) The version 1.1.21 breaks

2012-07-24 Thread bjac...@woti.com (JIRA) 














































Bryan Jacobs
 commented on  JENKINS-14394


The version 1.1.21 breaks















That patch looks good, but upon applying it, I got the dreaded "ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job." message.

My repository looks like this:

  remotes/target/HEAD - target/master
  remotes/target/changes/23/23/1
  remotes/target/master
  remotes/upstream/heads/master

The branch "target/changes/23/23/1" is supposed to be merged with "upstream/heads/master" before building. The repository got this way by specifying the same remote repo twice with two different refspecs.

I tried setting the "target branch" to "remotes/target/changes/23/23/1", "changes/23/23/1", and "refs/remotes/target/changes/23/23/1", and "target/changes/23/23/1". None 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

[JIRA] (JENKINS-14538) Separate configure tools page

2012-07-24 Thread jgl...@cloudbees.com (JIRA) 














































jglick
 commented on  JENKINS-14538


Separate configure tools page















I committed a different UI to the branch, a much less disruptive change from the current UI: all tools still shown in /configure, but collapsed by default, with Advanced-style buttons labeled e.g. "Ant installations...". Working except for button alignment which is gratuitously indented.



























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

[JIRA] (JENKINS-14507) NPE from JUnitParser.parse

2012-07-24 Thread dogf...@java.net (JIRA) 














































dogfood
 commented on  JENKINS-14507


NPE from JUnitParser.parse















Integrated in  jenkins_main_trunk #1812
 FIXED JENKINS-14507 NPE from JUnitParser.parse. (Revision 931fa176e811878e0bd06e6007036f5e8651c917)

 Result = UNSTABLE
Jesse Glick : 931fa176e811878e0bd06e6007036f5e8651c917
Files : 

	changelog.html
	core/src/main/resources/hudson/tasks/junit/Messages.properties
	core/src/main/java/hudson/model/AbstractBuild.java
	core/src/main/java/hudson/tasks/junit/JUnitParser.java





























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

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

2012-07-24 Thread dogf...@java.net (JIRA) 














































dogfood
 commented on  JENKINS-13972


Concurrent matrix builds abort















Integrated in  jenkins_main_trunk #1812
 FIXED JENKINS-13972 (Revision 9c7ef619cc96dc0111220412e841199de71d5b8d)

 Result = UNSTABLE
Kohsuke Kawaguchi : 9c7ef619cc96dc0111220412e841199de71d5b8d
Files : 

	changelog.html
	core/src/main/java/hudson/matrix/MatrixConfiguration.java
	core/src/main/java/hudson/matrix/MatrixBuild.java





























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

[JIRA] (JENKINS-14532) Create Job Advanced Plugin - an incorrect group name set when using dynamic permissions.

2012-07-24 Thread tzieleniew...@gmail.com (JIRA) 















































Tomasz Zieleniewski
 resolved  JENKINS-14532 as Fixed


Create Job Advanced Plugin - an incorrect group name set when using dynamic permissions.
















There is no error in the code but in the help message.
According to the spec group zero always stands for the entire _expression_.
http://docs.oracle.com/javase/1.6/docs/api/java/util/regex/Pattern.html#cg





Change By:


Tomasz Zieleniewski
(24/Jul/12 2:06 PM)




Status:


InProgress
Resolved





Fix Version/s:


current





Resolution:


Fixed



























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

[JIRA] (JENKINS-14554) With german locale buttons Advanced and Test are not visible in security management

2012-07-24 Thread fischer.n...@googlemail.com (JIRA) 














































Nick Fischer
 created  JENKINS-14554


With german locale buttons Advanced and Test are not visible in security management















Issue Type:


Bug



Assignee:


Nick Fischer



Attachments:


Advanced_Test.png



Components:


active-directory



Created:


24/Jul/12 2:07 PM



Description:


With installed Active Directory Plugin
Under "Manage Jenkins"  "Configure System"  "Enable security"  "Active Directory" buttons "Advanced" and "Test" are not visible with locale set to german.
Workaround to make buttons reappear:

(If not already done) Install Locale Plugin and swith interface language to english
1. Disable security
2. Restart TomCat
3. Enable security




Environment:


Windows 7 Professional x64, Apache Tomcat/6.0.35, JVM 1.6.0_26-b03




Project:


Jenkins



Labels:


jenkins,
windows
plugins




Priority:


Minor



Reporter:


Nick Fischer

























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

[JIRA] (JENKINS-14554) With german locale buttons Advanced and Test are not visible in security management

2012-07-24 Thread fischer.n...@googlemail.com (JIRA) 














































Nick Fischer
 updated  JENKINS-14554


With german locale buttons Advanced and Test are not visible in security management
















Change By:


Nick Fischer
(24/Jul/12 2:12 PM)




Environment:


Jenkins1.465
Windows7Professionalx64,ApacheTomcat/6.0.35,JVM1.6.0_26-b03



























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

[JIRA] (JENKINS-14509) PMD Plugin reporting existing warnings as new

2012-07-24 Thread scm_issue_l...@java.net (JIRA) 














































SCM/JIRA link daemon
 commented on  JENKINS-14509


PMD Plugin reporting existing warnings as new















Code changed in jenkins
User: Ulli Hafner
Path:
 src/main/java/hudson/plugins/pmd/parser/PmdParser.java
http://jenkins-ci.org/commit/pmd-plugin/c2d0b6ddb814a9de28f1e6f02c26c055ccd78703
Log:
  Revert "JENKINS-14509 Added debugging of exception to module name of bug."

This reverts commit bc7267d5b8eae0e8d741dcbbea5571afd8e8d174.































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

[JIRA] (JENKINS-14538) Separate configure tools page

2012-07-24 Thread jgl...@cloudbees.com (JIRA) 














































jglick
 started work on  JENKINS-14538


Separate configure tools page
















Change By:


jglick
(24/Jul/12 3:14 PM)




Status:


Open
InProgress



























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

[JIRA] (JENKINS-14078) Fetch stopped working

2012-07-24 Thread slaven...@internap.com (JIRA) 














































Scott Lavender
 commented on  JENKINS-14078


Fetch stopped working















How/were can I find previous releases of this plugin? I need to get back to 1.1.18 until 1.1.22 is released to avoid this issue.



























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

[JIRA] (JENKINS-14521) Configuration Slicing should temporarily disable the Auto Refresh plugin

2012-07-24 Thread kacynski.w...@aoins.com (JIRA) 














































Walter Kacynski
 commented on  JENKINS-14521


Configuration Slicing should temporarily disable the Auto Refresh plugin















Yes, that is correct, isn't that something that is controlled by 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

[JIRA] (JENKINS-14530) Allow to upgrade/downgrade to any plugin version

2012-07-24 Thread kacynski.w...@aoins.com (JIRA) 














































Walter Kacynski
 commented on  JENKINS-14530


Allow to upgrade/downgrade to any plugin version















This would also help us when migrating our environments in Jenkins.



























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

[JIRA] (JENKINS-14538) Separate configure tools page

2012-07-24 Thread scm_issue_l...@java.net (JIRA) 














































SCM/JIRA link daemon
 commented on  JENKINS-14538


Separate configure tools page















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
http://jenkins-ci.org/commit/jenkins/03546bd62c2abf14130efdc2739a17a3da978974
Log:
  FIXED JENKINS-14538 Collapse nonempty tool installation sections by default in /configure.































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

[JIRA] (JENKINS-14538) Separate configure tools page

2012-07-24 Thread scm_issue_l...@java.net (JIRA) 















































SCM/JIRA link daemon
 resolved  JENKINS-14538 as Fixed


Separate configure tools page
















Change By:


SCM/JIRA link daemon
(24/Jul/12 3:29 PM)




Status:


InProgress
Resolved





Resolution:


Fixed



























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

[JIRA] (JENKINS-14555) Error 500 org.apache.commons.jelly.JellyTagException

2012-07-24 Thread garlan...@gmail.com (JIRA) 














































Ken Garland
 created  JENKINS-14555


Error 500 org.apache.commons.jelly.JellyTagException















Issue Type:


Bug



Assignee:


ragesh_nair



Components:


rebuild



Created:


24/Jul/12 3:33 PM



Description:


Status Code: 500

Exception: org.apache.commons.jelly.JellyTagException: file:/root/.jenkins/plugins/rebuild/WEB-INF/classes/com/sonyericsson/rebuild/RebuildAction/index.jelly:54:63: st:include No page found 'ExtendedChoiceParameterValue.jelly' for class com.sonyericsson.rebuild.RebuildAction
Stacktrace:
javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: file:/root/.jenkins/plugins/rebuild/WEB-INF/classes/com/sonyericsson/rebuild/RebuildAction/index.jelly:54:63: st:include No page found 'ExtendedChoiceParameterValue.jelly' for class com.sonyericsson.rebuild.RebuildAction
	at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112)
	at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
	at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
	at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:162)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
	at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
	at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
	at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
	at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
	at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
	at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
	at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
	at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
	at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
	at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
	at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
	at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50)
	at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
	at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
	at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
	at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
	at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
	at winstone.RequestDispatcher.forward(RequestDispatcher.java:331)
	at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:215)
	at winstone.RequestHandlerThread.run(RequestHandlerThread.java:138)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at

[JIRA] (JENKINS-14538) Separate configure tools page

2012-07-24 Thread jgl...@cloudbees.com (JIRA) 














































jglick
 updated  JENKINS-14538


Separate configure tools page
















Change By:


jglick
(24/Jul/12 3:37 PM)




Description:


CurrentlyifyouwanttomanagetoolinstallationsinaJenkinsinstance,youjustgotothemaster{{/configure}}page.Unfortunatelythiscangetoutofhand:whentherearealotoftoolsalready(suchastwentydot-dotJDKreleases),regularJenkinsconfigurationcangetlostinthemess.The{{configureTools}}branch(seeURL)proposestosplittoolinstallationsoffintotheirownconfigurationpageforcomfort.Openissues:#Alltoolsareshownonasinglepage,thoughitmayalsobefeasibletoproduceonepagepertooltype(Ant,Maven,JDK,...);oronepagewithtabs,iftherewereaclearmeaningforSaveandApplyinthatcase.#Themanagementlinkusesthesame{{setting.png}}asthemain{{/configure}}page;probablyneedsitsownicon.#TBDwhetherotherbitsofconfigurationbelonginthenewlocation,notably{{ToolLocationNodeProperty}}and{{Shell.DescriptorImpl}}-shouldtherebeawayofindicatingthatagiven{{Descriptor}}wouldliketobe
renderer
rendered
onanalternateconfigpage?





URL:


https://github.com/jenkinsci/jenkins/
compare
commit
/
master...configureTools
468c5210355d41020ba168cfe45e2b4ef128ccc1



























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

[JIRA] (JENKINS-11606) configuration option for disabling the commands

2012-07-24 Thread cfo...@java.net (JIRA) 














































cforce
 commented on  JENKINS-11606


configuration option for disabling the commands















How does this work?
I found option to set globally "Initial group chats" with switch "Notification only".
I i give users to configure their jobs themself, they can enter any room to be notified in job. How can i restrict !bot control for all rooms /users except for some i only can configure beeing jenkins admin (in global config)?



























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

[JIRA] (JENKINS-11606) configuration option for disabling the commands

2012-07-24 Thread cfo...@java.net (JIRA) 












































 
cforce
 edited a comment on  JENKINS-11606


configuration option for disabling the commands
















How does this work?
I found option to set globally "Initial group chats" with switch "Notification only".
If i give users the right to configure/admin their jobs themself, then they also can enter any jabber room/user to be notified in job config. How can i then restrict to notication ony (no !bot control) for all rooms/users but for some be able to allow !bot control as Jenkins admin (in global config)?

Please explain, can't find any helo for this new feature.



























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

[JIRA] (JENKINS-14556) Timeline is wrong when tests are executed in parallel

2012-07-24 Thread martin.danjo...@gmail.com (JIRA) 














































Martin dAnjou
 created  JENKINS-14556


Timeline is wrong when tests are executed in parallel















Issue Type:


Bug



Assignee:


Unassigned


Attachments:


jenkins_timeline_bug.png



Components:


gui



Created:


24/Jul/12 3:59 PM



Description:


We use a grid engine software behind the scenes to dispatch tests to dozens of hosts and CPUs. This means that to total linear time of a build can be 3 days, but because it is done in parallel, the wall time is actually much smaller, e.g. 16 hours.

Jenkins cannot know that we are doing this, but nevertheless, the timeline has all the information to report it correctly, but it does not.

In the attached picture, we can clearly see that the duration was approximately 16 hours in the text, but Jenkins extends the red "line" to over 3 days.




Project:


Jenkins



Priority:


Major



Reporter:


Martin dAnjou

























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

[JIRA] (JENKINS-985) Cannot create process on windows

2012-07-24 Thread ever...@free.fr (JIRA) 















































evernat
 resolved  JENKINS-985 as Fixed


Cannot create process on windows
















No response from basiep, so closing this issue again as fixed.





Change By:


evernat
(24/Jul/12 4:06 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

[JIRA] (JENKINS-14497) Can't start emulator with new Android SDK Tools rev. 20.0.1

2012-07-24 Thread scm_issue_l...@java.net (JIRA) 















































SCM/JIRA link daemon
 resolved  JENKINS-14497 as Fixed


Cant start emulator with new Android SDK Tools rev. 20.0.1
















Change By:


SCM/JIRA link daemon
(24/Jul/12 4:27 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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

[JIRA] (JENKINS-14497) Can't start emulator with new Android SDK Tools rev. 20.0.1

2012-07-24 Thread scm_issue_l...@java.net (JIRA) 














































SCM/JIRA link daemon
 commented on  JENKINS-14497


Cant start emulator with new Android SDK Tools rev. 20.0.1















Code changed in jenkins
User: Christopher Orr
Path:
 src/main/java/hudson/plugins/android_emulator/util/Utils.java
 src/test/java/hudson/plugins/android_emulator/util/UtilsTest.java
http://jenkins-ci.org/commit/android-emulator-plugin/770bf157ef44b38b426781e568296a172b790341
Log:
  Merge pull request #14 from jberkel/master

FIXED JENKINS-14497 Fix parsing of recent SDK revision strings.


Compare: https://github.com/jenkinsci/android-emulator-plugin/compare/7a3d75b5d45f...770bf157ef44




























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

[JIRA] (JENKINS-14538) Separate configure tools page

2012-07-24 Thread dogf...@java.net (JIRA) 














































dogfood
 commented on  JENKINS-14538


Separate configure tools page















Integrated in  jenkins_main_trunk #1813
 FIXED JENKINS-14538 Collapse nonempty tool installation sections by default in /configure. (Revision 03546bd62c2abf14130efdc2739a17a3da978974)

 Result = UNSTABLE
Jesse Glick : 03546bd62c2abf14130efdc2739a17a3da978974
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

[JIRA] (JENKINS-11973) AVD should be in workspace instead of system-global

2012-07-24 Thread scm_issue_l...@java.net (JIRA) 














































SCM/JIRA link daemon
 commented on  JENKINS-11973


AVD should be in workspace instead of system-global















Code changed in jenkins
User: Jørgen P. Tjernø
Path:
 .gitignore
 src/main/java/hudson/plugins/android_emulator/AndroidEmulator.java
 src/main/java/hudson/plugins/android_emulator/AndroidEmulatorContext.java
 src/main/java/hudson/plugins/android_emulator/EmulatorConfig.java
 src/main/java/hudson/plugins/android_emulator/SdkInstaller.java
 src/main/java/hudson/plugins/android_emulator/TaskDispatcher.java
 src/main/java/hudson/plugins/android_emulator/builder/AbstractBuilder.java
 src/main/java/hudson/plugins/android_emulator/sdk/AndroidSdk.java
 src/main/java/hudson/plugins/android_emulator/util/Utils.java
 src/main/resources/hudson/plugins/android_emulator/AndroidEmulator/config.jelly
 src/main/resources/hudson/plugins/android_emulator/AndroidEmulator/global.jelly
 src/main/webapp/help-keepInWorkspace.html
http://jenkins-ci.org/commit/android-emulator-plugin/430606da6fef941288b5f427a696a5b8dcdb7c13
Log:
  JENKINS-11973 Option for emulators in $WORKSPACE

This adds a global option that essentially does
ANDROID_SDK_HOME=$WORKSPACE, causing emulators to be put into
$WORKSPACE/.android.

This allows you to run concurrent jobs on the same slave, and to run the
same emulator config from two different jobs on the same slave. It also
makes the emulators more isolated and allows you to clean-slate the
emulators by wiping out the workspace.





























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

[JIRA] (JENKINS-11973) AVD should be in workspace instead of system-global

2012-07-24 Thread ch...@orr.me.uk (JIRA) 














































Christopher Orr
 commented on  JENKINS-11973


AVD should be in workspace instead of system-global















Arguably this is a pretty niche feature anyway (i.e. just for you ), so global config is fine 



























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

[JIRA] (JENKINS-11973) AVD should be in workspace instead of system-global

2012-07-24 Thread scm_issue_l...@java.net (JIRA) 














































SCM/JIRA link daemon
 commented on  JENKINS-11973


AVD should be in workspace instead of system-global















Code changed in jenkins
User: Christopher Orr
Path:
 .gitignore
 src/main/java/hudson/plugins/android_emulator/AndroidEmulator.java
 src/main/java/hudson/plugins/android_emulator/AndroidEmulatorContext.java
 src/main/java/hudson/plugins/android_emulator/EmulatorConfig.java
 src/main/java/hudson/plugins/android_emulator/SdkInstaller.java
 src/main/java/hudson/plugins/android_emulator/TaskDispatcher.java
 src/main/java/hudson/plugins/android_emulator/builder/AbstractBuilder.java
 src/main/java/hudson/plugins/android_emulator/sdk/AndroidSdk.java
 src/main/java/hudson/plugins/android_emulator/util/Utils.java
 src/main/resources/hudson/plugins/android_emulator/AndroidEmulator/config.jelly
 src/main/resources/hudson/plugins/android_emulator/AndroidEmulator/global.jelly
 src/main/webapp/help-keepInWorkspace.html
http://jenkins-ci.org/commit/android-emulator-plugin/acae1f59bd739151383b21ad1cf867507c206cef
Log:
  Merge pull request #13 from jorgenpt/workspace-local-android-images

FIXED JENKINS-11973 Allow emulators to be stored in $WORKSPACE.


Compare: https://github.com/jenkinsci/android-emulator-plugin/compare/770bf157ef44...acae1f59bd73




























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

[JIRA] (JENKINS-11973) AVD should be in workspace instead of system-global

2012-07-24 Thread scm_issue_l...@java.net (JIRA) 















































SCM/JIRA link daemon
 resolved  JENKINS-11973 as Fixed


AVD should be in workspace instead of system-global
















Change By:


SCM/JIRA link daemon
(24/Jul/12 4:32 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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

[JIRA] (JENKINS-14557) Don't show SDK stats dialog for emulators in $WORKSPACE

2012-07-24 Thread ch...@orr.me.uk (JIRA) 














































Christopher Orr
 created  JENKINS-14557


Dont show SDK stats dialog for emulators in $WORKSPACE















Issue Type:


Improvement



Assignee:


Christopher Orr



Components:


android-emulator



Created:


24/Jul/12 4:34 PM



Description:


For some reason, opting out of the SDK stats collection doesn't work correctly when emulators are stored in $WORKSPACE.

See this pull request:
https://github.com/jenkinsci/android-emulator-plugin/pull/13#issuecomment-7002467

This should be fixed.




Project:


Jenkins



Priority:


Minor



Reporter:


Christopher Orr

























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

[JIRA] (JENKINS-14493) Send geo fix command to Android Emulator

2012-07-24 Thread ch...@orr.me.uk (JIRA) 














































Christopher Orr
 commented on  JENKINS-14493


Send geo fix command to Android Emulator















If you want to implement this yourself, there's an existing implementation that's very similar:
https://github.com/jenkinsci/android-emulator-plugin/blob/master/src/main/java/hudson/plugins/android_emulator/snapshot/AbstractSnapshotBuilder.java

Otherwise, I could take a look at adding this myself within the next couple of weeks.



























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

[JIRA] (JENKINS-14559) Windows Service - slave.xml is always overritten causing connection issues

2012-07-24 Thread vladdruss...@gmail.com (JIRA) 














































VladDRussian
 created  JENKINS-14559


Windows Service - slave.xml is always overritten causing connection issues















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


24/Jul/12 5:24 PM



Description:


when starting a slave via jenkins it now installs the service everytime and removes it when disconnected.  The issue i am hitting is that the jenkins-slave.xml is ALWAYS getting copied to the slave now overriding out local config for JAVA as well as the connection port.

I tried changing the jenkins-slave.xml to read only but then trying to start the issue we only get a permission issue.




Environment:


Jenkins 1.467 running on win2k3 / winXP / win2k8 R1 / win2k8 R2, upgraded from Jenkins 1.417




Project:


Jenkins



Priority:


Major



Reporter:


VladDRussian

























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

[JIRA] (JENKINS-14095) RedHat RPM has different checksum than repository metadata

2012-07-24 Thread billy.p...@nike.com (JIRA) 














































billy paul
 commented on  JENKINS-14095


RedHat RPM has different checksum than repository metadata















Hey Vladmir.  The problem appears to be with one specific mirror...

http://ftp-chi.osuosl.org/pub/jenkins/redhat/jenkins-1.475-1.1.noarch.rpm

I'm using Artifactory as a yum proxy.  When I wget from my Artifactory server, it's redirected to the above URL.  wget sits at 99% for an extended period of time, then tries again.  The second request gets a 206 (Partial Content).  The download completes, but I think the fact that it's taking two requests does something to the bits that causes it to have a slightly different checksum.  Would you mind trying that specific mirror and see if you have any issues with the checksums being different?



























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

[JIRA] (JENKINS-14492) IAE Illegal character(s) in message header value from com.saucelabs.rest.Credential.call

2012-07-24 Thread jgl...@cloudbees.com (JIRA) 















































jglick
 closed  JENKINS-14492 as Fixed


IAE Illegal character(s) in message header value from com.saucelabs.rest.Credential.call
















User says the 1.18 plugin is working as expected. Thanks!





Change By:


jglick
(24/Jul/12 5:50 PM)




Status:


Resolved
Closed



























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

[JIRA] (JENKINS-14497) Can't start emulator with new Android SDK Tools rev. 20.0.1

2012-07-24 Thread kevin...@gmail.com (JIRA) 














































Kevin Chow
 commented on  JENKINS-14497


Cant start emulator with new Android SDK Tools rev. 20.0.1















Thank you for the fix. Would you push it as Plugin 2.3? So we could upgrade the plugin on our side? Thanks!



























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

[JIRA] (JENKINS-14039) Scan-build can be used without xcode

2012-07-24 Thread glimb...@gmail.com (JIRA) 














































glimberg
 commented on  JENKINS-14039


Scan-build can be used without xcode















This would indeed be very helpful.  I'd love to use the scan-build plugin in Jenkins, but my project is makefile based as well.



























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

[JIRA] (JENKINS-14560) Job names are only static string fields instead of auto-complete fields

2012-07-24 Thread jos...@java.net (JIRA) 














































Jose Sa
 created  JENKINS-14560


Job names are only static string fields instead of auto-complete fields















Issue Type:


Improvement



Assignee:


Unassigned


Components:


promoted-builds



Created:


24/Jul/12 7:45 PM



Description:


The fields referent for Job names in the Promote Plugin are not using the same component as other fields usually applicable to job naming that auto-complete the job names as you type.

This makes it required to copy/paste the name from a different source.




Environment:


Jenkins promoted builds plugin v2.6.1




Project:


Jenkins



Priority:


Major



Reporter:


Jose Sa

























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

[JIRA] (JENKINS-14561) Changing job names refered by Promoted builds plugin doesn't update when jobs are renamed

2012-07-24 Thread jos...@java.net (JIRA) 














































Jose Sa
 created  JENKINS-14561


Changing job names refered by Promoted builds plugin doesnt update when jobs are renamed















Issue Type:


Bug



Assignee:


Unassigned


Components:


promoted-builds



Created:


24/Jul/12 7:50 PM



Description:


We have some jobs configured with promotion processes dependent on downstream jobs to perform some actions when they succeed, however we noticed those actions not being taken after those downstream jobs were renamed.

It was then verified that the definition of those job names in the Promotion section were not correctly updated as it happens in all other parts that refer to a job.




Environment:


Jenkins promoted builds plugin v2.6.1




Project:


Jenkins



Priority:


Critical



Reporter:


Jose Sa

























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

[JIRA] (JENKINS-14420) All SSH hosts are changed to be copies of the first SSH host entry after upgrade to 2.0

2012-07-24 Thread edmund_wag...@java.net (JIRA) 














































edmund_wagner
 commented on  JENKINS-14420


All SSH hosts are changed to be copies of the first SSH host entry after upgrade to 2.0















could you provide a screenshot?



























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

[JIRA] (JENKINS-14442) Child processes are killed on finished jobs

2012-07-24 Thread edmund_wag...@java.net (JIRA) 














































edmund_wagner
 commented on  JENKINS-14442


Child processes are killed on finished jobs















does using "nohup" in the shell scripts 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

[JIRA] (JENKINS-14393) Jenkins CLI is not giving enough information to builds that it kicks off

2012-07-24 Thread jgl...@cloudbees.com (JIRA) 















































jglick
 resolved  JENKINS-14393 as Fixed


Jenkins CLI is not giving enough information to builds that it kicks off
















BTW include the text FIXED JENKINS-14393 in one of your commits to ensure that JIRA gets updated when the fix is pushed.





Change By:


jglick
(24/Jul/12 8: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

[JIRA] (JENKINS-14442) Child processes are killed on finished jobs

2012-07-24 Thread edmund_wag...@java.net (JIRA) 












































 
edmund_wagner
 edited a comment on  JENKINS-14442


Child processes are killed on finished jobs
















does "nohup" in the shell scripts solve the problem? 
in 2.0 i use pty=true in the jsch options, maybe that was a bad idea... 



























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

[JIRA] (JENKINS-14420) All SSH hosts are changed to be copies of the first SSH host entry after upgrade to 2.0

2012-07-24 Thread edmund_wag...@java.net (JIRA) 















































edmund_wagner
 assigned  JENKINS-14420 to edmund_wagner



All SSH hosts are changed to be copies of the first SSH host entry after upgrade to 2.0
















Change By:


edmund_wagner
(24/Jul/12 8:21 PM)




Assignee:


edmund_wagner



























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

[JIRA] (JENKINS-14442) Child processes are killed on finished jobs

2012-07-24 Thread edmund_wag...@java.net (JIRA) 















































edmund_wagner
 assigned  JENKINS-14442 to edmund_wagner



Child processes are killed on finished jobs
















Change By:


edmund_wagner
(24/Jul/12 8:21 PM)




Assignee:


edmund_wagner



























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

[JIRA] (JENKINS-14340) Remote directory of a Transfer Set should resolve env variable more than once

2012-07-24 Thread chantiv...@yahoo.fr (JIRA) 














































chanti vlad
 commented on  JENKINS-14340


Remote directory of a Transfer Set should resolve env variable more than once















@bap: thank you for answering. I didn't think it would be too easy so I'll be patient on that one 



























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

[JIRA] (JENKINS-14562) Gradle Plugin generates incorrect URLs for test reports

2012-07-24 Thread jenk...@saliman.net (JIRA) 














































Steve Saliman
 created  JENKINS-14562


Gradle Plugin generates incorrect URLs for test reports















Issue Type:


Bug



Affects Versions:


current



Assignee:


Gregory Boissinot



Components:


gradle



Created:


24/Jul/12 9:15 PM



Description:


In Gradle 1.0, the build displays the test report location as a fully qualified directory, but ends it with a period.  When Jenkins sends the failure email, it replaces the project directory with the project URL, but keeps the final period, resulting in a link that doesn't work. It would also be nice if Jenkins could add "/index.html" to the end of the URL it sends for quick access to the HTML file.

Gradle 1.1 (release candidate 1 was released today) changes the report directory to the actual filename, but it displays it as a URL that starts with file://.  According to http://forums.gradle.org/gradle/topics/whats_new_in_gradle_1_1_test_logging, this is so that Mac users can click on it and go directly to the file.  For Jenkins users, this will result in URLs that look like "file://http://myhost:80880/path-to-index.html", which won't work.  I added the quotes, but not the "", which jenkins put in the url.





Environment:


Linux




Project:


Jenkins



Priority:


Minor



Reporter:


Steve Saliman

























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

[JIRA] (JENKINS-13774) Provide option for cloning all branches with Mercurial SCM

2012-07-24 Thread jgl...@cloudbees.com (JIRA) 














































jglick
 commented on  JENKINS-13774


Provide option for cloning all branches with Mercurial SCM















Are you sure you do not want to use the Multiple SCMs Plugin for this use case?



























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

[JIRA] (JENKINS-14487) Allow parameterization of whether to use Xvnc for a build

2012-07-24 Thread jgl...@cloudbees.com (JIRA) 














































jglick
 commented on  JENKINS-14487


Allow parameterization of whether to use Xvnc for a build















Pull requests welcome.



























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

[JIRA] (JENKINS-7501) POST'ing a config.xml to create a new job via the XML API results in newlines being removed from XML elements containing them (ant build steps, winbatch steps, etc)

2012-07-24 Thread jgl...@cloudbees.com (JIRA) 














































jglick
 commented on  JENKINS-7501


POSTing a config.xml to create a new job via the XML API results in newlines being removed from XML elements containing them (ant build steps, winbatch steps, etc)















I suspect the use of javax.xml.transform.Transformer is to blame; this has been there since the POST support was added in 2008 (eabb943).



























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

[JIRA] (JENKINS-14563) show other ldap attribute as user name in security config than login attribute (cn)

2012-07-24 Thread cfo...@java.net (JIRA) 














































cforce
 created  JENKINS-14563


show other ldap attribute as user name in security config than login attribute (cn)















Issue Type:


Improvement



Affects Versions:


current



Assignee:


Unassigned


Components:


core



Created:


24/Jul/12 11:22 PM



Description:


I i configure right in project matrix for my ldap users the user id (cn) show there in our case is juts a number. This i ok ok for the user who normally know his id to login but its very difficult to maintain for a jenkins admin who first has to make a manual ldap lookup to get the persons real name (name, sn)




Project:


Jenkins



Priority:


Major



Reporter:


cforce

























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

[JIRA] (JENKINS-14563) show other ldap attribute as user name in security config than login attribute (cn)

2012-07-24 Thread cfo...@java.net (JIRA) 














































cforce
 updated  JENKINS-14563


show other ldap attribute as user name in security config than login attribute (cn)
















Change By:


cforce
(24/Jul/12 11:28 PM)




Description:


I
i
fi
configure
right
rights
in
jenkinssecurityconfig
projectmatrixfor
myldap
users
connectevialdaprealm,
theuserid(cn)
show
showw
thereinourcaseis
juts
just
anumber.
Thisiokokfortheuserwhonormallyknowhisidto
Addingnewusersviauid/
login
ldapattributeisok-,
but

itsverydifficulttomaintain
forajenkins
userbaseas
admin
whofirsthasto
withouthavingnameattributesshownforaveryuseralso.Atthemomenti
makeamanualldaplookup
viaaldapclient
togetthepersonsrealname(name,sn)
andthenbesureisetjenkinsaccessrightsforthecoorectuser.Ldapconfigshouldprovideconfigforldapattribswhicharealsoshownrightbehindldaploginid.Inourcasethiscouldbefirstname.THisadditionalinformationshallbeshowninglobalprojectmatrixcfgandjobsone.



























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

[JIRA] (JENKINS-14563) show name ldap attribute as user name in project matruix security config instead of ldap login attribute (cn)

2012-07-24 Thread cfo...@java.net (JIRA) 














































cforce
 updated  JENKINS-14563


show name ldap attribute as user name in project matruix security config instead of ldap login attribute (cn)
















Change By:


cforce
(24/Jul/12 11:29 PM)




Summary:


show
other
name
ldapattributeasusernamein
projectmatruix
securityconfig
than
insteadofldap
loginattribute(cn)



























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

[JIRA] (JENKINS-14207) Upgrade Selenium Grid Plugin to latest Selenium

2012-07-24 Thread apg...@java.net (JIRA) 














































apgray
 updated  JENKINS-14207


Upgrade Selenium Grid Plugin to latest Selenium
















Change By:


apgray
(24/Jul/12 11:33 PM)




Summary:


UpgradeSeleniumGridPluginto
latest
Selenium
2.24.1



























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

[JIRA] (JENKINS-14535) Fails to poll when no executors on master

2012-07-24 Thread scm_issue_l...@java.net (JIRA) 














































SCM/JIRA link daemon
 commented on  JENKINS-14535


Fails to poll when no executors on master















Code changed in jenkins
User: Gregory Boissinot
Path:
 pom.xml
http://jenkins-ci.org/commit/scripttrigger-plugin/0896100e4de81df0906ad4b419beb409d4bf00df
Log:
  Fix JENKINS-14535





























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

[JIRA] (JENKINS-14138) New git branch has empty changelist

2012-07-24 Thread jpsch...@mtu.net (JIRA) 














































jpschewe
 commented on  JENKINS-14138


New git branch has empty changelist















Will this create a changeset for new branches even if I don't have Jenkins setup to do merges itself?



























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

[JIRA] (JENKINS-4728) 403 on login using container security

2012-07-24 Thread lev...@zcolegia.com (JIRA) 














































levani dvalishvili
 commented on  JENKINS-4728


403 on login using container security















I do have same issue with Glassfish 3.1.2 / Jenkins ver. 1.475
also adding user group membership to user, does not solve the issue .
its worth mentioning that I am not using matrix, i have option of 
"logged in user can do anything" selected. and container based authentication.




























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

[JIRA] (JENKINS-14442) Child processes are killed on finished jobs

2012-07-24 Thread i...@moe-k.de (JIRA) 














































Klaus
 commented on  JENKINS-14442


Child processes are killed on finished jobs















To use "nohup" maybe a workaround, but that's not very nice. 
I think the "channel.setPty(true)" is the problem. No pseudo terminal is needed in my opinion. Could you try to set the boolean to "false", please?



























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