date:20140826















































K P
 commented on  JENKINS-24407


missing weather icons (randomly?)















Would be interesting to know whether the working weather icons are percentages evenly dividable by 20.
In my attached screenshot, the working icons are 81%, 80%, 21%, 60%, 100% respectively. Not in this screenshot, but we also have jobs with 66%, 75%, 51%, 68%, 23%, 64%, 44%, etc... working correctly.



























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







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

[JIRA] [analysis-collector] (JENKINS-24436) Bad URLs in view

2014-08-26 Thread adam.swiezow...@comarch.pl (JIRA)















































Adam S
 created  JENKINS-24436


Bad URLs in view















Issue Type:


Bug



Assignee:


Ulli Hafner



Components:


analysis-collector



Created:


26/Aug/14 9:17 AM



Description:


Links in FindBugs/PMD/ Duplicate Code/Checkstyle/Coverage column in all views are bad. 
For example link to cobertura is http://server/view/ViewName/view/ViewName/job/Jobname/cobertura , which leads to 404 page.
There's duplicated "view/ViewName" fragment in URL. Link should be: http://server/view/ViewName/job/Jobname/cobertura

I have jenkins 1.577, with plugins: 
analysis-collector	1.41
analysis-core	1.58
checkstyle	3.39
cobertura	1.9.5
crap4j	0.8
dry	2.40
findbugs	4.57
pmd	3.38
tasks	4.40
token-macro	1.10
warnings	4.41




Environment:


Tomcat 7, Linux




Project:


Jenkins



Priority:


Minor



Reporter:


Adam S

























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







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

[JIRA] [email-ext] (JENKINS-24395) Fatal error with coming Jenkins ver. 1.577

2014-08-26 Thread theta...@java.net (JIRA)















































thetaphi
 commented on  JENKINS-24395


Fatal error with coming Jenkins ver. 1.577















Hi,
I tried the latest trunk build, seems to work. As this was caused by using a deprecated method already replaced by a newer one in the LTS release, I see no problem in releasing a new version based on Jenkins LTS.

Thanks Jesse!
Uwe



























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







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

[JIRA] [svn-workspace-cleaner] (JENKINS-24432) SVN modules in sub directories are not removed by SVN Workspace Cleaner















































David Pärsson
 commented on  JENKINS-24432


SVN modules in sub directories are not removed by SVN Workspace Cleaner















Thank you for reporting.

To me this was a known bug/limitation. This plugin is not currently under that active development, but we're happy to accept pull requests. Please let me know if you're interested, and need any pointers on how to do it.



























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







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

[JIRA] [svn-workspace-cleaner] (JENKINS-24432) SVN modules in sub directories are not removed by SVN Workspace Cleaner













































  
David Pärsson
 edited a comment on  JENKINS-24432


SVN modules in sub directories are not removed by SVN Workspace Cleaner
















Thank you for reporting. To me this was a known bug/limitation.

This plugin is not currently under that active development, but we're happy to accept pull requests. Please let me know if you're interested, and need any pointers on how to do it.



























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







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

[JIRA] [core] (JENKINS-23921) new s layout doesn't work with IE8

2014-08-26 Thread stephan.her...@nuance.com (JIRA)















































Stephan Herter
 commented on  JENKINS-23921


new s layout doesn't work with IE8 















I tried with "IE7Standard" document mode: The message is not shown, but the page is not displayed correctly.
I suppose that the message is shown in the wrong 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







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

[JIRA] [core] (JENKINS-23921) new s layout doesn't work with IE8

2014-08-26 Thread tom.fenne...@gmail.com (JIRA)















































Tom FENNELLY
 commented on  JENKINS-23921


new s layout doesn't work with IE8 















@Stephen Herter please attach screenshots



























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







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

[JIRA] [conditional-buildstep] (JENKINS-18629) Jenkins fails to save configuration when using Invoke Gradle script in Conditional Step (single).

2014-08-26 Thread d...@fortysix.ch (JIRA)















































Dominik Bartholdi
 commented on  JENKINS-18629


Jenkins fails to save configuration when using Invoke Gradle script in Conditional Step (single).















 Nicolas De Loof how come this can now be marked as fixed, as on other places we communicated this will not be fixed, see JENKINS-20262



























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







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

[JIRA] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs















































Paul Allen
 commented on  JENKINS-24028


using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs















It may be a long shot, but is one of your axis names using a reserved name e.g. 'label'?

(I updated the docs; 'label', 'change', 'status', 'review', 'pass', and 'fail')  Using any of these as axis names will have a strange effect.



























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







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

[JIRA] [core] (JENKINS-24426) Jenkins version 1.575 killing processes at end of shell script

2014-08-26 Thread reinhard.kar...@unify.com (JIRA)















































Reinhard Karbas
 commented on  JENKINS-24426


Jenkins version 1.575 killing processes at end of shell script















Thanks for the info
One more question:

Should I use this switch for Jenkins on the master job or should it be a parameter on the slave machines where I need to disable that behavior?



























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







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

[JIRA] [job-dsl-plugin] (JENKINS-24420) Add job-dsl-plugin support for delivery-pipeline-plugin

2014-08-26 Thread pat...@diabol.se (JIRA)















































Patrik Boström
 commented on  JENKINS-24420


Add job-dsl-plugin support for delivery-pipeline-plugin















Great! Let me know if you need any help or support.



























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







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

[JIRA] [envinject] (JENKINS-24437) EnvInject - ability to execute the script first, then inject parameters via file

2014-08-26 Thread yaniv.k...@emc.com (JIRA)















































Yaniv Kaul
 created  JENKINS-24437


EnvInject - ability to execute the script first, then inject parameters via file















Issue Type:


New Feature



Assignee:


Gregory Boissinot



Components:


envinject



Created:


26/Aug/14 10:22 AM



Description:


Today, the parameters are read from file and injected, then the 'script' section runs. In my case, I'd like the script to create the file, and then the parameters will be injected from it. I can see why the other way around also makes sense, but I'd be happy if we can change the order. That would be most beneficial, as it means the parameters are injected before the build part and can be used elsewhere (For example, when setting build name!)




Project:


Jenkins



Labels:


envinject




Priority:


Minor



Reporter:


Yaniv Kaul

























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







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

[JIRA] [core] (JENKINS-24316) Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL















































Denis Shvedchenko
 commented on  JENKINS-24316


Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL















Hi, I've found that some plugin ( config-file-provider ) , starts suffering from similar trouble ( rendering icons by \jenkins\core\src\main\resources\lib\layout\layout.jelly in main-panel-content ). if you can classify it for jenkins issue , or plugin issue, please, it would be nice



























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







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

[JIRA] [svn-workspace-cleaner] (JENKINS-24432) SVN modules in sub directories are not removed by SVN Workspace Cleaner













































  
David Pärsson
 edited a comment on  JENKINS-24432


SVN modules in sub directories are not removed by SVN Workspace Cleaner
















Thank you for reporting.

This plugin is not currently under that active development, but we're happy to accept pull requests. Please let me know if you're interested, and need any pointers on how to do it.



























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







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

[JIRA] [svn-workspace-cleaner] (JENKINS-24432) SVN modules in sub directories are not removed by SVN Workspace Cleaner













































  
David Pärsson
 edited a comment on  JENKINS-24432


SVN modules in sub directories are not removed by SVN Workspace Cleaner
















Thank you for reporting.

This plugin is not currently under that active development, but we're happy to accept pull requests. Please let me know if you're interestedand in need of any pointers on how to do it.



























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







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

[JIRA] [p4] (JENKINS-24101) Poll Watching Label Continually Triggering















































Paul Allen
 commented on  JENKINS-24101


Poll Watching Label Continually Triggering















JENKINS-24202 is now closed. Please can you verify if this job is now resolved?



























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







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

[JIRA] [postbuild-task] (JENKINS-24418) Getting NullPointer exception while executing post build steps (after successful build)















































Daniel Beck
 commented on  JENKINS-24418


Getting NullPointer exception while executing post build steps (after successful build)















sean head: Please file a new issue. Provide as much information as you can, see https://wiki.jenkins-ci.org/display/JENKINS/Issue+Tracking#IssueTracking-Whattoputinthedescriptionofanissuereport%3F



























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







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

[JIRA] [script-security] (JENKINS-24399) Modifying files in class directories can bypass approval in script-security (or class directories are accepted as classpaths)















































Daniel Beck
 commented on  JENKINS-24399


Modifying files in class directories can bypass approval in script-security (or class directories are accepted as classpaths)















Isn't this a simple case of the admin being a moron and deserving everything that follows? Like setting the setuid flag on a root owned file in Linux that is world-writable?



























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







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

[JIRA] [core] (JENKINS-24426) Jenkins version 1.575 killing processes at end of shell script















































Daniel Beck
 commented on  JENKINS-24426


Jenkins version 1.575 killing processes at end of shell script















Should be the master's java call (I'm not completely sure, but almost  ). Verify you did it correctly via /systemInfo URL that shows all System properties.

Note that a less all-encompassing option is to set the BUILD_ID environment variable in the shell script so sshd doesn't inherit the 'real' one, see last section.



























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







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

[JIRA] [subversion] (JENKINS-24438) Jenkins crashes regularly using Subversion Plugin 2.4.1

2014-08-26 Thread andy.sm...@mkodo.com (JIRA)

Andy Smith
created JENKINS-24438

Jenkins crashes regularly using Subversion Plugin 2.4.1

Issue Type:

Bug

Affects Versions:

current

Assignee:

Unassigned

Attachments:

hs_err_pid12459.log

Components:

subversion

Created:

26/Aug/14 11:40 AM

Description:

Jenkins seems to crash the JVM when using the Subversion plugin. I am using 2.4.1 of that plugin. The problem manifests itself when we use the drop down list to display the SVN tags in a parametrized build.

To get around the problem, I downgraded to pre 2.x versions of the SVN plugin. However, other plugins that I need to use seem to want to upgrade our Jenkins installation to the latest SVN plugin, with disastrous consequences.

I enclose a JVM dump.

Environment:

Linux megatron.mkodo.net 2.6.32-431.17.1.el6.x86_64 #1 SMP Fri Apr 11 17:27:00 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux

Project:

Jenkins

Priority:

Critical

Reporter:

Andy Smith

[JIRA] [core] (JENKINS-24316) Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL















































Daniel Beck
 commented on  JENKINS-24316


Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL















Denis Shvedchenko: If this occurs in 1.576, we don't care since there was a fix since. If it occurs in 1.577, please file a new issue against core and the plugin it occurs in as components, we'll sort it out. Make sure to use the label "user-experience".



























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







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

[JIRA] [svn-workspace-cleaner] (JENKINS-24432) SVN modules in sub directories are not removed by SVN Workspace Cleaner















































David Pärsson
 updated  JENKINS-24432


SVN modules in sub directories are not removed by SVN Workspace Cleaner
















Change By:


David Pärsson
(26/Aug/14 11:44 AM)




Issue Type:


Bug
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







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

[JIRA] [build-user-vars] (JENKINS-24439) Release new version to fix NPE

2014-08-26 Thread as.m...@gmail.com (JIRA)















































Andreas Schöneck
 created  JENKINS-24439


Release new version to fix NPE















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


build-user-vars



Created:


26/Aug/14 11:49 AM



Description:


We encounter the NPE that has already been fixed on master but not yet released:

https://github.com/jenkinsci/build-user-vars-plugin/commit/9a7ea4a8504c1871635c59065d8647df479a





Project:


Jenkins



Priority:


Critical



Reporter:


Andreas Schöneck

























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







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

[JIRA] [email-ext] (JENKINS-24395) Fatal error with coming Jenkins ver. 1.577

2014-08-26 Thread theta...@java.net (JIRA)















































thetaphi
 commented on  JENKINS-24395


Fatal error with coming Jenkins ver. 1.577















FYI: this is the commit: https://github.com/jenkinsci/email-ext-plugin/commit/26b1e1b8eaa1c1a11948268564de9970e40a9259



























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







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

[JIRA] [core] (JENKINS-24407) missing weather icons (randomly?)















































Daniel Beck
 commented on  JENKINS-24407


missing weather icons (randomly?)















I have this very bad feeling that any non-default weather report icons are no longer supported by core (e.g. various test or code coverage report plugins, or Cloudbees Folders Plus).

When you mouseover over the weather icons, a tooltip/popup should show up showing 1 or more "weather reports" for specific things (like X out of 5 builds failed, or percentage of tests failed, ...). Check to see which weather report is the worst for every weather icon.

There should be a common thread to the icons that work, and the icons that don't. Example: "the icon is shown when the worst report is "X out of 5 builds failed", and it isn't shown when the worst is "test code coverage".



























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







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

[JIRA] [svn-workspace-cleaner] (JENKINS-24432) SVN modules in sub directories are not removed by SVN Workspace Cleaner















































David Pärsson
 commented on  JENKINS-24432


SVN modules in sub directories are not removed by SVN Workspace Cleaner















I changed my mind. A release with version 1.1 is published and should hopefully appear soon. It contains support for this 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







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

[JIRA] [build-user-vars] (JENKINS-24439) Release new version to fix NPE

2014-08-26 Thread as.m...@gmail.com (JIRA)















































Andreas Schöneck
 updated  JENKINS-24439


Release new version to fix NPE
















Change By:


Andreas Schöneck
(26/Aug/14 11:57 AM)




Description:


We encounter the NPE that has already been fixed on master but not yet released:https://github.com/jenkinsci/build-user-vars-plugin/commit/
223500fbcb2da959efecc894bde3d0cd83417414Might also be related:https://github.com/jenkinsci/build-user-vars-plugin/commit/
9a7ea4a8504c1871635c59065d8647df479a



























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







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

[JIRA] [svn-workspace-cleaner] (JENKINS-24432) SVN modules in sub directories are not removed by SVN Workspace Cleaner
















































David Pärsson
 resolved  JENKINS-24432 as Fixed


SVN modules in sub directories are not removed by SVN Workspace Cleaner
















Change By:


David Pärsson
(26/Aug/14 11:57 AM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [svn-workspace-cleaner] (JENKINS-19100) Unable to wipe out workspace with file named: knäpplpåärtillvåraförlor.txt















































David Pärsson
 commented on  JENKINS-19100


Unable to wipe out workspace with file named: knäpplpåärtillvåraförlor.txt















Are you really sure that this is related to the svn-workspace-cleaner plugin? P4 workspaces are not supported.



























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







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

[JIRA] [core] (JENKINS-19100) Unable to wipe out workspace with file named: knäpplpåärtillvåraförlor.txt















































David Pärsson
 updated  JENKINS-19100


Unable to wipe out workspace with file named: knäpplpåärtillvåraförlor.txt
















Change By:


David Pärsson
(26/Aug/14 12:00 PM)




Component/s:


core





Component/s:


svn-workspace-cleaner



























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







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

[JIRA] [svn-release-mgr] (JENKINS-20202) Svn plugin.Exclude option does not work.excluded path are not excluded from checkout















































David Pärsson
 updated  JENKINS-20202


Svn plugin.Exclude option does not work.excluded path are not excluded from checkout
















Change By:


David Pärsson
(26/Aug/14 12:02 PM)




Component/s:


svn-workspace-cleaner



























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







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

[JIRA] [core] (JENKINS-23330) Spaces in project names are not encoded on IDs

2014-08-26 Thread domi.br...@free.fr (JIRA)















































Dominique Brice
 commented on  JENKINS-23330


Spaces in project names are not encoded on  IDs















I got it working, i.e. I can navigate to a job from a job list page using my keyboard (start with g-j then use arrow). However my setup is quite simple: Jenkins 1.578-SNAPSHOT and Keyboard Shortcuts Plugin 1.2, nothing else.
Is it not working for 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







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

[JIRA] [jacoco] (JENKINS-23708) Unable to view JaCoCo report and history graph

2014-08-26 Thread nn...@neulinger.org (JIRA)















































Nathan Neulinger
 commented on  JENKINS-23708


Unable to view JaCoCo report and history graph















We are seeing this symptom also. Haven't tried the fix (not set up to build jenkins module code) though. Tobias, would you share your .jpi file?



























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







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

[JIRA] [core] (JENKINS-24440) Jenkins cannot delete files owned by root in folders he own

2014-08-26 Thread pdup...@teads.tv (JIRA)

Philippe Dupont
created JENKINS-24440

Jenkins cannot delete files owned by root in folders he own

Issue Type:

Bug

Assignee:

Unassigned

Components:

core

Created:

26/Aug/14 12:39 PM

Description:

We want to be able to wipe workspaces containing files created via Docker containers (and thus owned by root). In a shell, as jenkins, we can delete root-owned files/folders as long as they are within jenkins-owned directories. But this function ( https://github.com/jenkinsci/jenkins/blob/6c2fffb/core/src/main/java/hudson/Util.java#L299 ) fails in that case.

Perhaps, it's due to a windowsOS java limitation which cannot delete a non-empty directory?

Could it be possible to create a special implementation for unix, that allows deletion of non-empty directories and thus supports the use-case mentioned above?

Project:

Jenkins

Labels:

docker

Priority:

Minor

Reporter:

Philippe Dupont

[JIRA] [core] (JENKINS-24407) missing weather icons (randomly?)















































K P
 updated  JENKINS-24407


missing weather icons (randomly?)
















Cobertura has worst percentage; icon is missing





Change By:


K P
(26/Aug/14 12:41 PM)




Attachment:


cobertura_worst_missing.png



























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







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

[JIRA] [core] (JENKINS-24407) missing weather icons (randomly?)















































K P
 commented on  JENKINS-24407


missing weather icons (randomly?)















Indeed, when looking at the tooltip, only Cobertura status weather icons (from the Cobertura Plugin) seem missing.

In the cases where the icon is missing, Cobertura is indeed the one with the worst percentage (and the Cobertura line is missing its icon).

However, there are jobs where Cobertura has the worst percentage, and its icon is not missing; in which case the overall icon isn't missing either.

(see screenshots)



























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







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

[JIRA] [websphere-deployer] (JENKINS-21641) The system cannot create a SOAP connector to connect to remote host using websphere deployer plugin

2014-08-26 Thread gregpeter...@gmail.com (JIRA)















































Greg Peters
 commented on  JENKINS-21641


The system cannot create a SOAP connector to connect to remote host using websphere deployer plugin 















@mohamed amin mengat,

1) Navigate to the websphere admin console with your browser. You will likely get a permissions issue that the certificate is not trusted by your browser.
2) This permissions issue means the default certificate by websphere is a "self signed" certificate.

3) You must either import WebSphere's "Self Signed" cert by exporting it from the browser and importing it into the JVM that jenkins is using
or
4) Provide a valid cert for websphere



























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







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

[JIRA] [core] (JENKINS-24407) missing weather icons (randomly?)













































  
K P
 edited a comment on  JENKINS-24407


missing weather icons (randomly?)
















screenshots added



























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







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

[JIRA] [core] (JENKINS-24407) missing weather icons (randomly?)















































K P
 updated  JENKINS-24407


missing weather icons (randomly?)
















Change By:


K P
(26/Aug/14 12:43 PM)




Attachment:


cobertura_notworst_missing.png





Attachment:


cobertura_worst_notmissing.png



























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







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

[JIRA] [websphere-deployer] (JENKINS-21641) The system cannot create a SOAP connector to connect to remote host using websphere deployer plugin

2014-08-26 Thread gregpeter...@gmail.com (JIRA)















































Greg Peters
 updated  JENKINS-21641


The system cannot create a SOAP connector to connect to remote host using websphere deployer plugin 
















Change By:


Greg Peters
(26/Aug/14 12:44 PM)




Status:


Reopened
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







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

[JIRA] [websphere-deployer] (JENKINS-21641) The system cannot create a SOAP connector to connect to remote host using websphere deployer plugin

2014-08-26 Thread gregpeter...@gmail.com (JIRA)
















































Greg Peters
 closed  JENKINS-21641 as Not A Defect


The system cannot create a SOAP connector to connect to remote host using websphere deployer plugin 
















Change By:


Greg Peters
(26/Aug/14 12:44 PM)




Status:


Open
Closed





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







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

[JIRA] [p4] (JENKINS-24202) Pin Build at Label Does not Sync at the CL of the Label
















































Paul Allen
 closed  JENKINS-24202 as Fixed


Pin Build at Label Does not Sync at the CL of the Label
















1.0.13





Change By:


Paul Allen
(26/Aug/14 12:46 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







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

[JIRA] [config-file-provider] (JENKINS-24441) After jenkins 1.576 ( and in 1.577 version did not fix it ) Config File Management plugin in main-panel-content are has ivalid icon path















































Denis Shvedchenko
 created  JENKINS-24441


After jenkins 1.576 ( and in 1.577 version did not fix it ) Config File Management plugin in main-panel-content are has ivalid icon path















Issue Type:


Bug



Affects Versions:


current



Assignee:


Dominik Bartholdi



Components:


config-file-provider, core



Created:


26/Aug/14 12:47 PM



Description:



  
  
	Config File Management
 You can edit or remove your configuration files

i think it is related to changes caused JENKINS-24316




Project:


Jenkins



Labels:


user-experience




Priority:


Minor



Reporter:


Denis Shvedchenko

























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







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

[JIRA] [pretested-integration] (JENKINS-24442) Use author name and email (our case 11861)

2014-08-26 Thread andrius...@gmail.com (JIRA)















































Andrius Ordojan
 created  JENKINS-24442


Use author name and email (our case 11861)















Issue Type:


Improvement



Assignee:


Praqma Support



Components:


pretested-integration



Created:


26/Aug/14 12:49 PM



Description:


When squashing commit(s) use the name and email information of the
author from the commit at the tip of the branch to be squashed.
Still use the system configuration for the comitter information.

https://github.com/jenkinsci/pretested-integration-plugin/pull/1




Project:


Jenkins



Priority:


Major



Reporter:


Andrius Ordojan

























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







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

[JIRA] [config-file-provider] (JENKINS-24441) in jenkins (1.577 ) Config File Management plugin in main-panel-content are has ivalid icon path ( double slash before plugin path )















































Denis Shvedchenko
 updated  JENKINS-24441


in jenkins (1.577 ) Config File Management plugin in main-panel-content are has ivalid icon path ( double slash before plugin path )
















Change By:


Denis Shvedchenko
(26/Aug/14 12:49 PM)




Summary:


After
in
 jenkins
 1.576
 (
 and in
 1.577
 version did not fix it
 ) Config File Management plugin in main-panel-content are has ivalid icon path
 ( double slash before plugin path )



























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







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

[JIRA] [config-file-provider] (JENKINS-24441) After jenkins 1.576 ( and in 1.577 version did not fix it ) Config File Management plugin in main-panel-content are has ivalid icon path















































Denis Shvedchenko
 updated  JENKINS-24441


After jenkins 1.576 ( and in 1.577 version did not fix it ) Config File Management plugin in main-panel-content are has ivalid icon path
















Change By:


Denis Shvedchenko
(26/Aug/14 12:48 PM)




Description:


main panel content rendered in such way.may instance is running 1.577 and does not have suffix
   	Config File Management You can edit or remove your configuration filesi think it is related to changes caused JENKINS-24316



























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







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

[JIRA] [p4] (JENKINS-24427) P4 Trust error show up when integrate Parameterize Trigger Plugin















































Paul Allen
 commented on  JENKINS-24427


P4 Trust error show up when integrate Parameterize Trigger Plugin















Perhaps auto accept is the way to go;  I wanted to actively encourage the user to verify the trust, but once established it should not change.  

With a shared home directory each client might access the trust file; could cause a threading issue. I'll need to look at this in more depth.



























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







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

[JIRA] [pretested-integration] (JENKINS-24443) Use original commit object for author and commit message info (our case 11862)

2014-08-26 Thread andrius...@gmail.com (JIRA)















































Andrius Ordojan
 created  JENKINS-24443


Use original commit object for author and commit message info (our case 11862)















Issue Type:


Improvement



Assignee:


Praqma Support



Components:


pretested-integration



Created:


26/Aug/14 12:53 PM



Description:


When squashing commit(s) use the name and email information of the
author from the commit at the tip of the branch to be squashed.
Still use the system configuration for the comitter information.

https://github.com/jenkinsci/pretested-integration-plugin/pull/2




Project:


Jenkins



Priority:


Major



Reporter:


Andrius Ordojan

























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







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

[JIRA] [pretested-integration] (JENKINS-24442) Use author name and email (our case 11861)

2014-08-26 Thread andrius...@gmail.com (JIRA)
















































Andrius Ordojan
 closed  JENKINS-24442 as Fixed


Use author name and email (our case 11861)
















Change By:


Andrius Ordojan
(26/Aug/14 12:56 PM)




Status:


Open
Closed





Resolution:


Fixed



























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







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

[JIRA] [ws-cleanup] (JENKINS-23693) Cannot delete workspace

2014-08-26 Thread scm_issue_l...@java.net (JIRA)















































SCM/JIRA link daemon
 commented on  JENKINS-23693


Cannot delete workspace















Code changed in jenkins
User: Yoann Dubreuil
Path:
 src/main/java/hudson/plugins/ws_cleanup/Cleanup.java
http://jenkins-ci.org/commit/ws-cleanup-plugin/a8067fbb2ca46ccfbefc65714730d62267cfb7e9
Log:
  [FIX JENKINS-23693]: Checks if delete command is null





























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







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

[JIRA] [core] (JENKINS-24444) Browser Compatibility Matrix

2014-08-26 Thread tom.fenne...@gmail.com (JIRA)
















































Tom FENNELLY
 resolved  JENKINS-2 as Fixed


Browser Compatibility Matrix
















Initial draft at https://wiki.jenkins-ci.org/display/JENKINS/Browser+Compatibility+Matrix





Change By:


Tom FENNELLY
(26/Aug/14 12:58 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [core] (JENKINS-24444) Browser Compatibility Matrix

2014-08-26 Thread tom.fenne...@gmail.com (JIRA)















































Tom FENNELLY
 created  JENKINS-2


Browser Compatibility Matrix















Issue Type:


Task



Assignee:


Tom FENNELLY



Components:


core



Created:


26/Aug/14 12:57 PM



Description:


Following on from https://groups.google.com/forum/?hl=en#!searchin/jenkinsci-dev/matrix/jenkinsci-dev/XxPqJDCrf6M/TZfqYHV9ehwJ




Project:


Jenkins



Labels:


user-experience




Priority:


Major



Reporter:


Tom FENNELLY

























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







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

[JIRA] [gerrit] (JENKINS-24445) Retriggering builds via the "Manual Trigger" feature of the Gerrit Trigger Plugin causes wrong verification

2014-08-26 Thread martin.h.schroe...@intel.com (JIRA)

Martin Schröder
created JENKINS-24445

Retriggering builds via the "Manual Trigger" feature of the Gerrit Trigger Plugin causes wrong verification

Issue Type:

Bug

Affects Versions:

current

Assignee:

rsandell

Attachments:

jobs.zip

Components:

gerrit, gerrit-trigger

Created:

26/Aug/14 12:59 PM

Description:

There is a serious issue with the Gerrit trigger plugin and its "retrigger" functionality.

This issue causes the plugin to get confused about how many and which builds it started for a particular changeset/patchset combination, and decide to post the Verification or Code Review update even if not all test have passed yet.

This behaviour leads to inconsistent verification results in Gerrit and can be easily replicated as follows:

1.) Start a blank, vanilla Jenkins server of an arbitrary version on your local host (the jobs below assume that a BASH shell is available).

2.) Install the gerrit-trigger plugin (arbitrary version, as all are affected)

3.) Increase the executor count of the "master" node to at least 6.

4.) Restart the server and create a connection to a Gerrit service.

5.) Shut down the server and extract the two jobs (Test_1 and Test_2) into the "jobs" directory of the Jenkins server.

5.a ) Test_1 will always fail, Test_2 will always succeed. Both will create a lock-file named "LOCKFILE-${JOB_NAME}-${BUILD_NUMBER}" in "${JENKINS_HOME}/workspace/Central" and wait for it to be deleted, before succeeding or failing.

6.) (Optional) Alter the Test_1 and Test_2 parameters to listen to a specific repository. By default repo and branch are set to "**".

After this set-up is done, upload a patchset to the Gerrit service in question.

This will cause a build of "Test_1" and "Test_2" to be started. Now, while they are running (they are wait until you delete their lock-file), go into the "manual trigger" interface:
http://[jenkins]/gerrit_manual_trigger/?

Search for the changeset and issue a retrigger. This will cause two additional builds to spawn, one for "Test_1" and one for "Test_2".

Now that 4 tests are running, the correct behaviour of the Gerrit trigger plugin is to ignore the first two runs that have been started by the "Patchset Created" event.

Instead, it should wait until BOTH of the retriggered builds have finished and then upload a "Verified -1" message to Gerrit.

To test this, first delete the two original lock files:

${JENKINS_HOME}/workspace/Central/LOCKFILE-Test_1-1
${JENKINS_HOME}/workspace/Central/LOCKFILE-Test_2-1

This tests the first half of the problem. This works fine. After both have finished, the Gerrit Trigger plugin will still wait for the others to finish.

Now, to expose the bug, ONLY delete the lockfile for the retriggered TEST_2 job:
${JENKINS_HOME}/workspace/Central/LOCKFILE-Test_2-2

This will let Test_2 finish successfully (as Test_2 always succeeds). The bug that happens now is, that the trigger plugin uploads a "Verified +1" message, DESPITE "Test_1 #2" not yet being finished.

If you then also let "Test_1" finish, it uploads yet another verification, this time "Verified -1".

This behaviour is absolutely wrong, as it sends a verification state without waiting for all jobs to complete, thus leading to inconsistent results in Gerrit.

Here's an excerpt of how this behaviour looks like in Gerrit:

##
Jenkins
Patch Set 1: -Verified
Build Started Test_2/1/ (1/2)
---
Jenkins
Patch Set 1:
Build Started Test_1/1/ (2/2)
---
Jenkins
Patch Set 1:
Build Started Test_2/2/ (2/2)
---
Jenkins
Patch Set 1:
Build Started Test_1/2/ (2/2)
---
Jenkins
Patch Set 1: Verified+1
Build Successful
Test_2/2/ : SUCCESS
---
Je

[JIRA] [ws-cleanup] (JENKINS-23693) Cannot delete workspace

2014-08-26 Thread vjura...@java.net (JIRA)
















































vjuranek
 resolved  JENKINS-23693 as Fixed


Cannot delete workspace
















Hopefully fixed by PR #18, fixed is contained in 0.23 released right now. If the issue is still present, please reopen.





Change By:


vjuranek
(26/Aug/14 1:05 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [core] (JENKINS-24440) Jenkins cannot delete root-owned files/folders in jenkins-owned directories

2014-08-26 Thread pdup...@teads.tv (JIRA)















































Philippe Dupont
 updated  JENKINS-24440


Jenkins cannot delete root-owned files/folders in jenkins-owned directories
















Change By:


Philippe Dupont
(26/Aug/14 1:16 PM)




Summary:


Jenkins cannot delete
 files owned by
 root
 in
-owned files/
 folders
 he own
 in jenkins-owned directories



























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







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

[JIRA] [ghprb] (JENKINS-24446) When using triggerOnly - only pull requests from whitelisted members are triggered

2014-08-26 Thread memp...@machzwo.de (JIRA)

Mem phisch
created JENKINS-24446

When using triggerOnly - only pull requests from whitelisted members are triggered

Issue Type:

Bug

Assignee:

Honza Brázdil

Components:

ghprb

Created:

26/Aug/14 1:21 PM

Description:

As the Topic says.

1. We are using the trigger only feature.
2. All members of the xbmc foundation are whitelisted for triggeronly
3. When a member now triggers by commenting the triggerphrase on a PR it only works when the PR was done by a whitelisted/team member

This line of code is the problem:

https://github.com/jenkinsci/ghprb-plugin/blob/master/src/main/java/org/jenkinsci/plugins/ghprb/GhprbPullRequest.java#L290

It checks the "accepted" flag which is only true if the author of the PR was whitelisted. It is set to true here:

https://github.com/jenkinsci/ghprb-plugin/blob/master/src/main/java/org/jenkinsci/plugins/ghprb/GhprbPullRequest.java#L77

IMO the "accepted" flag shouldn't be checked at all in the triggeronly scenario. Its enough that the commenter is whitelisted.

Environment:

Jenkins 1.571

GHPRB 1.14-3

Project:

Jenkins

Priority:

Major

Reporter:

Mem phisch

[JIRA] [scm-sync-configuration] (JENKINS-15128) Renaming job doesn't work with Git

2014-08-26 Thread bpodgur...@gmail.com (JIRA)















































Benjamin Podgursky
 commented on  JENKINS-15128


Renaming job doesn't work with Git















I'm testing out the fix but still seeing an issue.  It's throwing an error on:

[INFO] Executing: /bin/sh -c cd /var/lib/jenkins/scm-sync-configuration/checkoutConfiguration/jobs && git rm 
[INFO] Working directory: /var/lib/jenkins/scm-sync-configuration/checkoutConfiguration/jobs
Aug 26, 2014 7:03:49 AM hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy
SEVERE: [deleteHierarchy] Problem during remove : The git command failed.


when I run the command manually, I get:

fatal: not removing 'jobs/' recursively without -r

any thoughts?






























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







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

[JIRA] [build-pipeline] (JENKINS-24423) Just created (but not yet saved) pipeline breaks Jenkins

2014-08-26 Thread dsero...@gmail.com (JIRA)















































dserodio
 commented on  JENKINS-24423


Just created (but not yet saved) pipeline breaks Jenkins















I'm not sure it's dupe. JENKINS-23363 is caused by a NullPointerException in line 402 and this one is caused by a NumberFormatException in line 400. Also, the "how to reproduce" is different.

I was planning on fixing this one by setting a default value for noOfDisplayedBuilds in BuildPipelineView, what do you think?



























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







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

[JIRA] [publish-over-cifs] (JENKINS-23175) Add support for Credentials plugin supplied credentials

2014-08-26 Thread twolf...@java.net (JIRA)















































twolfart
 commented on  JENKINS-23175


Add support for Credentials plugin supplied credentials















Adding that feature would be very helpful.



























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







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

[JIRA] [ghprb] (JENKINS-24447) latest ghprb plugin still broken for github enterprise users athough JENKINS-24145 marked as resolved

2014-08-26 Thread wi...@eppendorf.de (JIRA)















































Michael Wild
 created  JENKINS-24447


latest ghprb plugin still broken for github enterprise users athough JENKINS-24145 marked as resolved















Issue Type:


Bug



Assignee:


Honza Brázdil



Components:


ghprb



Created:


26/Aug/14 2:16 PM



Description:


Although there was a fix for this bug from version 1.14-4 to 1.14-5 the bug described in JENKINS-24145 still occurs on my system:

Error while serving http://(myJenkins)/ghprbhook/
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
...
at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
...
at org.kohsuke.stapler.Stapler.service(Stapler.java:225)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
...
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
...
at java.lang.Thread.run(Thread.java:722)
Caused by: java.lang.Error: java.io.FileNotFoundException: http://(myGitHubEnterprise)/api/v3/api/v3/repos/(myOrg)/(myProject)/pulls/4/commits
at org.kohsuke.github.Requester$1.fetch(Requester.java:304)
at org.kohsuke.github.Requester$1.hasNext(Requester.java:271)
at org.kohsuke.github.PagedIterator.fetch(PagedIterator.java:44)
at org.kohsuke.github.PagedIterator.hasNext(PagedIterator.java:32)
at org.jenkinsci.plugins.ghprb.GhprbPullRequest.tryBuild(GhprbPullRequest.java:220)
at org.jenkinsci.plugins.ghprb.GhprbPullRequest.check(GhprbPullRequest.java:174)
at org.jenkinsci.plugins.ghprb.GhprbRepository.onIssueCommentHook(GhprbRepository.java:214)
at org.jenkinsci.plugins.ghprb.GhprbRootAction.doIndex(GhprbRootAction.java:58)
... 73 more
Caused by: java.io.FileNotFoundException: http://(myGitHubEnterprise)/api/v3/api/v3/repos/(myOrg)/(myProject)/pulls/4/commits
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1623)
at org.kohsuke.github.Requester.parse(Requester.java:359)
at org.kohsuke.github.Requester.access$300(Requester.java:59)
at org.kohsuke.github.Requester$1.fetch(Requester.java:295)
... 80 more




Project:


Jenkins



Priority:


Major



Reporter:


Michael Wild

























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







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

[JIRA] [build-with-parameters] (JENKINS-24008) Jobs stuck while waiting for an executor (and executors are available)

2014-08-26 Thread zf.0...@gmail.com (JIRA)















































tigren zhang
 commented on  JENKINS-24008


Jobs stuck while waiting for an executor (and executors are available)















Dear All

Our Jenkins has the exactly same issue, is there any solution or workaround?

We don't have "Build With Parameters Plugin" installed so I guess it's not caused by that



























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







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

[JIRA] [p4] (JENKINS-24427) P4 Trust error show up when integrate Parameterize Trigger Plugin

2014-08-26 Thread dant...@gmail.com (JIRA)















































dan tran
 commented on  JENKINS-24427


P4 Trust error show up when integrate Parameterize Trigger Plugin















not sure why the trust file get updated for every build and cause this concurrency issue



























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







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

[JIRA] [p4] (JENKINS-24427) P4 Trust error show up when integrate Parameterize Trigger Plugin

2014-08-26 Thread dant...@gmail.com (JIRA)















































dan tran
 updated  JENKINS-24427


P4 Trust error show up when integrate Parameterize Trigger Plugin
















Change By:


dan tran
(26/Aug/14 2:36 PM)




Description:


I have a start job on Maser Linux which dump p4 changelist number into a properties file, and use Parameterize Trigger Plugin to spin other slaves Unix slaves takes turn to pop this errorStarted by upstream project "authc-java-snapshot" build number 110originally caused by: Started by user trand8[EnvInject] - Loading node environment variables.Building on master in workspace /data/trand8/.jenkins/jobs/authc-linux-x64-snapshot/workspaceP4: Unable to connect: com.perforce.p4java.exception.ConnectionException: * WARNING PERFORCE SERVER IDENTIFICATION HAS CHANGED! * It is possible that someone is intercepting your connection to the Perforce server '
p4brsb.lss.emc.com
xxx
:1666' If this is not a scheduled key change, then you should contact your Perforce administrator. The fingerprint for the mismatched key sent to your client is
 71:FB:BD:1A:FA:D2:EF:D8:A7:12:70:B5:61:01:4F:2F:46:B1:BF:C3
 xxx
Can't trust mismatched Perforce server key without both 'force' and 'autoAccept' options.P4: Unable to use Workspace: java.lang.NullPointerExceptionP4: Unable to close Perforce connection: java.lang.NullPointerExceptionERROR: Unable to update workspace: java.lang.NullPointerExceptionWarning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggeredNotifying upstream build authc-java-snapshot #110 of job completionProject authc-java-snapshot still waiting for [authc-windows-x64-snapshot, authc-solaris-sparcv9-snapshot] builds to completeNotifying upstream projects of job completionNotifying upstream of completion: authc-java-snapshot #110Finished: FAILUREAlso notice that .p4trust updated for each build. There my be some concurrent write/read issue?I dont see the error on normal post job trigger, and it also does not show up at Perforce Plugin ( the one uses p4 exe)



























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







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

[JIRA] [scm-sync-configuration] (JENKINS-15128) Renaming job doesn't work with Git

2014-08-26 Thread fcamb...@java.net (JIRA)















































Frédéric Camblor
 commented on  JENKINS-15128


Renaming job doesn't work with Git















mmm.. I didn't tested it against file hierarchy (to test, I only settled simple freestyle job, thus not having any subdirectories)

There must be another issue here, could you file another issue about this 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







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

[JIRA] [scm-sync-configuration] (JENKINS-15128) Renaming job doesn't work with Git

2014-08-26 Thread bpodgur...@gmail.com (JIRA)















































Benjamin Podgursky
 commented on  JENKINS-15128


Renaming job doesn't work with Git















This actually doesn't have any subdirectories, it's just erroring because the target is a folder (the only thing inside is config.xml).  Unless the job was a single file, I don't see how the simple rm would work.



























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







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

[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client

2014-08-26 Thread dacul...@cisco.com (JIRA)















































David Cullen
 commented on  JENKINS-22820


Changes are not commited when using a recent git client















I have installed the 0.0.8 version of the scm-sync-configuration plugin and it still does not work with git 1.9.1 on Ubuntu 14.04.
The 0.0.8 version of the plugin partially works with git 1.8.3.2; however, the commit message dialog is not displayed.
Is there anything I can do to help resolve these problems?



























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







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

[JIRA] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs

2014-08-26 Thread mr...@sjm.com (JIRA)















































Michael Rose
 commented on  JENKINS-24028


using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs















Whoops! I didn't realize that label was the default name for the node axis. That solved the problem for the error in my second comment, but the first error still persists.


ERROR: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification.
Mapping '//JenkinsJob_test-new-p4plugin/arch=linux,bar=222,foo=yyy/...' is not under '//JenkinsJob_test-new-p4plugin-arch-linux-bar-222-foo-yyy/...'.

It looks like you don't replace you don't replace special characters in the view. Is there another way that I should be configuring my view that does not involve using the workspace name? The old plugin allowed for a special token to be used in that spot and they just replaced it later.



























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







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

[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client

2014-08-26 Thread roge...@java.net (JIRA)















































rogerhu
 commented on  JENKINS-22820


Changes are not commited when using a recent git client















The commit message dialog not being displayed is a different issue and a regression from a previous change.

What other symptoms are you seeing?

You can debug this too by using IntelliJ Community Edition and importing the project too...click right-click on the hpi:run and you can startup your own instance of Jenkins (bit.ly/1t9vKDd)



























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







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

[JIRA] [ghprb] (JENKINS-24145) latest ghprb plugin broken for gihub enterprise users

2014-08-26 Thread gshivel...@gmail.com (JIRA)















































Grant Shively
 reopened  JENKINS-24145


latest ghprb plugin broken for gihub enterprise users
















This bug still occurs in 1.14-5.  David Tanner has explained that the bug is caused by the github-api plugin, but closing this bug is misleading, since the github pull request plugin is still unusable for all github enterprise users.  Re-opening this bug will get it more visibility, which will hopefully get it fixed sooner.





Change By:


Grant Shively
(26/Aug/14 4:06 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







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

[JIRA] [git] (JENKINS-24448) Empty changes when building from tag not branch

2014-08-26 Thread pawel.per...@pwr.edu.pl (JIRA)















































Paweł Peryga
 created  JENKINS-24448


Empty changes when building from tag not branch















Issue Type:


Bug



Assignee:


Nicolas De Loof



Components:


git



Created:


26/Aug/14 4:23 PM



Description:


When triggering build with tag parameter not branch e.g. master the list of changes is always empty. Is this behaviour proper?




Project:


Jenkins



Priority:


Blocker



Reporter:


Paweł Peryga

























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







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

[JIRA] [build-pipeline] (JENKINS-24423) Just created (but not yet saved) pipeline breaks Jenkins















































Daniel Beck
 commented on  JENKINS-24423


Just created (but not yet saved) pipeline breaks Jenkins















Both seem to be the same overall issue of bad handling of incomplete or invalid input, especially while the created view has only been created, not configured. Maybe add a note to JENKINS-23363 that there's minor differences in the reports and that all relevant fields need fixes.



























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







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

[JIRA] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs















































Paul Allen
 commented on  JENKINS-24028


using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs















Are you using a the Manual workspace configuration (or Spec/Static/Stream/Template)?

Please can you send me the workspace view in Jenkins (if using the Manual mode)...
...and the client's view in Perforce. `p4 client -o `

and let me know which view is which.



























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







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

[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client

2014-08-26 Thread dacul...@cisco.com (JIRA)















































David Cullen
 commented on  JENKINS-22820


Changes are not commited when using a recent git client















> What other symptoms are you seeing?

When I install git 1.9.1 the checkoutConfiguration directory is created but the .git repository is not cloned from the remote.

I am unable to build the plugin. If I change the parent version to 1.509 so that the plugin will build with Java 7, the tests fail:



org.jenkins-ci.plugins
plugin
1.509
../pom.xml
  


Are you building against Java 6?



























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







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

[JIRA] [core] (JENKINS-23330) Spaces in project names are not encoded on IDs















































Daniel Beck
 commented on  JENKINS-23330


Spaces in project names are not encoded on  IDs















Just asked, never used the plugin.

Checking the plugin code, these actually seem to be used, however only for the function `ks_view_job_next`, `ks_view_job_prev`, which are triggered by j/k/n/p.

I just don't see how this could not achieved in the plugin by adding the classes in JS...



























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







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

[JIRA] [core] (JENKINS-24407) missing weather icons (randomly?)

2014-08-26 Thread mho...@8thbridge.com (JIRA)















































Mike Hobbs
 commented on  JENKINS-24407


missing weather icons (randomly?)















I can confirm that I'm seeing the same problem on our jobs that use Cobertura.



























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







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

[JIRA] [slave-squatter] (JENKINS-24449) slave cleanup causes jobs to hang

2014-08-26 Thread c...@miaow.com (JIRA)















































Christian Goetze
 created  JENKINS-24449


slave cleanup causes jobs to hang















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


slave-squatter



Created:


26/Aug/14 5:33 PM



Description:


I observe that jobs starting at the same time the slave is performing some sort of cleanup action hang:

Build Log:

17:04:21 Started by upstream project "pipeline-test-2" build number 422
17:04:21 originally caused by:
17:04:21  Started by upstream project "master-test" build number 867
17:04:21  originally caused by:
17:04:21   Started by upstream project "master-build" build number 5131
17:04:21   originally caused by:
17:04:21Started by an SCM change
17:04:21 [EnvInject] - Loading node environment variables.
... hang for 14h ...



Slave Log:

... lots of output ...
INFO: Deleting /tmp/1408400946520-0/jboss51x_centos5-x64-bld-slave-09.corp.appdynamics.com_10002/lib/jboss-j2se.jar (atime=1408400947, diff=-5424)
Aug 25, 2014 5:01:12 PM hudson.plugins.tmpcleaner.TmpCleanTask visit
INFO: Deleting /tmp/1408400946520-0/jboss51x_centos5-x64-bld-slave-09.corp.appdynamics.com_10002/lib/javassist.jar (atime=1408400947, diff=-5424)
Aug 25, 2014 5:01:12 PM hudson.plugins.tmpcleaner.TmpCleanTask visit
INFO: Deleting /tmp/1408400946520-0/jboss51x_centos5-x64-bld-slave-09.corp.appdynamics.com_10002/lib/jboss-system-jmx.jar (atime=1408400947, diff=-5424)
Aug 25, 2014 5:01:12 PM hudson.plugins.tmpcleaner.TmpCleanTask visit
INFO: Deleting /tmp/1408400946520-0/jboss51x_centos5-x64-bld-slave-09.corp.appdynamics.com_10002/lib/jboss-system.jar (atime=1408400947, diff=-5424)
Aug 25, 2014 5:01:12 PM hudson.plugins.tmpcleaner.TmpCleanTask visit
INFO: Deleting /tmp/1408400946520-0/jboss51x_centos5-x64-bld-slave-09.corp.appdynamics.com_10002/lib/jboss-mdr.jar (atime=1408400947, diff=-5424)
Aug 25, 2014 5:01:12 PM hudson.plugins.tmpcleaner.TmpCleanTask visit
INFO: Deleting /tmp/1408400946520-0/jboss51x_centos5-x64-bld-slave-09.corp.appdynamics.com_10002/lib/jboss-logging-spi.jar (atime=1408400947, diff=-5424)
Aug 25, 2014 5:01:12 PM hudson.plugins.tmpcleaner.TmpCleanTask visit



After interrupting the job, I get this:

0:30:26 ERROR: SEVERE ERROR occurs
10:30:26 org.jenkinsci.lib.envinject.EnvInjectException: java.lang.InterruptedException
10:30:26 	at org.jenkinsci.plugins.envinject.service.EnvironmentVariablesNodeLoader.gatherEnvironmentVariablesNode(EnvironmentVariablesNodeLoader.java:77)
10:30:26 	at org.jenkinsci.plugins.envinject.EnvInjectListener.loadEnvironmentVariablesNode(EnvInjectListener.java:81)
10:30:26 	at org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironment(EnvInjectListener.java:39)
10:30:26 	at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:575)
10:30:26 	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:481)
10:30:26 	at hudson.model.Run.execute(Run.java:1689)
10:30:26 	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
10:30:26 	at hudson.model.ResourceController.execute(ResourceController.java:88)
10:30:26 	at hudson.model.Executor.run(Executor.java:231)
10:30:26 Caused by: java.lang.InterruptedException
10:30:26 	at java.lang.Object.wait(Native Method)
10:30:26 	at hudson.remoting.Request.call(Request.java:146)
10:30:26 	at hudson.remoting.Channel.call(Channel.java:722)
10:30:26 	at hudson.FilePath.act(FilePath.java:1003)
10:30:26 	at org.jenkinsci.plugins.envinject.service.EnvironmentVariablesNodeLoader.gatherEnvironmentVariablesNode(EnvironmentVariablesNodeLoader.java:44)
10:30:26 	... 8 more
10:30:26 Archiving artifacts
10:30:26 ERROR: Publisher hudson.tasks.Mailer aborted due to exception
10:30:26 
hudson.remoting.ChannelClosedException: channel is already closed
10:30:26 	at hudson.remoting.Channel.send(Channel.java:524)
10:30:26 	at hudson.remoting.Request.call(Request.java:129)
10:30:26 	at hudson.remoting.Channel.call(Channel.java:722)
10:30:26 	at hudson.EnvVars.getRemote(EnvVars.java:404)
10:30:26 	at hudson.model.Computer.getEnvironment(Computer.java:911)
10:30:26 	at jenkins.model.CoreEnv

[JIRA] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs

2014-08-26 Thread mr...@sjm.com (JIRA)















































Michael Rose
 updated  JENKINS-24028


using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
















I am using the Manual workspace configuration:


Client view for parent:


Client: JenkinsJob_test-new-p4plugin

Update: 2014/08/22 14:57:04

Access: 2014/08/26 12:22:02

Owner:  integ

Root:   /usr/local/jenkins/jobs/test-new-p4plugin/workspace

Options:noallwrite clobber nocompress unlocked nomodtime normdir

SubmitOptions:  submitunchanged

LineEnd:local

View:
//test_mrose/... //JenkinsJob_test-new-p4plugin/...


Client view for one of the configurations:

Client: JenkinsJob_test-new-p4plugin-arch-linux-bar-111-foo-xxx

Update: 2014/08/26 10:25:33

Access: 2014/08/26 10:25:33

Root:   null

Options:noallwrite noclobber nocompress unlocked nomodtime normdir

SubmitOptions:  submitunchanged

LineEnd:local





Change By:


Michael Rose
(26/Aug/14 5:33 PM)




Attachment:


p4plugin_configurations_issue24028.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







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

[JIRA] [slave-squatter] (JENKINS-24449) slave cleanup causes jobs to hang

2014-08-26 Thread c...@miaow.com (JIRA)















































Christian Goetze
 updated  JENKINS-24449


slave cleanup causes jobs to hang
















Change By:


Christian Goetze
(26/Aug/14 5:34 PM)




Description:


I observe that jobs starting at the same time the slave is performing some sort of cleanup action hang:Build Log:{noformat}17:04:21 Started by upstream project "pipeline-test-2" build number 42217:04:21 originally caused by:17:04:21  Started by upstream project "master-test" build number 86717:04:21  originally caused by:17:04:21   Started by upstream project "master-build" build number 513117:04:21   originally caused by:17:04:21Started by an SCM change17:04:21 [EnvInject] - Loading node environment variables hang for 14h ...{noformat}Slave Log:{noformat}... lots of output ...INFO: Deleting /tmp/1408400946520-0/jboss51x_centos5-x64-bld-slave-09.corp.
appdynamics
XXX
.com_10002/lib/jboss-j2se.jar (atime=1408400947, diff=-5424)Aug 25, 2014 5:01:12 PM hudson.plugins.tmpcleaner.TmpCleanTask visitINFO: Deleting /tmp/1408400946520-0/jboss51x_centos5-x64-bld-slave-09.corp.
appdynamics
XXX
.com_10002/lib/javassist.jar (atime=1408400947, diff=-5424)Aug 25, 2014 5:01:12 PM hudson.plugins.tmpcleaner.TmpCleanTask visitINFO: Deleting /tmp/1408400946520-0/jboss51x_centos5-x64-bld-slave-09.corp.
appdynamics
XXX
.com_10002/lib/jboss-system-jmx.jar (atime=1408400947, diff=-5424)Aug 25, 2014 5:01:12 PM hudson.plugins.tmpcleaner.TmpCleanTask visitINFO: Deleting /tmp/1408400946520-0/jboss51x_centos5-x64-bld-slave-09.corp.
appdynamics
XXX
.com_10002/lib/jboss-system.jar (atime=1408400947, diff=-5424)Aug 25, 2014 5:01:12 PM hudson.plugins.tmpcleaner.TmpCleanTask visitINFO: Deleting /tmp/1408400946520-0/jboss51x_centos5-x64-bld-slave-09.corp.
appdynamics
XXX
.com_10002/lib/jboss-mdr.jar (atime=1408400947, diff=-5424)Aug 25, 2014 5:01:12 PM hudson.plugins.tmpcleaner.TmpCleanTask visitINFO: Deleting /tmp/1408400946520-0/jboss51x_centos5-x64-bld-slave-09.corp.
appdynamics
XXX
.com_10002/lib/jboss-logging-spi.jar (atime=1408400947, diff=-5424)Aug 25, 2014 5:01:12 PM hudson.plugins.tmpcleaner.TmpCleanTask visit{noformat}After interrupting the job, I get this:{noformat}0:30:26 ERROR: SEVERE ERROR occurs10:30:26 org.jenkinsci.lib.envinject.EnvInjectException: java.lang.InterruptedException10:30:26 	at org.jenkinsci.plugins.envinject.service.EnvironmentVariablesNodeLoader.gatherEnvironmentVariablesNode(EnvironmentVariablesNodeLoader.java:77)10:30:26 	at org.jenkinsci.plugins.envinject.EnvInjectListener.loadEnvironmentVariablesNode(EnvInjectListener.java:81)10:30:26 	at org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironment(EnvInjectListener.java:39)10:30:26 	at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:575)10:30:26 	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:481)10:30:26 	at hudson.model.Run.execute(Run.java:1689)10:30:26 	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)10:30:26 	at hudson.model.ResourceController.execute(ResourceController.java:88)10:30:26 	at hudson.model.Executor.run(Executor.java:231)10:30:26 Caused by: java.lang.InterruptedException10:30:26 	at java.lang.Object.wait(Native Method)10:30:26 	at hudson.remoting.Request.call(Request.java:146)10:30:26 	at hudson.remoting.Channel.call(Channel.java:722)10:30:26 	at hudson.FilePath.act(FilePath.java:1003)10:30:26 	at org.jenkinsci.plugins.envinject.service.EnvironmentVariablesNodeLoader.gatherEnvironmentVariablesNode(EnvironmentVariablesNodeLoader.java:44)10:30:26 	... 8 more10:30:26 Archiving artifacts10:30:26 ERROR: Publisher hudson.tasks.Mailer aborted due to exception10:30:26 hudson.remoting.ChannelClosedException: channel is already closed10:30:26 	at hudson.remoting.Channel.send(Channel.java:524)10:30:26 	at hudson.remoting.Request.call(Request.java:129)10:30:26 	at hudson.remoting.Channel.call(Channel.java:722)10:30:26 	at hudson.EnvVars.getRemote(EnvVars.java:404)10:30:26 	at hudson.model.Computer.getEnvironment(Computer.java:911)10:30:26 	at jenkins.model.CoreEnvironmentContributor.buildEnvironmentFor(CoreEnvironmentContributor.java:29)10:30:26 	at hudson.model.Run.getEnvironment(Run.java:2202)10:30:26 	at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:873)10:30:26 	at hudson.tas

[JIRA] [delivery-pipeline] (JENKINS-24392) Manual Build Trigger invoke job on different folder level

2014-08-26 Thread pat...@diabol.se (JIRA)
















































Patrik Boström
 resolved  JENKINS-24392 as Fixed


Manual Build Trigger invoke job on different folder level
















Will be released in 0.8.6





Change By:


Patrik Boström
(26/Aug/14 5:38 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







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

[JIRA] [delivery-pipeline] (JENKINS-22876) Support for Promoted Builds Plugin

2014-08-26 Thread pat...@diabol.se (JIRA)















































Patrik Boström
 commented on  JENKINS-22876


Support for Promoted Builds Plugin















Will be released in 0.8.6



























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







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

[JIRA] [ghprb] (JENKINS-24447) latest ghprb plugin still broken for github enterprise users athough JENKINS-24145 marked as resolved

2014-08-26 Thread david.joel.tan...@gmail.com (JIRA)















































David Tanner
 commented on  JENKINS-24447


latest ghprb plugin still broken for github enterprise users athough JENKINS-24145 marked as resolved















I added a workaround for enterprise versions, if the apiURL contains api/v3 then it won't call the listCommits method at all.  I hope this works until the github plugin is updated.

v1.14-6




























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







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

[JIRA] [subversion] (JENKINS-24438) Jenkins crashes regularly using Subversion Plugin 2.4.1















































Daniel Beck
 commented on  JENKINS-24438


Jenkins crashes regularly using Subversion Plugin 2.4.1















Also, JENKINS-16427.



























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







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

[JIRA] [subversion] (JENKINS-24438) Jenkins crashes regularly using Subversion Plugin 2.4.1















































Daniel Beck
 commented on  JENKINS-24438


Jenkins crashes regularly using Subversion Plugin 2.4.1















Appears to be related to use of Gnome Keyring by the SVNKit library.

May be related to SVNKIT-312, try what's described here as a workaround.



























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







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

[JIRA] [core] (JENKINS-18537) ArrayIndexOutOfBoundsException during Jenkins.doConfigSubmit; need XStream 1.4.6

2014-08-26 Thread jgl...@cloudbees.com (JIRA)















































Jesse Glick
 commented on  JENKINS-18537


ArrayIndexOutOfBoundsException during Jenkins.doConfigSubmit; need XStream 1.4.6















@leedega your issue is totally unrelated: something like JENKINS-20327 (but affecting the Sectioned View plugin rather than the built-in list view).



























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







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

[JIRA] [core] (JENKINS-24428) NullPointerException after Login
















































Daniel Beck
 resolved  JENKINS-24428 as Duplicate


NullPointerException after Login
















Unless proven otherwise, assuming to be a duplicates of JENKINS-24317.





Change By:


Daniel Beck
(26/Aug/14 6:04 PM)




Status:


Open
Resolved





Assignee:


R. Tyler Croy





Resolution:


Duplicate



























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







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

[JIRA] [core] (JENKINS-24440) Jenkins cannot delete root-owned files/folders in jenkins-owned directories