date:20150217
















































Nick Grealy
 assigned  JENKINS-25165 to Nick Grealy



Re-build a job using poll-mailbox-trigger-plugin
















Change By:


Nick Grealy
(18/Feb/15 1:03 AM)




Assignee:


NickGrealy



























This message is automatically generated by JIRA.
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-plugin] (JENKINS-26612) svn: absolutely unacceptably SLOW

2015-02-17 Thread i-love-s...@yandex.ru (JIRA)















































Pablob P
 commented on  JENKINS-26612


svn: absolutely unacceptably SLOW















I'm not even sure how to down grade to older version.

I think there is HUGE bug in svn code. For some retarded reason it tries to wipeout entire repo and checkout it again from scratch. I see it once again right now, it's been doing svn update for more than an hour already, and it was only a minor change in one file.

Here's what I see:

Started by user anonymous
Building in workspace C:\work\jenkins\my-project-name
Updating svn+ssh://my-username@svn-host/usr/svn/trunk/my-project-name at revision '2015-02-17T21:28:59.850 -0500'
Workspace appear to be locked, so getting a fresh workspace
Cleaning local Directory .

hours of wasted time here.


It looks like if the workspace is locked for whatever reason it does that wipe-out step. Can I disable that somehow??



























This message is automatically generated by JIRA.
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-plugin] (JENKINS-27001) On Windows installations if the pipeline view is set to show more than 200 jobs CPU is pushed to 100% causing the system to freeze















































Libero Scarcelli
 updated  JENKINS-27001


On Windows installations if the pipeline view is set to show more than 200 jobs CPU is pushed to 100% causing the system to freeze
















Change By:


Libero Scarcelli
(18/Feb/15 4:10 AM)




Description:


OnWindowsinstallationsifthepipelineviewissettoshowmorethan200jobsCPUispushedto100%causingthesystemtofreezeTestedonasinglecoreWindows2008R2machinerunningJenkins1.596.Theproblem*seems*togetworseafterinstallingthelatestcore(1.599
atthisstage
)duemaybetothelatestlogformatchanges(?)Withmultiplecoresit*might*bepossibletoincreasethenumberofrowstobeshownwithoutanyissue.However,IthinkloadingbuildlogsatthisstageisCPUconsuming



























This message is automatically generated by JIRA.
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-plugin] (JENKINS-25391) Cannot delete project
















































Idan Bidani
 closed  JENKINS-25391 as Fixed


Cannot delete project
















Been fixed here https://github.com/jenkinsci/build-pipeline-plugin/commit/880ba84553e1e6a58c284a8c8a705495ed5911b0





Change By:


Idan Bidani
(18/Feb/15 12:09 AM)




Status:


Reopened
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] [build-pipeline-plugin] (JENKINS-25391) Cannot delete project















































Idan Bidani
 reopened  JENKINS-25391


Cannot delete project
















should be closed as fixed





Change By:


Idan Bidani
(18/Feb/15 12:08 AM)




Resolution:


CannotReproduce





Status:


Closed
Reopened



























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







-- 
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-plugin] (JENKINS-26993) GIT Plugin requires /tmp to be executable

2015-02-17 Thread mark.earl.wa...@gmail.com (JIRA)

Mark Waite
commented on JENKINS-26993

GIT Plugin requires /tmp to be executable

This is not a bug, as far as I can tell, or at least your description does not give me confidence this is a bug.

I think you want to control where the git plugin (and possibly the rest of Jenkins) writes its temporary files. Have you tried adjusting the values of the environment variables (TMP) and properties (java.io.tmpdir) from the command line, or from the environment which starts the Jenkins server and / or the relevant slave agent? Refer to stackoverflow for one source of that information.

If you have made those adjustments and still see a requirement for a specific directory, please provided a detailed list of the steps you take to show the problem. For an even better chance of having your concerns addressed, submit a pull request to the git plugin and/or git client plugin with a test which shows the failure, and a code change which fixes the failure.

If you still believe this is a bug, please provide the additional information suggested in how to report an issue

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

--
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-plugin] (JENKINS-25391) Cannot delete project
















































Idan Bidani
 closed  JENKINS-25391 as Cannot Reproduce


Cannot delete project
















Change By:


Idan Bidani
(17/Feb/15 11:21 PM)




Status:


Open
Closed





Assignee:


IdanBidani





Resolution:


CannotReproduce



























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







-- 
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-trigger-plugin] (JENKINS-26616) Multi-config project concurrent build race

2015-02-17 Thread dmasla...@java.net (JIRA)















































Dmitry Maslakov
 commented on  JENKINS-26616


Multi-config project concurrent build race















After upgrade from 1.596 to 1.599 I got same issues. It happened on matrix job.

Here is a log, see how same build numbers are probed several times and failed:


Feb 18, 2015 6:55:09 AM hudson.model.Executor run
SEVERE: Unexpected executor death
java.lang.IllegalStateException: cannot create a build with number 2439 since that (or higher) is already in use among [2376, 2377, 2378, 2379, 2380, 2381, 2382, 2383, 2384, 2385, 2386, 2387, 2388, 2389, 2390, 2391, 2392, 2393, 2394, 2395, 2396, 2397, 2398, 2399, 2400, 2401, 2402, 2403, 2404, 2405, 2406, 2407, 2408, 2409, 2410, 2411, 2412, 2413, 2414, 2415, 2416, 2417, 2418, 2419, 2420, 2421, 2422, 2423, 2424, 2425, 2426, 2427, 2428, 2429, 2430, 2431, 2432, 2433, 2434, 2435, 2436, 2441]
at jenkins.model.lazy.AbstractLazyLoadRunMap.proposeNewNumber(AbstractLazyLoadRunMap.java:361)
at hudson.model.RunMap.put(RunMap.java:189)
at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:284)
at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:74)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1205)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144)
at hudson.model.Executor.run(Executor.java:213)

Feb 18, 2015 6:55:09 AM hudson.model.Executor run
SEVERE: Unexpected executor death
java.lang.IllegalStateException: cannot create a build with number 2440 since that (or higher) is already in use among [2376, 2377, 2378, 2379, 2380, 2381, 2382, 2383, 2384, 2385, 2386, 2387, 2388, 2389, 2390, 2391, 2392, 2393, 2394, 2395, 2396, 2397, 2398, 2399, 2400, 2401, 2402, 2403, 2404, 2405, 2406, 2407, 2408, 2409, 2410, 2411, 2412, 2413, 2414, 2415, 2416, 2417, 2418, 2419, 2420, 2421, 2422, 2423, 2424, 2425, 2426, 2427, 2428, 2429, 2430, 2431, 2432, 2433, 2434, 2435, 2436, 2441]
at jenkins.model.lazy.AbstractLazyLoadRunMap.proposeNewNumber(AbstractLazyLoadRunMap.java:361)
at hudson.model.RunMap.put(RunMap.java:189)
at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:284)
at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:74)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1205)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144)
at hudson.model.Executor.run(Executor.java:213)

Feb 18, 2015 6:55:14 AM hudson.model.Executor run
SEVERE: Unexpected executor death
java.lang.IllegalStateException: cannot create a build with number 2439 since that (or higher) is already in use among [2379, 2380, 2381, 2382, 2383, 2384, 2385, 2386, 2387, 2388, 2389, 2390, 2391, 2392, 2393, 2394, 2395, 2396, 2397, 2398, 2399, 2400, 2401, 2402, 2403, 2404, 2405, 2406, 2407, 2408, 2409, 2410, 2411, 2412, 2413, 2414, 2415, 2416, 2417, 2418, 2419, 2420, 2421, 2422, 2423, 2424, 2425, 2426, 2427, 2428, 2429, 2430, 2431, 2432, 2433, 2434, 2435, 2436, 2437, 2438, 2441]
at jenkins.model.lazy.AbstractLazyLoadRunMap.proposeNewNumber(AbstractLazyLoadRunMap.java:361)
at hudson.model.RunMap.put(RunMap.java:189)
at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:284)
at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:74)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1205)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144)
at hudson.model.Executor.run(Executor.java:213)

Feb 18, 2015 6:55:15 AM hudson.model.Executor run
SEVERE: Unexpected executor death
java.lang.IllegalStateException: cannot create a build with number 2440 since that (or higher) is already in use among [2379, 2380, 2381, 2382, 2383, 2384, 2385, 2386, 2387, 2388, 2389, 2390, 2391, 2392, 2393, 2394, 2395, 2396, 2397, 2398, 2399, 2400, 2401, 2402, 2403, 2404, 2405, 2406, 2407, 2408, 2409, 2410, 2411, 2412, 2413, 2414, 2415, 2416, 2417, 2418, 2419, 2420, 2421, 2422, 2423, 2424, 2425, 2426, 2427, 2428, 2429, 2430, 2431, 2432, 2433, 2434, 2435, 2436, 2437, 2438, 2441]
at jenkins.model.lazy.AbstractLazyLoadRunMap.proposeNewNumber(AbstractLazyLoadRunMap.java:361)
at hudson.model.RunMap.put(RunMap.java:189)
at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:284)
at

[JIRA] [git-client-plugin] (JENKINS-26981) Git plugin ignores the branch we tell it to build and builds a random branch instead

2015-02-17 Thread mark.earl.wa...@gmail.com (JIRA)
















































Mark Waite
 resolved  JENKINS-26981 as Not A Defect


Git plugin ignores the branch we tell it to build and builds a random branch instead
















Change By:


Mark Waite
(18/Feb/15 12:34 AM)




Status:


Open
Resolved





Resolution:


NotADefect



























This message is automatically generated by JIRA.
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-plugin] (JENKINS-25391) Cannot delete project















































Idan Bidani
 commented on  JENKINS-25391


Cannot delete project















I Agree Daniel, However this issue is not reproducible therefore will be 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] [poll-mailbox-trigger-plugin] (JENKINS-25165) Re-build a job using poll-mailbox-trigger-plugin
















































Nick Grealy
 resolved  JENKINS-25165 as Fixed


Re-build a job using poll-mailbox-trigger-plugin
















Fixed in version 0.16





Change By:


Nick Grealy
(18/Feb/15 2:36 AM)




Status:


InProgress
Resolved





Resolution:


Fixed



























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







-- 
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] [poll-mailbox-trigger-plugin] (JENKINS-25165) Re-build a job using poll-mailbox-trigger-plugin















































Nick Grealy
 commented on  JENKINS-25165


Re-build a job using poll-mailbox-trigger-plugin















Or better yet, I'll just close this ticket now, and we can reopen if it's still occurring.



























This message is automatically generated by JIRA.
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] [poll-mailbox-trigger-plugin] (JENKINS-25165) Re-build a job using poll-mailbox-trigger-plugin
















































Nick Grealy
 assigned  JENKINS-25165 to Gaurav Chhabra



Re-build a job using poll-mailbox-trigger-plugin
















Hi Gaurav,

Just realised this ticket was still open from Oct 2014. Going back over the emails, I'm sure we fixed this issue together. If you're happy that the issue is resolved (in version 0.16), I'll close off the ticket.

(Or, if I don't here back within 2 weeks, I'll close off the ticket.)

Kind regards,

Nick Grealy





Change By:


Nick Grealy
(18/Feb/15 2:34 AM)




Assignee:


NickGrealy
GauravChhabra



























This message is automatically generated by JIRA.
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] [poll-mailbox-trigger-plugin] (JENKINS-25165) Re-build a job using poll-mailbox-trigger-plugin















































Nick Grealy
 started work on  JENKINS-25165


Re-build a job using poll-mailbox-trigger-plugin
















Change By:


Nick Grealy
(18/Feb/15 2:35 AM)




Status:


Open
InProgress



























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







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

[JIRA] [build-pipeline-plugin] (JENKINS-25391) Cannot delete project















































Daniel Beck
 commented on  JENKINS-25391


Cannot delete project















Has nothing to do with "not reproducible", this particular NPE was fixed in https://github.com/jenkinsci/build-pipeline-plugin/commit/880ba84553e1e6a58c284a8c8a705495ed5911b0



























This message is automatically generated by JIRA.
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-client-plugin] (JENKINS-26981) Git plugin ignores the branch we tell it to build and builds a random branch instead

2015-02-17 Thread mark.earl.wa...@gmail.com (JIRA)
















































Mark Waite
 closed  JENKINS-26981 as Not A Defect


Git plugin ignores the branch we tell it to build and builds a random branch instead
















Change By:


Mark Waite
(18/Feb/15 12:34 AM)




Status:


Resolved
Closed



























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







-- 
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] [s3-plugin] (JENKINS-23338) Retry S3 uploads a couple times before giving up?

2015-02-17 Thread schristo...@gmail.com (JIRA)
















































Steven Christou
 resolved  JENKINS-23338 as Fixed


Retry S3 uploads a couple times before giving up?
















Fixed by Mattias Appelgren in PR 36. Thank you Mattias Appelgren!





Change By:


Steven Christou
(18/Feb/15 2:31 AM)




Status:


Open
Resolved





Assignee:


MichaelWatt
MattiasAppelgren





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-26739) Executors are dying since 1.597 - related to the directory layout change?

2015-02-17 Thread dmasla...@java.net (JIRA)















































Dmitry Maslakov
 commented on  JENKINS-26739


Executors are dying since 1.597 - related to the directory layout change?















After upgrade from 1.596 to 1.599 I got same issues. It happened on matrix job.

Here is a log, see how same build numbers are probed several times and failed:


Feb 18, 2015 6:55:09 AM hudson.model.Executor run
SEVERE: Unexpected executor death
java.lang.IllegalStateException: cannot create a build with number 2439 since that (or higher) is already in use among [2376, 2377, 2378, 2379, 2380, 2381, 2382, 2383, 2384, 2385, 2386, 2387, 2388, 2389, 2390, 2391, 2392, 2393, 2394, 2395, 2396, 2397, 2398, 2399, 2400, 2401, 2402, 2403, 2404, 2405, 2406, 2407, 2408, 2409, 2410, 2411, 2412, 2413, 2414, 2415, 2416, 2417, 2418, 2419, 2420, 2421, 2422, 2423, 2424, 2425, 2426, 2427, 2428, 2429, 2430, 2431, 2432, 2433, 2434, 2435, 2436, 2441]
at jenkins.model.lazy.AbstractLazyLoadRunMap.proposeNewNumber(AbstractLazyLoadRunMap.java:361)
at hudson.model.RunMap.put(RunMap.java:189)
at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:284)
at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:74)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1205)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144)
at hudson.model.Executor.run(Executor.java:213)

Feb 18, 2015 6:55:09 AM hudson.model.Executor run
SEVERE: Unexpected executor death
java.lang.IllegalStateException: cannot create a build with number 2440 since that (or higher) is already in use among [2376, 2377, 2378, 2379, 2380, 2381, 2382, 2383, 2384, 2385, 2386, 2387, 2388, 2389, 2390, 2391, 2392, 2393, 2394, 2395, 2396, 2397, 2398, 2399, 2400, 2401, 2402, 2403, 2404, 2405, 2406, 2407, 2408, 2409, 2410, 2411, 2412, 2413, 2414, 2415, 2416, 2417, 2418, 2419, 2420, 2421, 2422, 2423, 2424, 2425, 2426, 2427, 2428, 2429, 2430, 2431, 2432, 2433, 2434, 2435, 2436, 2441]
at jenkins.model.lazy.AbstractLazyLoadRunMap.proposeNewNumber(AbstractLazyLoadRunMap.java:361)
at hudson.model.RunMap.put(RunMap.java:189)
at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:284)
at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:74)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1205)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144)
at hudson.model.Executor.run(Executor.java:213)

Feb 18, 2015 6:55:14 AM hudson.model.Executor run
SEVERE: Unexpected executor death
java.lang.IllegalStateException: cannot create a build with number 2439 since that (or higher) is already in use among [2379, 2380, 2381, 2382, 2383, 2384, 2385, 2386, 2387, 2388, 2389, 2390, 2391, 2392, 2393, 2394, 2395, 2396, 2397, 2398, 2399, 2400, 2401, 2402, 2403, 2404, 2405, 2406, 2407, 2408, 2409, 2410, 2411, 2412, 2413, 2414, 2415, 2416, 2417, 2418, 2419, 2420, 2421, 2422, 2423, 2424, 2425, 2426, 2427, 2428, 2429, 2430, 2431, 2432, 2433, 2434, 2435, 2436, 2437, 2438, 2441]
at jenkins.model.lazy.AbstractLazyLoadRunMap.proposeNewNumber(AbstractLazyLoadRunMap.java:361)
at hudson.model.RunMap.put(RunMap.java:189)
at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:284)
at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:74)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1205)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144)
at hudson.model.Executor.run(Executor.java:213)

Feb 18, 2015 6:55:15 AM hudson.model.Executor run
SEVERE: Unexpected executor death
java.lang.IllegalStateException: cannot create a build with number 2440 since that (or higher) is already in use among [2379, 2380, 2381, 2382, 2383, 2384, 2385, 2386, 2387, 2388, 2389, 2390, 2391, 2392, 2393, 2394, 2395, 2396, 2397, 2398, 2399, 2400, 2401, 2402, 2403, 2404, 2405, 2406, 2407, 2408, 2409, 2410, 2411, 2412, 2413, 2414, 2415, 2416, 2417, 2418, 2419, 2420, 2421, 2422, 2423, 2424, 2425, 2426, 2427, 2428, 2429, 2430, 2431, 2432, 2433, 2434, 2435, 2436, 2437, 2438, 2441]
at jenkins.model.lazy.AbstractLazyLoadRunMap.proposeNewNumber(AbstractLazyLoadRunMap.java:361)
at hudson.model.RunMap.put(RunMap.java:189)
at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:284)
at

[JIRA] [build-pipeline-plugin] (JENKINS-27001) On Windows installations if the pipeline view is set to show more than 200 jobs CPU is pushed to 100% causing the system to freeze















































Libero Scarcelli
 created  JENKINS-27001


On Windows installations if the pipeline view is set to show more than 200 jobs CPU is pushed to 100% causing the system to freeze















Issue Type:


Bug



Assignee:


Unassigned


Components:


build-pipeline-plugin



Created:


18/Feb/15 3:56 AM



Description:


On Windows installations if the pipeline view is set to show more than 200 jobs CPU is pushed to 100% causing the system to freeze

Tested on a single core Windows 2008 R2 machine... with multiple cores it might be possible to increase the number of rows to be shown without any issue. However, I think loading build logs at this stage is CPU consuming




Project:


Jenkins



Labels:


pipeline
cpu




Priority:


Critical



Reporter:


Libero Scarcelli

























This message is automatically generated by JIRA.
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-plugin] (JENKINS-27001) On Windows installations if the pipeline view is set to show more than 200 jobs CPU is pushed to 100% causing the system to freeze















































Libero Scarcelli
 updated  JENKINS-27001


On Windows installations if the pipeline view is set to show more than 200 jobs CPU is pushed to 100% causing the system to freeze
















Change By:


Libero Scarcelli
(18/Feb/15 4:09 AM)




Description:


OnWindowsinstallationsifthepipelineviewissettoshowmorethan200jobsCPUispushedto100%causingthesystemtofreezeTestedonasinglecoreWindows2008R2machine
runningJenkins1
.
596
.
Theproblem*seems*togetworseafterinstallingthelatestcore(1
.
with
599)duemaybetothelatestlogformatchanges(?)With
multiplecoresit*might*bepossibletoincreasethenumberofrowstobeshownwithoutanyissue.However,IthinkloadingbuildlogsatthisstageisCPUconsuming



























This message is automatically generated by JIRA.
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-plugin] (JENKINS-16202) Can't pass $BUILD_NUMBER to downstream build pipeline jobs.















































Libero Scarcelli
 started work on  JENKINS-16202


Cant pass $BUILD_NUMBER to downstream build pipeline jobs.
















Change By:


Libero Scarcelli
(18/Feb/15 7:48 AM)




Status:


Open
InProgress



























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







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

[JIRA] [build-pipeline-plugin] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline















































Libero Scarcelli
 commented on  JENKINS-20499


unable to retry job execution for failed job in build-pipeline















This one should be fixed now...



























This message is automatically generated by JIRA.
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-plugin] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline















































Libero Scarcelli
 started work on  JENKINS-20499


unable to retry job execution for failed job in build-pipeline
















Change By:


Libero Scarcelli
(18/Feb/15 7:54 AM)




Status:


Open
InProgress



























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







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

[JIRA] [build-pipeline-plugin] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline













































 
Libero Scarcelli
 edited a comment on  JENKINS-20499


unable to retry job execution for failed job in build-pipeline
















This one should be fixed now... but you need to update Core and pipeline plugin



























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







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

[JIRA] [subversion-plugin] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.

2015-02-17 Thread alexey.lar...@jeppesen.com (JIRA)















































Alexey Larsky
 commented on  JENKINS-22542


Subversion polling not work with externals or variables in URL -  E200015: No credential to try.















I have an issue only with lastest Subversion plugin 2.5 version.
Previos 2.4.5 works stable. You can install 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] [claim-plugin] (JENKINS-27002) Claim Stickiness default value should be configurable

2015-02-17 Thread bat...@batmat.net (JIRA)















































Baptiste Mathus
 commented on  JENKINS-27002


Claim Stickiness default value should be configurable















See https://github.com/jenkinsci/claim-plugin/pull/15



























This message is automatically generated by JIRA.
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-plugin] (JENKINS-16202) Can't pass $BUILD_NUMBER to downstream build pipeline jobs.
















































Libero Scarcelli
 closed  JENKINS-16202 as Fixed


Cant pass $BUILD_NUMBER to downstream build pipeline jobs.
















I guess we can close this one as the pipeline plugin has been able to pass parameters for quite some time now





Change By:


Libero Scarcelli
(18/Feb/15 7:50 AM)




Status:


InProgress
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] [beaker-builder-plugin] (JENKINS-27003) NullPointerException XMLEscapingVariableResolver.java:15

2015-02-17 Thread d...@djc.id.au (JIRA)















































Dan C
 commented on  JENKINS-27003


NullPointerException XMLEscapingVariableResolver.java:15















https://github.com/vjuranek/beaker-builder-plugin/pull/3



























This message is automatically generated by JIRA.
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] [claim-plugin] (JENKINS-27002) Claim Stickiness default value should be configurable

2015-02-17 Thread bat...@batmat.net (JIRA)















































Baptiste Mathus
 created  JENKINS-27002


Claim Stickiness default value should be configurable















Issue Type:


Bug



Assignee:


Baptiste Mathus



Components:


claim-plugin



Created:


18/Feb/15 5:48 AM



Description:


Hi,

I've had the request from coworkers that having claims be sticky by default does not somehow encourage "conscious" choice about claiming failed jobs. And this could lead to somehow lower quality standards (which is constantly fought against).

So I guess at least the Claim plugin could have a global option that would let users define their default behaviour for the claim stickiness.

I'm gonna file a PR for that one.

Thanks for that useful plugin!




Environment:


Jenkins 1.593




Project:


Jenkins



Labels:


configuration
quality




Priority:


Minor



Reporter:


Baptiste Mathus

























This message is automatically generated by JIRA.
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] [beaker-builder-plugin] (JENKINS-27003) NullPointerException XMLEscapingVariableResolver.java:15

2015-02-17 Thread d...@djc.id.au (JIRA)















































Dan C
 created  JENKINS-27003


NullPointerException XMLEscapingVariableResolver.java:15















Issue Type:


Bug



Assignee:


Dan C



Components:


beaker-builder-plugin



Created:


18/Feb/15 6:26 AM



Description:



FATAL: null
java.lang.NullPointerException
	at org.jenkinsci.plugins.beakerbuilder.XMLEscapingVariableResolver.resolve(XMLEscapingVariableResolver.java:15)
	at org.jenkinsci.plugins.beakerbuilder.XMLEscapingVariableResolver.resolve(XMLEscapingVariableResolver.java:5)
	at hudson.Util.replaceMacro(Util.java:160)
	at org.jenkinsci.plugins.beakerbuilder.JobSource.createDefaultJobFile(JobSource.java:65)
	at org.jenkinsci.plugins.beakerbuilder.FileJobSource.createJobFile(FileJobSource.java:53)
	at org.jenkinsci.plugins.beakerbuilder.BeakerBuilder.prepareJob(BeakerBuilder.java:130)
	at org.jenkinsci.plugins.beakerbuilder.BeakerBuilder.perform(BeakerBuilder.java:77)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)
	at hudson.model.Build$BuildExecution.build(Build.java:199)
	at hudson.model.Build$BuildExecution.doRun(Build.java:160)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533)
	at hudson.model.Run.execute(Run.java:1745)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:89)
	at hudson.model.Executor.run(Executor.java:240)


I'm guessing the inner VariableResolver can return null from .resolve() if the variable was undefined.




Environment:


Plugin version 1.6




Project:


Jenkins



Priority:


Minor



Reporter:


Dan C

























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







-- 
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] [claim-plugin] (JENKINS-27002) Claim Stickiness default value should be configurable

2015-02-17 Thread bat...@batmat.net (JIRA)















































Baptiste Mathus
 updated  JENKINS-27002


Claim Stickiness default value should be configurable
















Change By:


Baptiste Mathus
(18/Feb/15 6:32 AM)




Issue Type:


Bug
Improvement



























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

Won!

2015-02-17 Thread Mrs, Kate Muller




maduchieelo:
Congratulations you have won {£1,000.000.00 GBP} One million Great
Britain Pounds from our Microsoft 2015 Promotion, send the below
details for claims or you can call us for more details.

1. Full Name:...
2. Address:..
3. Nationality:.
5. Sex:
6.Occupation:
7. Phone/Fax:
8. Present Country:.

Agent:
Mrs.Kate Muller
E-mail:katemuller...@hotmail.com

--
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-plugin] (JENKINS-16202) Can't pass $BUILD_NUMBER to downstream build pipeline jobs.















































Libero Scarcelli
 commented on  JENKINS-16202


Cant pass $BUILD_NUMBER to downstream build pipeline jobs.















I guess we can close this one as the pipeline plugin has been able to pass parameters for quite some time now



























This message is automatically generated by JIRA.
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-plugin] (JENKINS-27001) On Windows installations if the pipeline view is set to show more than 200 jobs CPU is pushed to 100% causing the system to freeze















































Libero Scarcelli
 updated  JENKINS-27001


On Windows installations if the pipeline view is set to show more than 200 jobs CPU is pushed to 100% causing the system to freeze
















Change By:


Libero Scarcelli
(18/Feb/15 4:12 AM)




Description:


OnWindowsinstallationsifthepipelineviewissettoshowmorethan200jobsCPUispushedto100%causingthesystemtofreezeTestedonasinglecoreWindows2008R2machinerunningJenkins1.596.Theproblem*seems*togetworseafterinstallingthelatestcore(1.599atthisstage)duemaybetothelatestlogformatchanges(?)Withmultiplecoresit*might*bepossibletoincreasethenumberofrowstobeshownwithoutanyissue.
However,IthinkloadingbuildlogsatthisstageisCPUconsuming
..(?)



























This message is automatically generated by JIRA.
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-26571) Job page becomes un responsive when there are a lot of builds in the queue

2015-02-17 Thread ar...@hortonworks.com (JIRA)















































Arpit Gupta
 commented on  JENKINS-26571


Job page becomes un responsive when there are a lot of builds in the queue















@Tom it is not as bad as before but the scrolling is not smooth. Atleast the above JS error goes away once i click stop using the script button. I will try to replicate it and post a recording. Since this is our production jenkins its difficult to create this scenario on demand .



























This message is automatically generated by JIRA.
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] [android-emulator-plugin] (JENKINS-23688) Headless Linux and Valid ABIs: no ABIs.















































Christopher Orr
 commented on  JENKINS-23688


Headless Linux and Valid ABIs: no ABIs.















This should be fixed, and will be in the next plugin release.

If you want to test this in the meantime, you can download the ".hpi" file from the following link, then you can upload it to your Jenkins instance via the Plugin Manager  Advanced  Upload; you will then need to restart Jenkins:
https://jenkins.ci.cloudbees.com/job/plugins/job/android-emulator-plugin/lastStableBuild/org.jenkins-ci.plugins$android-emulator/



























This message is automatically generated by JIRA.
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-plugin] (JENKINS-26994) Post-build task fails if job is aborted

2015-02-17 Thread william.vilp...@gmail.com (JIRA)















































william vilpoix
 commented on  JENKINS-26994


Post-build task fails if job is aborted















My mistake  the temp script
hudson.bat is written in the folder



























This message is automatically generated by JIRA.
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-17514) NullPointerException: no workspace from node hudson.slaves.DumbSlave after upgrade to 1.510

2015-02-17 Thread pjdar...@java.net (JIRA)















































pjdarton
 commented on  JENKINS-17514


NullPointerException: no workspace from node hudson.slaves.DumbSlave after upgrade to 1.510















I'm seeing this a bit on my jobs that use the DSL Plugin.
I've got hundreds of other jobs that all seem (no promises, but I've not noticed this problem with them...) to work fine - it's just the DSL-plugin-using jobs that seem to (sometimes) fail like this (it doesn't always happen; it's usually fine, but I'm seeing this often enough to google for this error...)

I'm using Jenkins version 1.559 (running on Windows server 2008, with many Windows 7 slaves that run the Jenkins slave process as a service), and my DSL plugin build failed with the error:


Existing Templates: 
New Templates: 
Unreferenced Templates: 
Adding items: 
Existing items: GeneratedJob{jobName='foo', templateName=none},GeneratedJob{jobName='bar', templateName=none}
Removing items: 
Adding views: 
Existing views: GeneratedJob{viewName='Foo'}
Removing views: 
Adding config files: 
Existing config files: 
Removing config files: 
FATAL: no workspace from node hudson.slaves.DumbSlave@2a6a31b which is computer hudson.slaves.SlaveComputer@ac2c5d14 and has channel null
java.lang.NullPointerException: no workspace from node hudson.slaves.DumbSlave@2a6a31b which is computer hudson.slaves.SlaveComputer@ac2c5d14 and has channel null
	at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:76)
	at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
	at hudson.model.Build$BuildExecution.build(Build.java:198)
	at hudson.model.Build$BuildExecution.doRun(Build.java:159)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:523)
	at hudson.model.Run.execute(Run.java:1700)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:231)




























This message is automatically generated by JIRA.
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-plugin] (JENKINS-26993) GIT Plugin requires /tmp to be executable

2015-02-17 Thread ja...@ds2000.org (JIRA)















































David Shaw
 created  JENKINS-26993


GIT Plugin requires /tmp to be executable















Issue Type:


Bug



Assignee:


Nicolas De Loof



Components:


git-plugin



Created:


17/Feb/15 2:04 PM



Description:


We believe that the jenkins GIT plugin requires the /tmp on the jenkins nodes to be executable.  Is there anyway we can change this location as it is against our security policy to not have temp locked down.  

Thanks, if a bug is not the correct method to report this I do apologise.

Thanks

Dave




Environment:


2.2.12	2.2.7




Project:


Jenkins



Priority:


Minor



Reporter:


David Shaw

























This message is automatically generated by JIRA.
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] [disk-usage-plugin] (JENKINS-26995) NPE

2015-02-17 Thread gentoo.inte...@gmail.com (JIRA)















































Kanstantsin Shautsou
 commented on  JENKINS-26995


NPE















@lycie, please run findbugs and put annotations for NPE exception checks.



























This message is automatically generated by JIRA.
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] [android-emulator-plugin] (JENKINS-25790) New adb connect command always fails to connect emulator on OS X















































Christopher Orr
 commented on  JENKINS-25790


New adb connect command always fails to connect emulator on OS X















If you could try the build linked to here, that would be great:
https://issues.jenkins-ci.org/browse/JENKINS-11952?focusedCommentId=221787#comment-221787



























This message is automatically generated by JIRA.
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] [performance-plugin] (JENKINS-26988) Responding time graphs should not ignore samples with errors

2015-02-17 Thread guus.der.kinde...@gmail.com (JIRA)















































Guus der Kinderen
 commented on  JENKINS-26988


Responding time graphs should not ignore samples with errors















A fix for this issue is presented in pull request #45: https://github.com/jenkinsci/performance-plugin/pull/45



























This message is automatically generated by JIRA.
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] [android-emulator-plugin] (JENKINS-26930) Emulator fails to start with bogus error message















































Christopher Orr
 commented on  JENKINS-26930


Emulator fails to start with bogus error message















Hmm. I couldn't reproduce this with the newest SDK tools on my Ubuntu 14.04 x86_64 machine (nor in a Docker image with Ubuntu 12.04), but it's strange that you get a different result on the command line.

In the command line version, are you running as the same user that Jenkins is running under?

Does the same happen if you run a Jenkins job, where you manually run the emulator command via a "Execute shell script" build step?

Is there anything weird in the build's environment, e.g. env variables injected globally in Jenkins (or on that particular build slave)?  Probably you can see this by running env in an execute shell build step.



























This message is automatically generated by JIRA.
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] [packer-plugin] (JENKINS-26966) Unable to build packer image from subdirectory

2015-02-17 Thread jeffreydam...@gmail.com (JIRA)
















































Jeffrey Damick
 assigned  JENKINS-26966 to Jeffrey Damick



Unable to build packer image from subdirectory
















Change By:


Jeffrey Damick
(17/Feb/15 1:59 PM)




Assignee:


JeffreyDamick



























This message is automatically generated by JIRA.
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] [disk-usage-plugin] (JENKINS-26995) NPE

2015-02-17 Thread gentoo.inte...@gmail.com (JIRA)















































Kanstantsin Shautsou
 created  JENKINS-26995


NPE















Issue Type:


Bug



Assignee:


Lucie Votypkova



Components:


disk-usage-plugin



Created:


17/Feb/15 3:05 PM



Description:



Feb 17, 2015 2:45:53 PM WARNING hudson.ExpressionFactory2$JexlExpression evaluate
Caught exception evaluating: it.getBuildUsageString() in /job/some-job/. Reason: java.lang.NullPointerException
java.lang.NullPointerException
	at hudson.plugins.disk_usage.BuildDiskUsageAction.getDiskUsage(BuildDiskUsageAction.java:83)
	at hudson.plugins.disk_usage.BuildDiskUsageAction.getAllDiskUsage(BuildDiskUsageAction.java:92)
	at hudson.plugins.disk_usage.BuildDiskUsageAction.getBuildUsageString(BuildDiskUsageAction.java:101)
	at sun.reflect.GeneratedMethodAccessor412.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258)
	at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104)
	at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
	at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
	at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
	at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
	at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74)
	at org.apache.commons.jelly.impl.ExpressionScript.run(ExpressionScript.java:66)
	at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
	at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
	at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95)
	at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147)
	at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
	at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
	at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
	at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
	at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
	at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98)
	at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
	at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
	at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
	at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
	at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
	at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
	at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95)
	at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147)
	at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
	at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
	at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
	at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
	at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
	at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
	at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95)
	at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147)
	at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
	at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
	at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
	at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95)
	at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147)
	at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
	at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
	at

[JIRA] [other] (JENKINS-2107) email notification when disk space runs low.

2015-02-17 Thread timothy.br...@dematic.com (JIRA)















































Tim Bradt
 commented on  JENKINS-2107


email notification when disk space runs low.















Perspective.  Technically I agree that no build is impacted by marking a node offline - I can address the issue and resume the build.  However, my issue is that I have a department full of developers and ScrumMasters that are relying on our full nightly build being completed and waiting when they come in the next day.  I can't afford to fall below my threshold and queue up the remainder of that process due to offline node.  So my non-technical perspective (and that of my management I expect) is that I effectively failed the build/deploy/test process by causing a significant delay.  Big impact on human resources.

I agree that a soft/warning threshold would meet the requirement for a proactive solution that doesn't suspend a running build.



























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







-- 
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-plugin] (JENKINS-26994) Post-build task fails if job is aborted

2015-02-17 Thread william.vilp...@gmail.com (JIRA)















































william vilpoix
 created  JENKINS-26994


Post-build task fails if job is aborted















Issue Type:


Bug



Assignee:


Unassigned


Components:


postbuild-task-plugin



Created:


17/Feb/15 2:34 PM



Description:


Jenkins is running on a windows 2003 server
In the job config postbuild task part:
log text : .
script : dir
When the job is successed or failed, the postbuild task works fine

When the job is aborted (manually stopped or timeout case) I get this kind of logs:
Running script  :dir
workspace $ cmd /c call C:\Users\XXX\AppData\Local\Temp\2\hudson13287273761205392.bat
Exception when executing the batch command : null
Build step 'Post build task' marked build as failure
Finished: ABORTED

C:\Users\XXX\AppData\Local\Temp\2 is the java.io.tmpdir data

I ran a non-stop script listing files in this folder, the temp script
hudson.bat is never written in this folder


in the jenkins log  I have a java exception generated each time a job is aborted :
java.lang.InterruptedException
	at java.lang.ProcessImpl.waitFor(Native Method)
	at hudson.Proc$LocalProc.join(Proc.java:319)
	at hudson.Launcher$ProcStarter.join(Launcher.java:345)
	at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:82)
	at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:58)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
	at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:710)
	at hudson.model.Build$RunnerImpl.build(Build.java:178)
	at hudson.model.Build$RunnerImpl.doRun(Build.java:139)
	at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:480)
	at hudson.model.Run.run(Run.java:1438)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:239)

It is a main issue in my professional project.
>From my web research it appears that post build task is supposed to work fine even when the job is aborted




Environment:


Jenkins 1.466.1 

postbuild-task plugin 1.8




Project:


Jenkins



Priority:


Major



Reporter:


william vilpoix

























This message is automatically generated by JIRA.
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-14332) Repeated channel/timeout errors from Jenkins slave

2015-02-17 Thread bert...@jpoint.nl (JIRA)















































Bert Jan Schrijver
 commented on  JENKINS-14332


Repeated channel/timeout errors from Jenkins slave















Downgrading the kernel on the master has definitely fixed it for us.
Running for a week now without any trouble.



























This message is automatically generated by JIRA.
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] [performance-plugin] (JENKINS-16627) Fail to parse jmeter report

2015-02-17 Thread guus.der.kinde...@gmail.com (JIRA)















































Guus der Kinderen
 commented on  JENKINS-16627


Fail to parse jmeter report 















A fix for this issue is provided in pull request #45: https://github.com/jenkinsci/performance-plugin/pull/45



























This message is automatically generated by JIRA.
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-26983) On MacOSX, pkg installation reset the daemon defaults values
















































Daniel Beck
 resolved  JENKINS-26983 as Duplicate


On MacOSX, pkg installation reset the daemon defaults values 
















Duplicates JENKINS-26982





Change By:


Daniel Beck
(17/Feb/15 1:32 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























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







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

[JIRA] [core] (JENKINS-23543) Launchctl does not load Jenkins on OS X 10.10 Yosemite
















































Daniel Beck
 resolved  JENKINS-23543 as Duplicate


Launchctl does not load Jenkins on OS X 10.10 Yosemite
















Resolved as JENKINS-26982, so resolving as duplicate of that.





Change By:


Daniel Beck
(17/Feb/15 1:34 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























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







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

[JIRA] [android-emulator-plugin] (JENKINS-23600) SDK repositories and emulator images do not install















































Christopher Orr
 commented on  JENKINS-23600


SDK repositories and emulator images do not install 















This should be fixed, and there will be a release soon.

See the current latest comment on JENKINS-23688 if you want to try out a recent build of the plugin.



























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







-- 
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] [ec2-plugin] (JENKINS-23705) EC2 slave disconnects on longer running builds

2015-02-17 Thread bert...@jpoint.nl (JIRA)















































Bert Jan Schrijver
 commented on  JENKINS-23705


EC2 slave disconnects on longer running builds















Yes, downgrading the kernel on the master has definitely fixed it for us. 
Running for a week now without any trouble.



























This message is automatically generated by JIRA.
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] [other] (JENKINS-2107) email notification when disk space runs low.

Daniel Beck
commented on JENKINS-2107

email notification when disk space runs low.

How are any further jobs supposed to be executed on an offline node? Coming in the next day with the remainder of my build jobs queued up due to falling below the disk space threshold is not desirable. Effectively that is a failed build.

You wrote:

… have a build in progress when free disk space falls below the setting, and then the node will be taken offline. … I want to be proactive, … BEFORE it impacts a single build.

A build that is already in progress is never impacted by marking a node offline. Hence my interpretation that you thought node monitors disconnected nodes. Re-reading that, I probably misunderstood that last part to mean the build in progress, rather than any build.

So there should probably be two thresholds for every node monitor: One soft (admin monitor preferably, i.e. a warning on the /manage page), one hard (marking the node offline).

[JIRA] [build-pipeline-plugin] (JENKINS-25391) Cannot delete project















































Daniel Beck
 commented on  JENKINS-25391


Cannot delete project















Build Pipeline had horrible input validation and related failures for a while. Basically, create a Build Pipeline view and don't enter anything will result in breakage. Don't know whether that has been 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] [android-emulator-plugin] (JENKINS-23612) Failed to run AVD creation command