[JIRA] (JENKINS-16294) windows managed batch looses arguments when used within testlink

2013-01-10 Thread angela.bauer....@rohde-schwarz.com (JIRA)














































Angela Bauer
 updated  JENKINS-16294


windows managed batch looses arguments when used within testlink
















Change By:


Angela Bauer
(11/Jan/13 7:54 AM)




Description:


"Execute managed windows batch" within  "Test Execution" within Testlink looses the defined arguments (both in "single build steps" and as well in "iterative test build steps"
)
.The used windows batch file defines one argument, which is shown as "required arguments".Clicking on "Define arguments" I can input an argument.Clicking on "Save", then again on "Configure", to have a look on my Jenkins Job, this argument is lost.Doing the same outside of Testlink, "Execute manage windows batch" works as it should, the arguments are kept.I attach a printout with a very simple example, which I only used for testing purposes.
testlink plugin version: 3.1.8



























This message is automatically generated by JIRA.
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-8334) maven-plugin insists on Surefire to run tests

2013-01-10 Thread a...@bedatadriven.com (JIRA)












































  
Alexander Bertram
 edited a comment on  JENKINS-8334


maven-plugin insists on Surefire to run tests
















Here's a build of the maven-plugin.hpi from the kutzi's pull request.
(see attachment at top of page)



























This message is automatically generated by JIRA.
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-8334) maven-plugin insists on Surefire to run tests

2013-01-10 Thread a...@bedatadriven.com (JIRA)














































Alexander Bertram
 updated  JENKINS-8334


maven-plugin insists on Surefire to run tests
















Built from https://github.com/jenkinsci/jenkins/pull/668





Change By:


Alexander Bertram
(11/Jan/13 7:50 AM)




Attachment:


maven-plugin-kutzi.hpi



























This message is automatically generated by JIRA.
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-8334) maven-plugin insists on Surefire to run tests

2013-01-10 Thread a...@bedatadriven.com (JIRA)














































Alexander Bertram
 commented on  JENKINS-8334


maven-plugin insists on Surefire to run tests















Here's a build of the maven-plugin.hpi from the kutzi's pull request.



























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






[JIRA] (JENKINS-16310) Source code loses spacing/indenting due to html white space collapsing.

2013-01-10 Thread ognjen.bub...@gmail.com (JIRA)














































Ognjen Bubalo
 commented on  JENKINS-16310


Source code loses spacing/indenting due to html white space collapsing.















Hi,
Which plugin version do you use?

Thanks,
Ogi



























This message is automatically generated by JIRA.
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-16278) "Remember me on this computer" does not work, cookie is not accepted in new session

2013-01-10 Thread xiaopan3...@gmail.com (JIRA)














































Bao Xiaopan(Bob)
 commented on  JENKINS-16278


"Remember me on this computer" does not work, cookie is not accepted in new session















Same Problem occurred in my side... 
What's the latest status for this topic?!



























This message is automatically generated by JIRA.
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-8334) maven-plugin insists on Surefire to run tests

2013-01-10 Thread jwb...@gmail.com (JIRA)














































John Bito
 commented on  JENKINS-8334


maven-plugin insists on Surefire to run tests















The HPI file is a subversion plugin. Maven plugin available?



























This message is automatically generated by JIRA.
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-16157) Regression Report: Send only to culprit, make contents editable

2013-01-10 Thread skypen...@gmail.com (JIRA)














































Kengo TODA
 commented on  JENKINS-16157


Regression Report: Send only to culprit, make contents editable















Thanks for your feedback.

To manage requests easily, I have divided this issue into 2 tickets at GitHub. Please check it.


	https://github.com/jenkinsci/regression-report-plugin/issues/1
	https://github.com/jenkinsci/regression-report-plugin/issues/2





























This message is automatically generated by JIRA.
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-16311) Feature to display contributory upstream job changes in downstream builds

2013-01-10 Thread nuad...@java.net (JIRA)














































nuadhu1
 created  JENKINS-16311


Feature to display contributory upstream job changes in downstream builds















Issue Type:


New Feature



Affects Versions:


current



Assignee:


kutzi



Components:


downstream-ext



Created:


10/Jan/13 10:35 PM



Description:


I have a build heirarchy consisting of 15 separate modules (jobs) where several upstream "lib" jobs trigger several intermediate downstream jobs and a lowest-level job which produces a installable *.exe artifact. 

In the intermediate and lowest-level jobs, I'd like to be able to see a list of changes from the contributing upstream jobs.  For example,  "lib a" job polls and spins on a new SCM commit and then triggers "lib b" job which also has some bug fix commits.  Finally, the lowest-level "installer" build job gets triggered.I'd like to see a list of the "contributing" changes from all the upstream build jobs in the "changes" page of the "installer" job.   For example, maybe show changes for the installer job and then in a different section all the upstream contributing changes kinda like a release notes.  The changes report would include both SCM code changes/comments and any build dependency changes.

-G




Project:


Jenkins



Priority:


Minor



Reporter:


nuadhu1

























This message is automatically generated by JIRA.
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-8334) maven-plugin insists on Surefire to run tests

2013-01-10 Thread a...@bedatadriven.com (JIRA)














































Alexander Bertram
 commented on  JENKINS-8334


maven-plugin insists on Surefire to run tests















I've tried uploading the HPI to our 'real' jenkins server, but i'm not sure jenkins is using it-- will installation via upload work for a "core" plugin or do i have to replace it on the filesystem and restart 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-14193) EnvInject doesn't pass variables defined in prebuild step if maven project is used

2013-01-10 Thread gagoja...@gmail.com (JIRA)














































Jaime Gago
 commented on  JENKINS-14193


EnvInject doesn't pass variables defined in prebuild step if maven project is used















Hey Gregory, thanks for your time on this, I'm certainly not going to go Project Manager on you, this is Open Source! All that said I don't know if you've read my problem but I think your workaround just doesn't apply in my case because of the dynamic nature of what I need to inject and it being computed after a checkout. The only way out of this I see in my case is to work with commit hooks to create a property file but if you have another idea I'll take it (for free  )

In any case thanks for the plugin it was so close to work on itself for me !



























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






[JIRA] (JENKINS-5408) Quoting Issue with JDK Installer with Windows Slave

2013-01-10 Thread robtechst...@gmail.com (JIRA)














































Rob Techstuff
 commented on  JENKINS-5408


Quoting Issue with JDK Installer with Windows Slave















Glad to see that this has been fixed. What needs to be done to get the fix into the next LTS version? Our Jenkins build farm runs both Linux and Windows slaves, and this problem forces us to manually install and configure OS-specific JDK versions on all slaves.

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-16279) Parameter paths are not correctly calculated when master is running on Windows machine

2013-01-10 Thread kiy0t...@java.net (JIRA)















































kiy0taka
 resolved  JENKINS-16279 as Fixed


Parameter paths are not correctly calculated when master is running on Windows machine
















Change By:


kiy0taka
(10/Jan/13 10:07 PM)




Status:


In Progress
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-16310) Source code loses spacing/indenting due to html white space collapsing.

2013-01-10 Thread bart...@zak.name (JIRA)














































Bartosz Zak
 created  JENKINS-16310


Source code loses spacing/indenting due to html white space collapsing.















Issue Type:


Improvement



Assignee:


Ognjen Bubalo



Components:


jacoco



Created:


10/Jan/13 9:52 PM



Description:


Source code loses spacing/indenting due to html white space collapsing.
Please add to style.css :

code {white-space: pre;}





Project:


Jenkins



Priority:


Minor



Reporter:


Bartosz Zak

























This message is automatically generated by JIRA.
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-16279) Parameter paths are not correctly calculated when master is running on Windows machine

2013-01-10 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-16279


Parameter paths are not correctly calculated when master is running on Windows machine















Code changed in jenkins
User: Kiyotaka Oku
Path:
 .gitignore
 pom.xml
 src/main/java/org/jenkinsci/plugins/mongodb/MongoBuildWrapper.java
 src/test/java/org/jenkinsci/plugins/mongodb/MongoBuildWrapperTest.java
http://jenkins-ci.org/commit/mongodb-plugin/71c881f4d30fa48d9de7de64ba0ba3d4634bebcc
Log:
  Merge pull request #1 from borgeorgiev/master

Fix for JENKINS-16279


Compare: https://github.com/jenkinsci/mongodb-plugin/compare/c0db6d8b0da9...71c881f4d30f




























This message is automatically generated by JIRA.
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-16233) EnvInject plugin using a cached value for ${WORKSPACE}

2013-01-10 Thread gregory.boissi...@gmail.com (JIRA)














































Gregory Boissinot
 started work on  JENKINS-16233


EnvInject plugin using a cached value for ${WORKSPACE}
















Change By:


Gregory Boissinot
(10/Jan/13 9:38 PM)




Status:


Open
In Progress



























This message is automatically generated by JIRA.
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-16233) EnvInject plugin using a cached value for ${WORKSPACE}

2013-01-10 Thread gregory.boissi...@gmail.com (JIRA)














































Gregory Boissinot
 commented on  JENKINS-16233


EnvInject plugin using a cached value for ${WORKSPACE}















JENKINS-15658 was introduced in version 1.73. Therefore, if it is the cause, you have to downgrade to 1.72.
For this issue, it seems not to be a workspace from another job but a shared workspace.
Does this value is specified in another place in the job or in the global configuration?



























This message is automatically generated by JIRA.
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-14193) EnvInject doesn't pass variables defined in prebuild step if maven project is used

2013-01-10 Thread gregory.boissi...@gmail.com (JIRA)












































  
Gregory Boissinot
 edited a comment on  JENKINS-14193


EnvInject doesn't pass variables defined in prebuild step if maven project is used
















I will not change my priorities. There are more important issues. In addition, you have a workaround and it works. The issue is assigned to me automatically because I'm the creator and the owner of the plugin.
I made the analysis of the issue and give the technical solution. 
If you want to fix it quickly, feel free to do the pull request by yourself.



























This message is automatically generated by JIRA.
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-14193) EnvInject doesn't pass variables defined in prebuild step if maven project is used

2013-01-10 Thread gregory.boissi...@gmail.com (JIRA)














































Gregory Boissinot
 commented on  JENKINS-14193


EnvInject doesn't pass variables defined in prebuild step if maven project is used















I will not change my priorities. There a more important issues. In addition, you have a workaround and it works. The issue is assigned to me automatically because I'm the creator and the owner of the plugin.
I made the analysis of the issue and give the technical solution. 
If you want to fix it quickly, feel free to do the pull request by yourself.



























This message is automatically generated by JIRA.
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-12400) Discard old build does not working

2013-01-10 Thread ever...@free.fr (JIRA)















































evernat
 resolved  JENKINS-12400 as Incomplete


Discard old build does not working
















No response from the reporter, so resolving as incomplete.





Change By:


evernat
(10/Jan/13 8:34 PM)




Status:


Open
Resolved





Resolution:


Incomplete



























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






[JIRA] (JENKINS-16309) CLI errors with Job names containing dashes

2013-01-10 Thread r4r...@yahoo.com (JIRA)














































Rita Garcia
 created  JENKINS-16309


CLI errors with Job names containing dashes















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


cli



Created:


10/Jan/13 8:32 PM



Description:


Jenkins v 1.498 does not allow command line builds with jobs containing dashes, ie hello-world-job, in their name. It is unable to find the build and says it does not exist. This is through the CLI interface.




Project:


Jenkins



Priority:


Major



Reporter:


Rita Garcia

























This message is automatically generated by JIRA.
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-15603) Cannot find changelist number for arbitrary job (api/xml should list it)

2013-01-10 Thread rob.pe...@gmail.com (JIRA)














































Rob Petti
 commented on  JENKINS-15603


Cannot find changelist number for arbitrary job (api/xml should list it)















Sorry, I'm still working on this, just having a lot of issues trying to export this value... :/



























This message is automatically generated by JIRA.
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-15994) Perforce session ticket is not parsed correctly (again)

2013-01-10 Thread af...@java.net (JIRA)














































aflat
 commented on  JENKINS-15994


Perforce session ticket is not parsed correctly (again)















Built locally and tested, works great 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-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used

2013-01-10 Thread egues...@java.net (JIRA)












































  
eguess74
 edited a comment on  JENKINS-15779


Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
















We have resolved compilation problem. I don't know why I'm the only one who got this, but It seems to be a Java bug:
http://stackoverflow.com/questions/4829576/javac-error-inconvertible-types-with-generics

So if the IvyBuild.java is changed in this way it compiles OK:

 
diff --git a/src/main/java/hudson/ivy/IvyBuild.java b/src/main/java/hudson/ivy/IvyBuild.java
index fbe04d6..d98fb80 100644
--- a/src/main/java/hudson/ivy/IvyBuild.java
+++ b/src/main/java/hudson/ivy/IvyBuild.java
@@ -498,8 +498,13 @@ public class IvyBuild extends AbstractIvyBuild {
 }

 public void buildEnvVars(AbstractBuild build, EnvVars env) {
-env.put("IVY_MODULE_NAME", ((IvyModule) build.getParent()).getModuleName().name);
-env.put("IVY_MODULE_ORGANISATION", ((IvyModule) build.getParent()).getModuleName().organisation);
+//env.put("IVY_MODULE_NAME", ((IvyModule) build.getParent()).getModuleName().name);
+//env.put("IVY_MODULE_ORGANISATION", ((IvyModule) build.getParent()).getModuleName().organisation);
+Object o = build.getParent();
+ModuleName n = ( ( IvyModule ) o ).getModuleName() ;
+env.put("IVY_MODULE_NAME", n.name);
+env.put("IVY_MODULE_ORGANISATION", n.organisation);
+
 }
 }
 }

 



























This message is automatically generated by JIRA.
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-12127) Maven incremental build doesn't work when changes are in svn:externals

2013-01-10 Thread ku...@gmx.de (JIRA)














































kutzi
 commented on  JENKINS-12127


Maven incremental build doesn't work when changes are in svn:externals















@Tom A.: you're using Hudson or 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-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used

2013-01-10 Thread egues...@java.net (JIRA)












































  
eguess74
 edited a comment on  JENKINS-15779


Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
















We have resolved compilation problem. I don't know why I'm the only one who got this, but It seems to be a Java bug:
http://stackoverflow.com/questions/4829576/javac-error-inconvertible-types-with-generics

So if the IvyBuild.java is changed in this way it compiles OK:

diff --git a/src/main/java/hudson/ivy/IvyBuild.java b/src/main/java/hudson/ivy/IvyBuild.java
index fbe04d6..d98fb80 100644
— a/src/main/java/hudson/ivy/IvyBuild.java
+++ b/src/main/java/hudson/ivy/IvyBuild.java
@@ -498,8 +498,13 @@ public class IvyBuild extends AbstractIvyBuild {
 }

 public void buildEnvVars(AbstractBuild build, EnvVars env) {

-env.put("IVY_MODULE_NAME", ((IvyModule) build.getParent()).getModuleName().name);

-env.put("IVY_MODULE_ORGANISATION", ((IvyModule) build.getParent()).getModuleName().organisation);

+//env.put("IVY_MODULE_NAME", ((IvyModule) build.getParent()).getModuleName().name);

+//env.put("IVY_MODULE_ORGANISATION", ((IvyModule) build.getParent()).getModuleName().organisation);

+Object o = build.getParent();

+ModuleName n = ( ( IvyModule ) o ).getModuleName() ;

+env.put("IVY_MODULE_NAME", n.name);

+env.put("IVY_MODULE_ORGANISATION", n.organisation);

+

 }

 }

 }




























This message is automatically generated by JIRA.
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-16304) complete perforce changelist history in email

2013-01-10 Thread rob.pe...@gmail.com (JIRA)














































Rob Petti
 commented on  JENKINS-16304


complete perforce changelist history in email















No, do not raise a ticket, just ask on the mailing list. It's readily available on the jenkins-ci website: jenkinsci-us...@googlegroups.com



























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






[JIRA] (JENKINS-16308) executing external C++ application through batch failure

2013-01-10 Thread sarra.be...@gmail.com (JIRA)














































sarra beng
 created  JENKINS-16308


executing external C++ application through batch failure















Issue Type:


Bug



Affects Versions:


current



Assignee:


Kohsuke Kawaguchi



Components:


batch-task



Created:


10/Jan/13 4:46 PM



Description:


I'm trying to execute a console application (created using Microsoft Visual C++) that enables to do signal measurements through a measurement equipment. 
When the application is executed directly by batch under Windows (console),  it does measurements and make results without any problem. 
When the application is launched by Jenkins (execute Windows Batch Command), it executes simple C++ instructions such as "printf", but the instructions provided by VISA library is not recognized (got "failure: Error - A code library required by VISA could not be loaded" and execution is stopped) 




Environment:


Windows




Project:


Jenkins



Priority:


Major



Reporter:


sarra beng

























This message is automatically generated by JIRA.
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-16304) complete perforce changelist history in email

2013-01-10 Thread prasad.ushan...@gmail.com (JIRA)














































Uma shankar
 commented on  JENKINS-16304


complete perforce changelist history in email















Thanks for your reply.

For 1st question, do i need to raise ticket under Email-ext?

Could you also please share mailing listid and your email id?

Thank you.



























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






[JIRA] (JENKINS-16307) Updating bundled plugin can leave behind old pinned dependency

2013-01-10 Thread jgl...@cloudbees.com (JIRA)














































Jesse Glick
 created  JENKINS-16307


Updating bundled plugin can leave behind old pinned dependency















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


10/Jan/13 4:34 PM



Description:


Reproduced with Jenkins Enterprise but may be more generally applicable. Start with 1.466.2.1 which bundles old versions of analysis-core and findbugs. Upgrade analysis-core to 1.47, pinning it. Now run 1.466.12.1 which bundles analysis-core:1.48 and findbugs:4.45. Then you are running findbugs:4.45 with analysis-core:1.47. This is very bad because 4.45 requires analysis-core:1.48 in its Plugin-Dependencies and in fact throws a LinkageError when you try to run or configure jobs using FindBugs.

The plugin manager should somehow detect when upgrading an unpinned plugin from the bundled HPI would cause a version clash with a pinned plugin, and either refuse to upgrade the downstream plugin or ignore the pin and upgrade both.




Project:


Jenkins



Labels:


plugin




Priority:


Major



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






[JIRA] (JENKINS-16304) complete perforce changelist history in email

2013-01-10 Thread rob.pe...@gmail.com (JIRA)















































Rob Petti
 resolved  JENKINS-16304 as Not A Defect


complete perforce changelist history in email
















Questions are better posed on the mailing list, or by sending me an email directly.

1: That would be a question for the email-ext maintainer.

2: Use the ${ENV,var=...} token macro to reference the P4_CHANGELIST environment variable, ie ${ENV,var="P4_CHANGELIST"}.





Change By:


Rob Petti
(10/Jan/13 4:30 PM)




Status:


Open
Resolved





Resolution:


Not A Defect



























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






[JIRA] (JENKINS-16306) Plugin Manager » Upload File misbehaves when filename not arttifactId.hpi

2013-01-10 Thread jgl...@cloudbees.com (JIRA)














































Jesse Glick
 created  JENKINS-16306


Plugin Manager » Upload File misbehaves when filename not arttifactId.hpi















Issue Type:


Bug



Assignee:


Jesse Glick



Components:


core



Created:


10/Jan/13 4:25 PM



Description:


Say you have someplugin installed at version 1.1, and you use Upload File to upload someplugin-1.2.hpi from your local Maven repository. doUploadPlugin will save $JENKINS_HOME/plugins/someplugin-1.2.jpi alongside the existing $JENKINS_HOME/plugins/someplugin.jpi, and will not create a $JENKINS_HOME/plugins/someplugin.jpi.pinned as expected, leading to a confused situation.

Workaround is to locally rename the file to someplugin.hpi before uploading.




Project:


Jenkins



Labels:


plugin




Priority:


Major



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






[JIRA] (JENKINS-16305) Add support for Quiet period configuration slicing

2013-01-10 Thread m...@nordicsemi.no (JIRA)














































Markus Hjerto
 created  JENKINS-16305


Add support for Quiet period configuration slicing















Issue Type:


New Feature



Assignee:


mdonohue



Components:


configurationslicing



Created:


10/Jan/13 4:18 PM



Description:


It would be great if thus plugin could support slicing the Quiet period configuration item.

Thanks for a great plugin! Use it all the time!




Project:


Jenkins



Priority:


Major



Reporter:


Markus Hjerto

























This message is automatically generated by JIRA.
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-12769) Cannot specify location of gradle wrapper

2013-01-10 Thread david.pars...@gmail.com (JIRA)














































David Pärsson
 reopened  JENKINS-12769


Cannot specify location of gradle wrapper
















Change By:


David Pärsson
(10/Jan/13 4:10 PM)




Resolution:


Fixed





Status:


Resolved
Reopened



























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






[JIRA] (JENKINS-12769) Cannot specify location of gradle wrapper

2013-01-10 Thread david.pars...@gmail.com (JIRA)














































David Pärsson
 commented on  JENKINS-12769


Cannot specify location of gradle wrapper















What if the gradlew file does not reside in the root build script project? We're in the situation where we have a multi-project Gradle build, but we don't always want to build from the master directory (where gradlew resides).

I'd like the ability to supply a relative path to gradlew, or a relative folder where gradlew resides. That path should ideally be relative to the root build script directory.



























This message is automatically generated by JIRA.
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-13110) Automatic tool installer: Install from mongodb.org option doesn't include a label field

2013-01-10 Thread bor.georg...@gmail.com (JIRA)












































  
Boris Georgiev
 edited a comment on  JENKINS-13110


Automatic tool installer: Install from mongodb.org option doesn't include a label field
















The json file given as an example on https://wiki.jenkins-ci.org/display/JENKINS/Adding+tool+auto-installer does not seem to contain any information about the OS which the described installer is applicable for, so the hudson.tools.DownloadFromUrlInstaller.Installable does not contain a field with OS information so it is obviously not implemented. I'll try to contribute a patch for this in a few weeks, but it will be good if someone more experienced comments if I'm on the right track .



























This message is automatically generated by JIRA.
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-13110) Automatic tool installer: Install from mongodb.org option doesn't include a label field

2013-01-10 Thread bor.georg...@gmail.com (JIRA)














































Boris Georgiev
 commented on  JENKINS-13110


Automatic tool installer: Install from mongodb.org option doesn't include a label field















The json file given as an example on https://wiki.jenkins-ci.org/display/JENKINS/Adding+tool+auto-installer does not seem to contain any information about the OS which the described installer is applicable for, so the hudson.tools.DownloadFromUrlInstaller.Installable does not contain a field with OS information so it is obviously not implemented. I'll try to contribute a patch for this in a few 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-13110) Automatic tool installer: Install from mongodb.org option doesn't include a label field

2013-01-10 Thread bor.georg...@gmail.com (JIRA)














































Boris Georgiev
 commented on  JENKINS-13110


Automatic tool installer: Install from mongodb.org option doesn't include a label field















I'm currently experiencing the same problem, but in my case the JDK installer works correclty on both Windows and Linux systems. The problem seems to be present only in installers extending the DownloadFromUrlInstaller.



























This message is automatically generated by JIRA.
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-16304) complete perforce changelist history in email

2013-01-10 Thread prasad.ushan...@gmail.com (JIRA)














































Uma shankar
 created  JENKINS-16304


complete perforce changelist history in email















Issue Type:


Task



Affects Versions:


current



Assignee:


Rob Petti



Components:


perforce



Created:


10/Jan/13 3:54 PM



Description:


Hi,

i am have been using perforce plugin for integration with SCM. I have some issue with the plugin.
1:Email integration
I use Email-ext plugin and tring get complete changelist history in mail with revision no and workspace as display on build home page.
Exam: (Expected to be in e-mail)
Changes
1436416 by umashankar@umashakar-test on Jan 10, 2013 8:44:54 AM
Forcing a build 
Affected Files: 
//myproject/src/test/java/control.java(#16)

But i have used some keyword to get this things in email like:
List of changed file(s):
${CHANGES, showPaths=true}

${CHANGES_SINCE_LAST_SUCCESS, showPaths=true}

And output is:
List of changed file(s):
[umashankar] Updates
	src/test/java/control.java

Changes for Build #16
[umashankar] Updates
	src/test/java/control.java

It is missing the full path, revision number, changelist  workspace.

2: P4 changelist->

I want to capture highest changelist number from changes, I have tried P4_CHANGELIST variable, but this does give any thing. Could you please let me know if there are any other variable which has Last changlist or Higest changelist number.

Early reply would be much helpful.

Thank you.




Due Date:


14/Jan/13 12:00 AM




Environment:


Windows




Fix Versions:


current



Project:


Jenkins



Priority:


Major



Reporter:


Uma shankar

























This message is automatically generated by JIRA.
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-16303) "Console" link missing in pop-up dialog on dashboard

2013-01-10 Thread ryan.shoema...@gmail.com (JIRA)














































ryan shoemaker
 created  JENKINS-16303


"Console" link missing in pop-up dialog on dashboard















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Attachments:


config.xml, Screen Shot 2013-01-08 at 4.50.06 PM.png



Components:


core



Created:


10/Jan/13 3:46 PM



Description:


After creating a new job, the "Console" link is missing from the pop-up menu when hovering over a build id on the dashboard page (see attached image).

https://groups.google.com/forum/?fromgroups=#!topic/jenkinsci-users/w4b9W-KflPQ

The job is a free form and all it does is ssh into a remote system, grab some data, and echo it so Jenkins can archive the results.  I've attached the config.xml.

The console output does exist in Jenkins filesystem and if you click on a particular build id, the console output link is shown in the top left navigation area.




Environment:


Jenkins 1.492



Deployed on GlassFish 3.1.2



java version "1.6.0_32"

Java(TM) SE Runtime Environment (build 1.6.0_32-b05)

Java HotSpot(TM) 64-Bit Server VM (build 20.7-b02, mixed mode)



Linux 2.6.32-71.29.1.el6.x86_64 #1 SMP Mon Jun 27 19:49:27 BST 2011 x86_64 x86_64 x86_64 GNU/Linux




Project:


Jenkins



Labels:


ui
console,




Priority:


Minor



Reporter:


ryan shoemaker

























This message is automatically generated by JIRA.
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-16302) Resource remains locked after job abort

2013-01-10 Thread massimo.rosse...@azcom.it (JIRA)














































Massimo Rossello
 created  JENKINS-16302


Resource remains locked after job abort















Issue Type:


Bug



Affects Versions:


current



Assignee:


rsandell



Components:


external-resource-dispatcher



Created:


10/Jan/13 3:18 PM



Description:


An aborted job does not release its locked resouce even if it reports it does


Collecting metadata...
Metadata collection done.
Releasing previously locked resource: 0019001200190072...
Resource 0019001200190072 successfully released.
Finished: ABORTED




Environment:


Jenkins 1.478 

external-resource-dispatcher 1.0b 

metadata 1.0b




Project:


Jenkins



Labels:


abort




Priority:


Major



Reporter:


Massimo Rossello

























This message is automatically generated by JIRA.
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-16301) Fingerprint performance

2013-01-10 Thread jgl...@cloudbees.com (JIRA)














































Jesse Glick
 created  JENKINS-16301


Fingerprint performance















Issue Type:


Bug



Assignee:


Jesse Glick



Components:


core



Created:


10/Jan/13 3:03 PM



Description:


A user working with files in the 100+ Mb range asked whether fingerprinting them was expensive. Probably it is not that expensive but it is likely the implementation could be optimized and at least measured.

As far as the I/O goes, FilePath.digest uses FileInputStream rather than NIO—hmm, maybe OK. It does not use buffering, which may or may not be an issue here. Then it calls Util.getDigestOf.

That uses the JRE’s MD5 implementation which AFAIK takes advantage of any cryptographic hardware acceleration when available. It does read into a 1024-byte buffer however which seems excessively small. (And uses a proxy stream rather than simply calling the update method, which is odd.) http://stackoverflow.com/questions/9321912/very-slow-when-generaing-md5-using-java-with-large-file suggests using a custom library though this may be overkill; others suggest DigestUtils from Commons Codec.




Project:


Jenkins



Labels:


performance
fingerprints




Priority:


Minor



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






[JIRA] (JENKINS-16300) Dashborad plugin shows 2008R2 / 2012 connected slaves as offline

2013-01-10 Thread morl...@java.net (JIRA)














































morlajb
 created  JENKINS-16300


Dashborad plugin shows 2008R2 / 2012 connected slaves as offline















Issue Type:


Bug



Assignee:


Peter Hayes



Components:


dashboard-view



Created:


10/Jan/13 2:32 PM



Description:


all slaves of 2008R2 & 2012 that connect using JNLP display as disconnected although they are connected.




Environment:


master -  2008 64 bit.




Project:


Jenkins



Priority:


Minor



Reporter:


morlajb

























This message is automatically generated by JIRA.
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-6890) clone-workspace-scm doesn't work when source job is a matrix job.

2013-01-10 Thread trnl...@gmail.com (JIRA)














































Uladzimir Mihura
 commented on  JENKINS-6890


clone-workspace-scm doesn't work when source job is a matrix job.















Fixed this:
https://github.com/jenkinsci/jenkins-clone-workspace-scm-plugin/pull/3

-vova



























This message is automatically generated by JIRA.
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-6922) PROJECT_URL variable not correctly set when email is sent by Promoted Build Plugin

2013-01-10 Thread slide.o....@gmail.com (JIRA)














































Slide-O-Mix
 commented on  JENKINS-6922


PROJECT_URL variable not correctly set when email is sent by Promoted Build Plugin















The other idea (and I said I didn't have any other ideas!) would be to use a Groovy script to get at the data you want and present that in the email.



























This message is automatically generated by JIRA.
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-16298) DRY FATAL: null java.lang.StackOverflowError

2013-01-10 Thread ullrich.haf...@gmail.com (JIRA)














































Ulli Hafner
 updated  JENKINS-16298


DRY FATAL: null   java.lang.StackOverflowError
















Change By:


Ulli Hafner
(10/Jan/13 2:17 PM)




Component/s:


analysis-core





Component/s:


analysis-collector



























This message is automatically generated by JIRA.
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-16298) DRY FATAL: null java.lang.StackOverflowError

2013-01-10 Thread ullrich.haf...@gmail.com (JIRA)














































Ulli Hafner
 commented on  JENKINS-16298


DRY FATAL: null   java.lang.StackOverflowError















Which Jenkins and dry version are you using? Is this a freestyle or maven project type?



























This message is automatically generated by JIRA.
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-16296) Sometimes commits that mix property changes and text changes do not cause project to be triggered

2013-01-10 Thread step...@eucodos.de (JIRA)















































Stephan Pauxberger
 closed  JENKINS-16296 as Not A Defect


Sometimes commits that mix property changes and text changes do not cause project to be triggered
















Change By:


Stephan Pauxberger
(10/Jan/13 2:04 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-12127) Maven incremental build doesn't work when changes are in svn:externals

2013-01-10 Thread ar3...@gmail.com (JIRA)














































Tom A.
 commented on  JENKINS-12127


Maven incremental build doesn't work when changes are in svn:externals















I am using hudson and when updating svn view which consists of externals only, every update on subdirectories (from externals) is updated in hudson workspace but changelog says that nothing was modified and the file changelog.xml is wrong (has only "" string inside)  It seems like JENKINS-12127 patch could fix it but ticket is still open and not resolved yet. This is a mustbe functionality for me. Some other plugins depends on changelog for example 'Scan for compiler warnings' will not be launched because of empty changelog. 

Could you tell me if it is going to be delivered? 
Kindly waiting for response. 



























This message is automatically generated by JIRA.
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-16299) Add groups to reverse proxy auth

2013-01-10 Thread laurent.f...@math.u-bordeaux1.fr (JIRA)














































Laurent FACQ
 created  JENKINS-16299


Add groups to reverse proxy auth















Issue Type:


New Feature



Assignee:


Unassigned


Components:


reverse-proxy-auth



Created:


10/Jan/13 1:16 PM



Description:


Add the ability to choose an HTTP header to pass groups informations related to the user. so w'll have on header for the user id and one (optionnal) for group(s) info. (coma separated fro ex.)

An other possibility could be to allow to combine reverse-proxy-auth (for user identification) and a script from script-security-realm to get only the groups of the user.




Project:


Jenkins



Priority:


Major



Reporter:


Laurent FACQ

























This message is automatically generated by JIRA.
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-16296) Sometimes commits that mix property changes and text changes do not cause project to be triggered

2013-01-10 Thread step...@eucodos.de (JIRA)















































Stephan Pauxberger
 resolved  JENKINS-16296 as Not A Defect


Sometimes commits that mix property changes and text changes do not cause project to be triggered
















Actually, the problem was caused by a wrong post-commit hook (Argument List to long), however I will create a pull request for the corrected test case.





Change By:


Stephan Pauxberger
(10/Jan/13 1:05 PM)




Status:


Open
Resolved





Resolution:


Not A Defect



























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






[JIRA] (JENKINS-16279) Parameter paths are not correctly calculated when master is running on Windows machine

2013-01-10 Thread bor.georg...@gmail.com (JIRA)














































Boris Georgiev
 stopped work on  JENKINS-16279


Parameter paths are not correctly calculated when master is running on Windows machine
















Change By:


Boris Georgiev
(10/Jan/13 1:02 PM)




Status:


In Progress
Open



























This message is automatically generated by JIRA.
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-16279) Parameter paths are not correctly calculated when master is running on Windows machine

2013-01-10 Thread bor.georg...@gmail.com (JIRA)














































Boris Georgiev
 started work on  JENKINS-16279


Parameter paths are not correctly calculated when master is running on Windows machine
















Change By:


Boris Georgiev
(10/Jan/13 1:03 PM)




Status:


Open
In Progress



























This message is automatically generated by JIRA.
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-16279) Parameter paths are not correctly calculated when master is running on Windows machine

2013-01-10 Thread bor.georg...@gmail.com (JIRA)














































Boris Georgiev
 started work on  JENKINS-16279


Parameter paths are not correctly calculated when master is running on Windows machine
















Change By:


Boris Georgiev
(10/Jan/13 1:02 PM)




Status:


Open
In Progress



























This message is automatically generated by JIRA.
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-16279) Parameter paths are not correctly calculated when master is running on Windows machine

2013-01-10 Thread bor.georg...@gmail.com (JIRA)















































Boris Georgiev
 assigned  JENKINS-16279 to Boris Georgiev



Parameter paths are not correctly calculated when master is running on Windows machine
















Change By:


Boris Georgiev
(10/Jan/13 1:02 PM)




Assignee:


Boris Georgiev



























This message is automatically generated by JIRA.
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-16279) Parameter paths are not correctly calculated when master is running on Windows machine

2013-01-10 Thread bor.georg...@gmail.com (JIRA)














































Boris Georgiev
 commented on  JENKINS-16279


Parameter paths are not correctly calculated when master is running on Windows machine















proposed fix  - https://github.com/jenkinsci/mongodb-plugin/pull/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-16045) Subversion plugin doesn't adhere getAffectedPaths() contract

2013-01-10 Thread math...@codercpf.be (JIRA)














































Mathias Teugels
 commented on  JENKINS-16045


Subversion plugin doesn't adhere getAffectedPaths() contract















At the very least, it's supposed to be normalized to not start with a '/'
Also, and this might not be seen as the best way of proceeding, but we might want to check out the implementations of other SCM plugins.

Another source for information might be the usages of the function, where it is used that I know for sure is the maven plugin. This plugin assumes that the normalization at the very least has been taken care of (removing the leading '/'), and also assumes it is a relative path to the workspace. Perhaps this last assumption is wrong and might need fixing there, but in the end, one change we are sure about is the leading '/'!



























This message is automatically generated by JIRA.
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-16298) DRY FATAL: null java.lang.StackOverflowError

2013-01-10 Thread e...@altoqi.com.br (JIRA)














































Eric Brito
 updated  JENKINS-16298


DRY FATAL: null   java.lang.StackOverflowError
















here's the XML file





Change By:


Eric Brito
(10/Jan/13 11:25 AM)




Attachment:


simian.xml



























This message is automatically generated by JIRA.
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-16297) FATAL: Could not apply tag [project name]test-17

2013-01-10 Thread faisal....@elastica.co (JIRA)














































faisal ali
 created  JENKINS-16297


FATAL: Could not apply tag [project name]test-17















Issue Type:


Bug



Affects Versions:


current



Assignee:


faisal ali



Components:


github



Created:


10/Jan/13 11:08 AM



Description:


ok, so, before I explain my issue, I must mention that I am fairly new to jenkins and github, both.. The issue is, I have managed to attach jenkins Job with github project, but when I try to build the job on jenkins, I get the following error to my email:

Started by user anonymous
Building in workspace 
Checkout:workspace /  - hudson.remoting.LocalChannel@7932e6fd
Using strategy: Default
Fetching changes from 1 remote Git repository
Fetching upstream changes from g...@github.com:[user]/[project]-portal.git
Seen branch in repository origin/HEAD
Seen branch in repository origin/develop
Seen branch in repository origin/development_umair
Seen branch in repository origin/logs_redesign
Seen branch in repository origin/master
Seen branch in repository origin/overviewtabs
Commencing build of Revision b65f1a84d55a048accbcf7af2f56bb357fe73b64 (origin/overviewtabs)
Checking out Revision b65f1a84d55a048accbcf7af2f56bb357fe73b64 (origin/overviewtabs)
FATAL: Could not apply tag jenkins-[project name]_test-17
hudson.plugins.git.GitException: Could not apply tag [project name] test-17
at hudson.plugins.git.GitAPI.tag(GitAPI.java:829)
at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1270)
at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1231)
at hudson.FilePath.act(FilePath.java:852)
at hudson.FilePath.act(FilePath.java:825)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1231)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1325)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:682)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:587)
at hudson.model.Run.execute(Run.java:1543)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:236)
Caused by: hudson.plugins.git.GitException: Command "git tag a -f -m Jenkins Build #17 jenkins[project name]_test-17" returned status code 128:
stdout:
stderr:

	
	
		
		
			Please tell me who you are.
		
		
	
	



Run

  git config --global user.email "y...@example.com"
  git config --global user.name "Your Name"

to set your account's default identity.
Omit --global to set the identity only in this repository.

fatal: empty ident  [email]-KJ419AA-AB4-a6417l.(none)> not allowed

at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:897)
at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:858)
at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:868)
at hudson.plugins.git.GitAPI.tag(GitAPI.java:827)
... 13 more

Need detailed yet easy for a new be to configure type of help.. =)




Due Date:


10/Jan/13 12:00 AM




Environment:


ubuntu 12.04,




Project:


Jenkins



Labels:


jenkins
github,




Priority:


Critical



Reporter:


faisal ali

























This message is automatically generated by JIRA.
 

[JIRA] (JENKINS-16296) Sometimes commits that mix property changes and text changes do not cause project to be triggered

2013-01-10 Thread step...@eucodos.de (JIRA)














































Stephan Pauxberger
 commented on  JENKINS-16296


Sometimes commits that mix property changes and text changes do not cause project to be triggered















Actually, the changed tests does NOT reproduce this behaviour (nontheless the test were not complete).



























This message is automatically generated by JIRA.
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-16296) Sometimes commits that mix property changes and text changes do not cause project to be triggered

2013-01-10 Thread step...@eucodos.de (JIRA)














































Stephan Pauxberger
 created  JENKINS-16296


Sometimes commits that mix property changes and text changes do not cause project to be triggered















Issue Type:


Bug



Assignee:


Unassigned


Components:


subversion



Created:


10/Jan/13 9:49 AM



Description:


JENKINS-14685 does not cover all situations (i.e. there was a test-case missing).

Testcase test only combined adding of files and property changes, but not file modification and property changes.

I have added the missing test case (which now fails) and look for a fix.




Environment:


subversion-plugin 1.44




Project:


Jenkins



Priority:


Major



Reporter:


Stephan Pauxberger

























This message is automatically generated by JIRA.
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-14376) Rational Team Concert Plugin: NullPointerException when changes has been accepted but not yet delivered

2013-01-10 Thread iloncar.ml+jenk...@gmail.com (JIRA)














































Ivica Loncar
 commented on  JENKINS-14376


Rational Team Concert Plugin: NullPointerException when changes has been accepted but not yet delivered















There is a pull request on github that works for us:

https://github.com/jenkinsci/rtc-plugin/pull/6

Until deluan accepts pull request you can build your own version of 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-14550) "Checksum mismatch while updating" with Subversion Plugin 1.42

2013-01-10 Thread mai...@trilobit.net (JIRA)














































maik s
 commented on  JENKINS-14550


"Checksum mismatch while updating" with Subversion Plugin 1.42















After switching Subversion URL from http:// to svn:// Jenkins checks out a fresh workspace after checksum mismatch.



























This message is automatically generated by JIRA.
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-8334) maven-plugin insists on Surefire to run tests

2013-01-10 Thread ku...@gmx.de (JIRA)














































kutzi
 commented on  JENKINS-8334


maven-plugin insists on Surefire to run tests















I you like to test the pull request on a 'real' Jenkins environment - which would be great - here's a link to a build:
http://dl.dropbox.com/u/25863594/subversion.hpi



























This message is automatically generated by JIRA.
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-16295) [ERROR] BUILD ERROR - (Permission denied)

2013-01-10 Thread sergej.kl...@hermes-softlab.com (JIRA)














































Sergej Kleva
 commented on  JENKINS-16295


[ERROR] BUILD ERROR - (Permission denied)















To be more specific task = Jenkins 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-16295) [ERROR] BUILD ERROR - (Permission denied)

2013-01-10 Thread sergej.kl...@hermes-softlab.com (JIRA)














































Sergej Kleva
 started work on  JENKINS-16295


[ERROR] BUILD ERROR - (Permission denied)
















Change By:


Sergej Kleva
(10/Jan/13 8:36 AM)




Status:


Open
In Progress



























This message is automatically generated by JIRA.
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-16295) [ERROR] BUILD ERROR - (Permission denied)

2013-01-10 Thread sergej.kl...@hermes-softlab.com (JIRA)














































Sergej Kleva
 created  JENKINS-16295


[ERROR] BUILD ERROR - (Permission denied)















Issue Type:


Bug



Affects Versions:


current



Assignee:


Nicolas De Loof



Components:


build-flow



Created:


10/Jan/13 8:35 AM



Description:


Hi!

We are getting Permission Denied when executing task with Jenkins.

If i run task with ROOT user (directly from the command prompt) i am not getting errors:

mvn clean package -Ptomcat -DskipTests

[JENKINS] Archiving /var/lib/jenkins/jobs/chi-tester/workspace/chi.tester.core/pom.xml to /var/lib/jenkins/jobs/chi-tester/modules/com.hsl.chi$chi.tester.core/builds/2013-01-09_15-28-08/archive/com.hsl.chi/chi.tester.core/1.3.0-SNAPSHOT/chi.tester.core-1.3.0-SNAPSHOT.pom
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] /com/hsl/chi/tester/spring/g2s-MG2S_ECT061.xml (Permission denied)

I checked permission for that particular file:
rw-rr-. 1 jenkins jenkins  3453 Jan  7 14:27 g2s-MG2S_ECT061.xml

All previous directories are having the same permission they are owned by:
jenkins:jenkins

Here is the config.xml for that particular Jenkins job:



  
  
  false
  
  

  
https://svn-lj.hermes.si/repos/chi/src/sim/chi-tester/trunk
.
  







  
  true
  false
  false
  false
  
  false
  
com.hsl.chi
chi-tester
  
  clean package -Ptomcat -DskipTests
  true
  false
  false
  true
  false
  true
  false
  -1
  false
  false
  
  
  
  
  
  
  


Please can anyone assists?

Brgds




Environment:


JENKINS_HOME	/mnt/data/jenkins

executable-war	/usr/lib/jenkins/jenkins.war

file.encoding	UTF-8

file.encoding.pkg	sun.io

file.separator	/

guice.disable.misplaced.annotation.check	true

hudson.diyChunking	true

java.awt.graphicsenv	sun.awt.X11GraphicsEnvironment

java.awt.headless	true

java.awt.printerjob	sun.print.PSPrinterJob

java.class.path	/usr/lib/jenkins/jenkins.war

java.class.version	50.0

java.endorsed.dirs	/usr/java/jdk1.6.0_33/jre/lib/endorsed

java.ext.dirs	/usr/java/jdk1.6.0_33/jre/lib/ext:/usr/java/packages/lib/ext

java.home	/usr/java/jdk1.6.0_33/jre

java.io.tmpdir	/tmp

java.library.path	/usr/java/jdk1.6.0_33/jre/lib/amd64/server:/usr/java/jdk1.6.0_33/jre/lib/amd64:/usr/java/jdk1.6.0_33/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib

java.runtime.name	Java(TM) SE Runtime Environment

java.runtime.version	1.6.0_33-b04

java.specification.name	Java Platform API Specification

java.specification.vendor	Sun Microsystems Inc.

java.specification.version	1.6

java.vendor	Sun Microsystems Inc.

java.vendor.url	http://java.sun.com/

java.vendor.url.bug	http://java.sun.com/cgi-bin/bugreport.cgi

java.version	1.6.0_33

java.vm.info	mixed mode

java.vm.name	Java HotSpot(TM) 64-Bit Server VM

java.vm.specification.name	Java Virtual Machine Specification

java.vm.specification.vendor	Sun Microsystems Inc.

java.vm.specification.version	1.0

java.vm.vendor	Sun Microsystems Inc.

java.vm.version	20.8-b03

jna.platform.library.path	/usr/lib64:/lib64:/usr/lib:/lib

line.separator	

mail.smtp.sendpartial	true

mail.smtps.sendpartial	true

os.arch	amd64

os.name	Linux

os.version	2.6.32-279.11.1.el6.x86_64

path.separator	:

securerandom.source	file:/dev/./urandom

sun.arch.data.model	64

sun.boot.class.path	/usr/java/jdk1.6.0_33/jre/lib/resources.jar:/usr/java/jdk1.6.0_33/jre/lib/rt.jar:/usr/java/jdk1.6.0_33/jre/lib/sunrsasign.jar:/usr/java/jdk1.6.0_33/jre/lib/jsse.jar:/usr/java/jdk1.6.0_33/jre/lib/jce.jar:/usr/java/jdk1.6.0_33/jre/lib/charsets.jar:/usr/java/jdk1.6.0_33/jre/lib/modules/jdk.boot.jar:/usr/java/jdk1.6.0_33/jre/classes

sun.boot.library.path	/usr/java/jdk1.6.0_33/jre/lib/amd64

sun.cpu.endian	little

sun.cpu.isalist	

sun.io.unicode.encoding	UnicodeLittle

sun.java.command	/usr/lib/jenkins/jenkins.war --logfile=/var/log/jenkins/jenkins.log --we

[JIRA] (JENKINS-16294) windows managed batch looses arguments when used within testlink

2013-01-10 Thread angela.bauer....@rohde-schwarz.com (JIRA)














































Angela Bauer
 created  JENKINS-16294


windows managed batch looses arguments when used within testlink















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Attachments:


ManagedWindowsBug.doc



Components:


plugin



Created:


10/Jan/13 8:22 AM



Description:


"Execute managed windows batch" within  "Test Execution" within Testlink looses the defined arguments (both in "single build steps" and as well in "iterative test build steps".

The used windows batch file defines one argument, which is shown as "required arguments".
Clicking on "Define arguments" I can input an argument.
Clicking on "Save", then again on "Configure", to have a look on my Jenkins Job, this argument is lost.

Doing the same outside of Testlink, "Execute manage windows batch" works as it should, the arguments are kept.

I attach a printout with a very simple example, which I only used for testing purposes.




Environment:


Windows XP




Fix Versions:


current



Project:


Jenkins



Labels:


testlink
managed-windows-batch




Priority:


Major



Reporter:


Angela Bauer

























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