[JIRA] (JENKINS-17349) CPU on master node keeps increasing and never come down
sharon xia created JENKINS-17349 CPU on master node keeps increasing and never come down Issue Type: Bug Assignee: wolfs Attachments: JavaMelody__CNRDGPS_3_26_13 (1).pdf Components: all-changes Created: 26/Mar/13 3:00 AM Description: We are using Jenkins ver. 1.480.3, upgraded on Mar 1st. During the past month, the CPU usage continuously creasing... The 1st week: <5% The 2ed week: ~=17% The 3ed week: ~= 25%, And today it increasd to ~= 44%!!! Due Date: 26/Mar/13 12:00 AM Environment: Jenkins ver. 1.480.3 Java memory used: 170 Mb / 910 Mb Nb of http sessions: 7 Nb of active threads (current http requests): 0 Details OS: Windows Server 2008 R2 , amd64/64 (16 cores) Java: Java(TM) SE Runtime Environment, 1.6.0_23-b05 JVM: Java HotSpot(TM) 64-Bit Server VM, 19.0-b09, mixed mode PID of process: 1416 Server: Winstone Servlet Engine v0.9.10 Webapp context: Start: 3/2/13 4:51 AM JVM arguments: -Xrs -Xmx1024m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle Mean age of http sessions (min): 194 Memory: Non heap memory = 104 Mb (Perm Gen, Code Cache), Loaded classes = 12,501, Garbage collection time = 530,283 ms, Process cpu time = 4,929,846,038 ms, Committed virtual memory = 967 Mb, Free physical memory = 11,554 Mb, Total physical memory = 16,371 Mb, Free swap space = 28,954 Mb, Total swap space = 32,740 Mb Perm Gen memory: 81 Mb / 82 Mb Free disk space: 1,762,773 Mb Dependencies: 110 dependencies ; Project: Jenkins Labels: jenkins Priority: Critical Reporter: sharon xia This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17337) Failed to load job on Matrix jobs
Bao Xiaopan(Bob) edited a comment on JENKINS-17337 Failed to load job on Matrix jobs I have to reopen this issue coz I still met this problem after upgrade to 1.508, pls check it asap, my env is: Linux r49d05001.xy2.aliyun.com 2.6.18-164.11.1.el5 #1 SMP Wed Jan 6 13:26:04 EST 2010 x86_64 x86_64 x86_64 GNU/Linux following is the logs: SEVERE: Failed Loading job xxx.Deploy-WS.ci02 java.lang.NullPointerException at hudson.plugins.promoted_builds.JobPropertyImpl.getItem(JobPropertyImpl.java:220) at hudson.plugins.promoted_builds.JobPropertyImpl.getItem(JobPropertyImpl.java:41) at hudson.model.AbstractProject.onLoad(AbstractProject.java:291) at hudson.model.Items.load(Items.java:221) at hudson.model.ItemGroupMixIn.loadChildren(ItemGroupMixIn.java:99) at hudson.plugins.promoted_builds.JobPropertyImpl.setOwner(JobPropertyImpl.java:145) at hudson.plugins.promoted_builds.JobPropertyImpl.setOwner(JobPropertyImpl.java:41) at hudson.model.Job.onLoad(Job.java:201) at hudson.model.AbstractProject.onLoad(AbstractProject.java:282) at hudson.model.Project.onLoad(Project.java:83) at hudson.model.Items.load(Items.java:221) at jenkins.model.Jenkins$17.run(Jenkins.java:2552) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:887) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17337) Failed to load job on Matrix jobs
Bao Xiaopan(Bob) edited a comment on JENKINS-17337 Failed to load job on Matrix jobs I have to reopen this issue coz I still met this problem after upgrade to 1.508, pls check it asap, following is the logs: SEVERE: Failed Loading job xxx.Deploy-WS.ci02 java.lang.NullPointerException at hudson.plugins.promoted_builds.JobPropertyImpl.getItem(JobPropertyImpl.java:220) at hudson.plugins.promoted_builds.JobPropertyImpl.getItem(JobPropertyImpl.java:41) at hudson.model.AbstractProject.onLoad(AbstractProject.java:291) at hudson.model.Items.load(Items.java:221) at hudson.model.ItemGroupMixIn.loadChildren(ItemGroupMixIn.java:99) at hudson.plugins.promoted_builds.JobPropertyImpl.setOwner(JobPropertyImpl.java:145) at hudson.plugins.promoted_builds.JobPropertyImpl.setOwner(JobPropertyImpl.java:41) at hudson.model.Job.onLoad(Job.java:201) at hudson.model.AbstractProject.onLoad(AbstractProject.java:282) at hudson.model.Project.onLoad(Project.java:83) at hudson.model.Items.load(Items.java:221) at jenkins.model.Jenkins$17.run(Jenkins.java:2552) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:887) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17337) Failed to load job on Matrix jobs
Bao Xiaopan(Bob) reopened JENKINS-17337 Failed to load job on Matrix jobs I still met this problem after upgrade to 1.508, following is the logs: SEVERE: Failed Loading job xxx.Deploy-WS.ci02 java.lang.NullPointerException at hudson.plugins.promoted_builds.JobPropertyImpl.getItem(JobPropertyImpl.java:220) at hudson.plugins.promoted_builds.JobPropertyImpl.getItem(JobPropertyImpl.java:41) at hudson.model.AbstractProject.onLoad(AbstractProject.java:291) at hudson.model.Items.load(Items.java:221) at hudson.model.ItemGroupMixIn.loadChildren(ItemGroupMixIn.java:99) at hudson.plugins.promoted_builds.JobPropertyImpl.setOwner(JobPropertyImpl.java:145) at hudson.plugins.promoted_builds.JobPropertyImpl.setOwner(JobPropertyImpl.java:41) at hudson.model.Job.onLoad(Job.java:201) at hudson.model.AbstractProject.onLoad(AbstractProject.java:282) at hudson.model.Project.onLoad(Project.java:83) at hudson.model.Items.load(Items.java:221) at jenkins.model.Jenkins$17.run(Jenkins.java:2552) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:887) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Change By: Bao Xiaopan(Bob) (26/Mar/13 2:51 AM) 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/groups/opt_out.
[JIRA] (JENKINS-15319) Failure starting slave nodes
John Dyer commented on JENKINS-15319 Failure starting slave nodes Anyone ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12076) m2 Release Plugin lock builds
David Venable edited a comment on JENKINS-12076 m2 Release Plugin lock builds This feature does not work from the master branch of GitHub due to an incorrect constructor argument name. I created a pull request on GitHub which fixes it. https://github.com/jenkinsci/m2release-plugin/pull/10 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12076) m2 Release Plugin lock builds
David Venable commented on JENKINS-12076 m2 Release Plugin lock builds This feature does not work from the master branch of GitHub due to an incorrect constructor argument name. This prevents the current code from locking any builds (since the default is zero). I created a pull request on GitHub which fixes it. https://github.com/jenkinsci/m2release-plugin/pull/10 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17348) Git Plugin: Fast-Remote Polling Does not Filter Branch Name
Andrew Schurman
commented on JENKINS-17348
Git Plugin: Fast-Remote Polling Does not Filter Branch Name
Debugging has shown the problem in and about in compareRemoteRevisionWithImpl(..) in GitSCM:
final String singleBranch = getSingleBranch(lastBuild);
...
String gitRepo = getParamExpandedRepos(lastBuild).get(0).getURIs().get(0).toString();
ObjectId head = git.getHeadRev(gitRepo, getBranches().get(0).getName());
if (head != null && buildData.lastBuild.getRevision().getSha1().name().equals(head.name())) {
Here singleBranch is able to resolve the branch as a build parameter (in the getSingleBranch(..)), but head always will resolve to null as the branch name is given as a parameter which obviously won't exist in the remote git repo.
It looks like the branch name for head just needs to be filtered in the same ways getSingleBranch(..) does to accept build parameters.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17347) xpath functions are broken in API (Error 330 (net::ERR_CONTENT_DECODING_FAILED): Unknown error. is back)
Ivan Kurnosov updated JENKINS-17347 xpath functions are broken in API (Error 330 (net::ERR_CONTENT_DECODING_FAILED): Unknown error. is back) Change By: Ivan Kurnosov (26/Mar/13 1:47 AM) Component/s: core Component/s: copyartifact This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17347) xpath functions are broken in API (Error 330 (net::ERR_CONTENT_DECODING_FAILED): Unknown error. is back)
Ivan Kurnosov updated JENKINS-17347 xpath functions are broken in API (Error 330 (net::ERR_CONTENT_DECODING_FAILED): Unknown error. is back) Change By: Ivan Kurnosov (26/Mar/13 1:46 AM) Description: The functions (ie `text()`) are broken in API 's xpath .Example: https://ci.jenkins-ci.org/view/Jenkins%20core/api/xml?xpath=/listView/job[1]/name/text()Expected: "core_selenium-test"Actual: Error 330 (net::ERR_CONTENT_DECODING_FAILED): Unknown error. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17145) URLTrigger gives severe error message, envinject NPE
dmeibusch commented on JENKINS-17145 URLTrigger gives severe error message, envinject NPE Just confirming, Jenkins reports that we have v0.28. Stack trace look pretty similar to above. Almost 100% sure now that we only see this exception when our slaves are idled down. java.lang.NullPointerException at org.jenkinsci.lib.envinject.service.EnvVarsResolver.gatherEnvVarsNode(EnvVarsResolver.java:160) at org.jenkinsci.lib.envinject.service.EnvVarsResolver.getDefaultEnvVarsJob(EnvVarsResolver.java:89) at org.jenkinsci.lib.envinject.service.EnvVarsResolver.getEnVars(EnvVarsResolver.java:68) at org.jenkinsci.lib.envinject.service.EnvVarsResolver.getPollingEnvVars(EnvVarsResolver.java:36) at org.jenkinsci.plugins.urltrigger.URLTrigger.getURLValue(URLTrigger.java:108) at org.jenkinsci.plugins.urltrigger.URLTrigger.checkIfModifiedEntry(URLTrigger.java:136) at org.jenkinsci.plugins.urltrigger.URLTrigger.checkIfModified(URLTrigger.java:125) at org.jenkinsci.lib.xtrigger.AbstractTrigger$Runner.run(AbstractTrigger.java:197) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17145) URLTrigger gives severe error message, envinject NPE
Gregory Boissinot commented on JENKINS-17145 URLTrigger gives severe error message, envinject NPE Please could you add again the stacktrace with URLTrigger 0.28? It seems your posted strack trace doesn't match the version and therefore I cannot try to identify the right error. Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17343) Jenkins is no more WinXP compliant : CreateSymbolicLinkW is not available
Joshua Masek commented on JENKINS-17343 Jenkins is no more WinXP compliant : CreateSymbolicLinkW is not available I also have this issue. I run Jenkins on 32bit Windows Server 2003. Also upgraded to 1.507 from 1.505. FATAL: Error looking up function 'CreateSymbolicLinkW': The specified procedure could not be found. java.lang.UnsatisfiedLinkError: Error looking up function 'CreateSymbolicLinkW': The specified procedure could not be found. at com.sun.jna.Function.(Function.java:179) at com.sun.jna.NativeLibrary.getFunction(NativeLibrary.java:347) at com.sun.jna.NativeLibrary.getFunction(NativeLibrary.java:327) at com.sun.jna.Library$Handler.invoke(Library.java:203) at $Proxy29.CreateSymbolicLinkW(Unknown Source) at hudson.util.jna.Kernel32Utils.createSymbolicLink(Kernel32Utils.java:85) at hudson.Util.createSymlink(Util.java:1048) at hudson.model.Run.execute(Run.java:1573) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17345) generatedJUnitFiles does not exist
Gregory Boissinot resolved JENKINS-17345 as Fixed generatedJUnitFiles does not exist Change By: Gregory Boissinot (25/Mar/13 10:33 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17345) generatedJUnitFiles does not exist
SCM/JIRA link daemon commented on JENKINS-17345 generatedJUnitFiles does not exist Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/xunit/XUnitPublisher.java http://jenkins-ci.org/commit/xunit-plugin/6310527830b1c2495339cbd2ec459c14e80b5daf Log: Fix JENKINS-17345 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-3265) Reload Configuration from Disk (or POSTing config.xml) loses info on running builds
dogfood commented on JENKINS-3265 Reload Configuration from Disk (or POSTing config.xml) loses info on running builds Integrated in jenkins_main_trunk #2411 [FIXED JENKINS-3265] Hotfix for regression in matrix project loading from 25084f5.(cherry picked from commit 3370e6edf5e0e7c7a8cf22e4a7a5decc24c45205) (Revision 6b1f8d1aaa2179c99af33a8d60851abd032442ac) Result = SUCCESS kohsuke : 6b1f8d1aaa2179c99af33a8d60851abd032442ac Files : core/src/main/java/hudson/matrix/MatrixProject.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17337) Failed to load job on Matrix jobs
dogfood commented on JENKINS-17337 Failed to load job on Matrix jobs Integrated in jenkins_main_trunk #2411 JENKINS-17337 Added test for NPE.(cherry picked from commit 1bf958afb196d0c56b37f00681027a549d0c9189) (Revision 18b5f4f13377349b1c249c2f62d11966c5b7dd9d) Revert "JENKINS-17337 Added test for NPE.(cherry picked from commit 1bf958afb196d0c56b37f00681027a549d0c9189)" (Revision 991cac9debfc87fbc5f4e664e6ae0c73f7eb1cf6) Result = SUCCESS kohsuke : 18b5f4f13377349b1c249c2f62d11966c5b7dd9d Files : test/src/test/groovy/hudson/matrix/MatrixProjectTest.groovy kohsuke : 991cac9debfc87fbc5f4e664e6ae0c73f7eb1cf6 Files : test/src/test/groovy/hudson/matrix/MatrixProjectTest.groovy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17337) Failed to load job on Matrix jobs
SCM/JIRA link daemon commented on JENKINS-17337 Failed to load job on Matrix jobs Code changed in jenkins User: Kohsuke Kawaguchi Path: test/src/test/groovy/hudson/matrix/MatrixProjectTest.groovy http://jenkins-ci.org/commit/jenkins/991cac9debfc87fbc5f4e664e6ae0c73f7eb1cf6 Log: Revert "JENKINS-17337 Added test for NPE.(cherry picked from commit 1bf958afb196d0c56b37f00681027a549d0c9189)" This reverts commit 18b5f4f13377349b1c249c2f62d11966c5b7dd9d. It looks like this change depends on other test harness related changes. It doesn't build on this branch. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-10274) Can this plugin support CLOC for even more languages and better Windows support
Adam Westhusing resolved JENKINS-10274 as Won't Fix Can this plugin support CLOC for even more languages and better Windows support Nevermind, I wasn't following the directions properly. Once I used xsltproc this worked as expected. Sorry! Change By: Adam Westhusing (25/Mar/13 8:44 PM) Status: Reopened Resolved Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15103) jenkins slave process does not let go of .git\objects\pack\*.pack file causeing "Unable to delete" when wiping workspace
Abdelrahman Elogeel commented on JENKINS-15103 jenkins slave process does not let go of .git\objects\pack\*.pack file causeing "Unable to delete" when wiping workspace This issue really affects our projects, we had lot of projects failing because of this issue. Please consider fixing it soon. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17341) Promoted builds throw NullPointerException after upgrade to 1.507
Josh Davidson commented on JENKINS-17341 Promoted builds throw NullPointerException after upgrade to 1.507 Same problem here This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12821) android.device
SCM/JIRA link daemon commented on JENKINS-12821 android.device Code changed in jenkins User: Richard Mortimer Path: src/main/java/org/jvnet/hudson/plugins/port_allocator/PortAllocationManager.java src/test/java/org/jvnet/hudson/plugins/port_allocator/PortAllocationManagerTest.java http://jenkins-ci.org/commit/port-allocator-plugin/007ca2616293ece2e033070e4e0ad13253eecd0a Log: Add PortAllocationManager#allocateConsecutivePortRange to allow multiple ports to be allocated together within a specific range of ports. This forms part of the fix for JENKINS-12821 in android-emulator-plugin.. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17346) git project building twice every time new change committed
Marc Chapman created JENKINS-17346 git project building twice every time new change committed Issue Type: Bug Assignee: Nicolas De Loof Attachments: Screen Shot 2013-03-25 at 1.06.25 PM.png, Screen Shot 2013-03-25 at 1.06.38 PM.png, Screen Shot 2013-03-25 at 1.06.51 PM.png, Screen Shot 2013-03-25 at 1.18.37 PM.png Components: git Created: 25/Mar/13 8:19 PM Description: Running git-plugin 1.3.0, git-client-plugin 1.0.5, jenkins version 1.506 Whenever I check in, my build will trigger twice (but only 2 times, never more than that). I've tried limiting to specific branches, and adding different refspecs, but nothing has seemed to work. I have attached 3 screenshots. The first is the build information page on the first build. Please note that it says, "2 times" The 2nd is the polling log for the first build. The 3rd is the polling log for the 2nd build. I find that if I watch the polling, the build does not seem to trigger right away and spends some time resetting itself in the quiet period. Once it triggers, it usually triggers with 2 builds to do right away, which can be viewed in the 4th picture. Environment: MacOS Project: Jenkins Priority: Major Reporter: Marc Chapman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17341) Promoted builds throw NullPointerException after upgrade to 1.507
Jason Swager commented on JENKINS-17341 Promoted builds throw NullPointerException after upgrade to 1.507 Also experiencing the same problem: Jenkins 1.507 and Promoted plugin 2.8. Using Win2008R2 Server though. Raised issue to Critical priority. Any jobs that use the plugin will be appear to have been deleted from Jenkins. Reverting Jenkins resolved the problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17341) Promoted builds throw NullPointerException after upgrade to 1.507
Jason Swager updated JENKINS-17341 Promoted builds throw NullPointerException after upgrade to 1.507 Change By: Jason Swager (25/Mar/13 8:07 PM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17311) Expand and encourage use of hash syntax in crontabs
dogfood commented on JENKINS-17311 Expand and encourage use of hash syntax in crontabs Integrated in jenkins_main_trunk #2410 Result = SUCCESS This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-7291) Flyweight jobs and zero executors
dogfood commented on JENKINS-7291 Flyweight jobs and zero executors Integrated in jenkins_main_trunk #2410 Result = SUCCESS This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17337) Failed to load job on Matrix jobs
SCM/JIRA link daemon commented on JENKINS-17337 Failed to load job on Matrix jobs Code changed in jenkins User: Jesse Glick Path: test/src/test/groovy/hudson/matrix/MatrixProjectTest.groovy http://jenkins-ci.org/commit/jenkins/18b5f4f13377349b1c249c2f62d11966c5b7dd9d Log: JENKINS-17337 Added test for NPE.(cherry picked from commit 1bf958afb196d0c56b37f00681027a549d0c9189) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-3265) Reload Configuration from Disk (or POSTing config.xml) loses info on running builds
SCM/JIRA link daemon commented on JENKINS-3265 Reload Configuration from Disk (or POSTing config.xml) loses info on running builds Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/matrix/MatrixProject.java http://jenkins-ci.org/commit/jenkins/6b1f8d1aaa2179c99af33a8d60851abd032442ac Log: [FIXED JENKINS-3265] Hotfix for regression in matrix project loading from 25084f5.(cherry picked from commit 3370e6edf5e0e7c7a8cf22e4a7a5decc24c45205) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17345) generatedJUnitFiles does not exist
John Kelly created JENKINS-17345 generatedJUnitFiles does not exist Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: xunit Created: 25/Mar/13 7:09 PM Description: When I run my build, xUnit logs that the generatedJUnitFiles directory does not exist. My build doesn't create or reference this directory so this must be something xUnit is trying to create? [xUnit] [INFO] - Starting to record. ERROR: Publisher org.jenkinsci.plugins.xunit.XUnitPublisher aborted due to exception /var/lib/jenkins/jobs/Functional-Production/workspace/generatedJUnitFiles does not exist. at org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractFileSet.java:483) at org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractFileSet.java:460) at org.jenkinsci.plugins.xunit.XUnitPublisher$4.invoke(XUnitPublisher.java:292) at org.jenkinsci.plugins.xunit.XUnitPublisher$4.invoke(XUnitPublisher.java:287) at hudson.FilePath.act(FilePath.java:865) at hudson.FilePath.act(FilePath.java:838) at org.jenkinsci.plugins.xunit.XUnitPublisher.getTestResult(XUnitPublisher.java:287) at org.jenkinsci.plugins.xunit.XUnitPublisher.recordTestResult(XUnitPublisher.java:249) at org.jenkinsci.plugins.xunit.XUnitPublisher.performXUnit(XUnitPublisher.java:123) at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(XUnitPublisher.java:93) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:820) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:792) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:739) at hudson.model.Run.execute(Run.java:1592) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Environment: xUnit 1.52 Jenkins 1.506 Project: Jenkins Priority: Critical Reporter: John Kelly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17337) Failed to load job on Matrix jobs
dogfood commented on JENKINS-17337 Failed to load job on Matrix jobs Integrated in jenkins_main_trunk #2408 JENKINS-17337 Added test for NPE. (Revision 1bf958afb196d0c56b37f00681027a549d0c9189) Result = UNSTABLE Jesse Glick : 1bf958afb196d0c56b37f00681027a549d0c9189 Files : test/src/test/groovy/hudson/matrix/MatrixProjectTest.groovy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-7291) Flyweight jobs and zero executors
SCM/JIRA link daemon commented on JENKINS-7291 Flyweight jobs and zero executors Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/src/main/java/hudson/model/AbstractCIBase.java core/src/main/java/hudson/model/Computer.java core/src/main/java/hudson/model/Queue.java core/src/main/java/hudson/slaves/SlaveComputer.java core/src/main/java/jenkins/model/Jenkins.java core/src/main/resources/lib/hudson/executors.jelly test/src/test/java/hudson/model/QueueTest.java http://jenkins-ci.org/commit/jenkins/a114c693bc61c564232e78c9fffb5de1ef946ea8 Log: [FIXED JENKINS-7291] Permit flyweight tasks to run on master even when it has zero configured executors. Always adding Computer for master as a fallback The original proposed fix for JENKINS-7291 creates a Computer object transitively. This seems unwise as it violates the design of Computer as stated in the javadoc, and for example we can end up creating two Computers for the master. I think a better fix is to create a Computer for the master all the time, even if there's no executors configured. The discrimination in Queue.makeBuildable would ensure that such phantom Computer is only used as a last resort (statistically speaking). I've also tweaked executors.jelly a bit. I simplified it somewhat based on the idea that "if there's only one computer to show, the context is likely making it obvious". (I must be missing the intricacy in the current code.) Originally developed in a branch at 2c5b57fcc1f39ed39057254e802f4183db5aa0dc then squashed for clarity. – You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-7291) Flyweight jobs and zero executors
SCM/JIRA link daemon resolved JENKINS-7291 as Fixed Flyweight jobs and zero executors Change By: SCM/JIRA link daemon (25/Mar/13 6:23 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/groups/opt_out.
[JIRA] (JENKINS-17311) Expand and encourage use of hash syntax in crontabs
SCM/JIRA link daemon commented on JENKINS-17311 Expand and encourage use of hash syntax in crontabs Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html http://jenkins-ci.org/commit/jenkins/c4760b472c8c54c874b043502a1a6892532ba07a Log: recording JENKINS-17311 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-5790) Parameterize Tomcat Context Path and URL Fields
Scott Ellis commented on JENKINS-5790 Parameterize Tomcat Context Path and URL Fields Add me as an interested party in this feature. I have three different servers to which I deploy an application, and it looks like I am going to have to create a job for each one. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-7291) Flyweight jobs and zero executors
SCM/JIRA link daemon commented on JENKINS-7291 Flyweight jobs and zero executors Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/hudson/model/AbstractCIBase.java core/src/main/java/hudson/model/Computer.java core/src/main/java/hudson/model/Queue.java core/src/main/java/hudson/slaves/SlaveComputer.java core/src/main/java/jenkins/model/Jenkins.java core/src/main/resources/lib/hudson/executors.jelly http://jenkins-ci.org/commit/jenkins/2c5b57fcc1f39ed39057254e802f4183db5aa0dc Log: Always adding Computer for master as a fallback The original proposed fix for JENKINS-7291 creates a Computer object transitively. This seems unwise as it violates the design of Computer as stated in the javadoc, and for example we can end up creating two Computers for the master. I think a better fix is to create a Computer for the master all the time, even if there's no executors configured. The discrimination in Queue.makeBuildable would ensure that such phantom Computer is only used as a last resort. I've also tweaked executors.jelly a bit. I simplified it somewhat based on the idea that "if there's only one computer to show, the context is likely making it obvious". (I must be missing the intricacy in the current code.) – You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17311) Expand and encourage use of hash syntax in crontabs
SCM/JIRA link daemon commented on JENKINS-17311 Expand and encourage use of hash syntax in crontabs Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/scheduler/CronTab.java core/src/test/java/hudson/scheduler/CronTabTest.java http://jenkins-ci.org/commit/jenkins/7f92a9bd1a003b81419e5b9142f2592da608eb43 Log: JENKINS-17311 Improved hashify to detect manual skip idiom. – You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17344) Config pages broken by No such property: compressBuildLog
Alex Earl commented on JENKINS-17344 Config pages broken by No such property: compressBuildLog No, the previous jpi would not be around. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17344) Config pages broken by No such property: compressBuildLog
Gergely Nagy commented on JENKINS-17344 Config pages broken by No such property: compressBuildLog In the meantime, I had to downgrade to 2.25. I found 'plugins/email-ext.jpi', but this is the working version now. Can I still find the previous .jpi hanging around? If not I'll have to try again later in the week. Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17344) Config pages broken by No such property: compressBuildLog
Alex Earl commented on JENKINS-17344 Config pages broken by No such property: compressBuildLog I can't reproduce this at all. I've tried upgrading from 2.25 to 2.27.1 and can't reproduce it. Can you post the email-ext hpi that you have on your server? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17344) Config pages broken by No such property: compressBuildLog
Gergely Nagy commented on JENKINS-17344 Config pages broken by No such property: compressBuildLog Yes it's the latest LTS: 1.480.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/groups/opt_out.
[JIRA] (JENKINS-17344) Config pages broken by No such property: compressBuildLog
Alex Earl commented on JENKINS-17344 Config pages broken by No such property: compressBuildLog What version of Jenkins? email-ext is built against the LTS and is only tested vs. the LTS releases. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17344) Config pages broken by No such property: compressBuildLog
Gergely Nagy edited a comment on JENKINS-17344 Config pages broken by No such property: compressBuildLog Thanks for the quick reply. Yes, I have restarted Jenkins after upgrading. BTW, the install is a standard .deb(Debian Linux) one. Attaching config.xml. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17344) Config pages broken by No such property: compressBuildLog
Gergely Nagy updated JENKINS-17344 Config pages broken by No such property: compressBuildLog Change By: Gergely Nagy (25/Mar/13 5:06 PM) Attachment: config.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17344) Config pages broken by No such property: compressBuildLog
Gergely Nagy commented on JENKINS-17344 Config pages broken by No such property: compressBuildLog Yes, I have restarted Jenkins after upgrading. BTW, the install is a standard .deb(Debian Linux) one. Attaching config.xml. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17341) Promoted builds throw NullPointerException after upgrade to 1.507
Bruce Edge commented on JENKINS-17341 Promoted builds throw NullPointerException after upgrade to 1.507 Just confirming, I'm seeing this too. All jobs using build promotion fail to load and are missing from the dashboard view. Reverting to 1.506 fixes the problem. Using Jenkins promoted builds plugin 2.8 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17344) Config pages broken by No such property: compressBuildLog
Alex Earl commented on JENKINS-17344 Config pages broken by No such property: compressBuildLog I think you might have an issue in your setup, there IS in fact a field compressBuildLog on the ExtendedEmailPublisher class. Did you restart Jenkins after installing the new plugin? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17344) Config pages broken by No such property: compressBuildLog
Gergely Nagy
updated JENKINS-17344
Config pages broken by No such property: compressBuildLog
Change By:
Gergely Nagy
(25/Mar/13 4:58 PM)
Description:
Since an upgrade of Email-Ext plugin v2.25 -> v2.27.1, I cannot open same Configuration pages. They are stuck at the LOADING stage, and throw an exception stack trace (500). So this breaks -not just email- related configuration of those jobs completely. the only "workaround" I found is hacking into the config.xml on server to remove the element related to ext-email config, then restart server (not an option for me), so had to downgrade to 2.25.{code}javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.480.3.jar!/lib/form/hetero-list.jelly:112:94: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.480.3.jar!/lib/form/optionalBlock.jelly:84:23: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.480.3.jar!/lib/form/entry.jelly:73:23: No such property: compressBuildLog for class: hudson.plugins.emailext.ExtendedEmailPublisher at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103){code}Side question: could Jenkins be improved so that plugin bugs like this would
be
isolated
have
to avoid
such a disastrous effect
?
(e.g in this case, handle the exception
gracefully
while viewing the page
).
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17337) Failed to load job on Matrix jobs
SCM/JIRA link daemon commented on JENKINS-17337 Failed to load job on Matrix jobs Code changed in jenkins User: Jesse Glick Path: test/src/test/groovy/hudson/matrix/MatrixProjectTest.groovy http://jenkins-ci.org/commit/jenkins/1bf958afb196d0c56b37f00681027a549d0c9189 Log: JENKINS-17337 Added test for NPE. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17344) Config pages broken by No such property: compressBuildLog
Alex Earl commented on JENKINS-17344 Config pages broken by No such property: compressBuildLog Please post a config.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13465) Unable perform release: ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject on Hudson 2.2.0
Bertrand Gillis edited a comment on JENKINS-13465 Unable perform release: ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject on Hudson 2.2.0 I have the same problem and 2.2.1 of maven release plugin. I cannot perform a release anymore. So I've reverted back to jenkins 1.504 (last stable version for us). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17344) Config pages broken by No such property: compressBuildLog
Gergely Nagy updated JENKINS-17344 Config pages broken by No such property: compressBuildLog Change By: Gergely Nagy (25/Mar/13 4:54 PM) Summary: Config pages broken by No such property: compressBuildLog This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13465) Unable perform release: ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject on Hudson 2.2.0
Bertrand Gillis commented on JENKINS-13465 Unable perform release: ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject on Hudson 2.2.0 I have the same problem and 2.2.1 of maven release plugin. I cannot perform a release anymore so I've reverted back to jenkins 1.504 (last stable version for us). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17344) No such property: compressBuildLog
Gergely Nagy created JENKINS-17344 No such property: compressBuildLog Issue Type: Bug Assignee: Alex Earl Components: email-ext Created: 25/Mar/13 4:53 PM Description: Since an upgrade of Email-Ext plugin v2.25 -> v2.27.1, I cannot open same Configuration pages. They are stuck at the LOADING stage, and throw an exception stack trace (500). So this breaks not just email related configuration of those jobs completely. the only "workaround" I found is hacking into the config.xml on server to remove the element related to ext-email config, then restart server (not an option for me), so had to downgrade to 2.25. javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.480.3.jar!/lib/form/hetero-list.jelly:112:94: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.480.3.jar!/lib/form/optionalBlock.jelly:84:23: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.480.3.jar!/lib/form/entry.jelly:73:23: No such property: compressBuildLog for class: hudson.plugins.emailext.ExtendedEmailPublisher at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) Side question: could Jenkins be improved so that plugin bugs like this would isolated have such a disastrous effect (e.g in this case, handle the exception gracefully). Project: Jenkins Priority: Critical Reporter: Gergely Nagy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17337) Failed to load job on Matrix jobs
Jesse Glick assigned JENKINS-17337 to Jesse Glick Failed to load job on Matrix jobs Change By: Jesse Glick (25/Mar/13 4:34 PM) Assignee: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-3265) Reload Configuration from Disk (or POSTing config.xml) loses info on running builds
Jesse Glick commented on JENKINS-3265 Reload Configuration from Disk (or POSTing config.xml) loses info on running builds @vige I am not sure what build gets the hotfix but I think not 1.507. This got filed as JENKINS-17337. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17337) Failed to load job on Matrix jobs
Björn Pedersen commented on JENKINS-17337 Failed to load job on Matrix jobs I get the same problem on FreeBSD 9. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17337) Failed to load job on Matrix jobs
Jesse Glick resolved JENKINS-17337 as Fixed Failed to load job on Matrix jobs Was fixed in 3370e6e. Change By: Jesse Glick (25/Mar/13 4:28 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13465) Unable perform release: ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject on Hudson 2.2.0
Scott Oster commented on JENKINS-13465 Unable perform release: ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject on Hudson 2.2.0 I have the same problem with Jenkins 1.506 and 0.9.1 of maven release plugin. I cannot perform a release. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17342) CVS Checkout does not respect "Use Head If Not Found" option
Michael Clarke closed JENKINS-17342 as Not A Defect CVS Checkout does not respect "Use Head If Not Found" option CVS's "Use Head If Not Found" feature does not work in this way. The Branch/Tag must exist - this option is purely referring to any files in the repository that are in head, but not on the tag/branch you've requested. Enabling this option on update works since CVS uses the existing control files to find the target location rather than using the over-ridden option. Change By: Michael Clarke (25/Mar/13 3:44 PM) Status: Open Closed Assignee: Michael Clarke 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/groups/opt_out.
[JIRA] (JENKINS-17343) Jenkins is no more WinXP compliant : CreateSymbolicLinkW is not available
alexandre aubert created JENKINS-17343 Jenkins is no more WinXP compliant : CreateSymbolicLinkW is not available Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 25/Mar/13 3:34 PM Description: since update to 1.507 (from 1.505), no build is possible. it seems that fix of https://issues.jenkins-ci.org/browse/JENKINS-15587 has broken XP compatibility. when starting to run any job, error message is : FATAL: Error looking up function 'CreateSymbolicLinkW': La procédure spécifiée est introuvable. java.lang.UnsatisfiedLinkError: Error looking up function 'CreateSymbolicLinkW': La procédure spécifiée est introuvable. at com.sun.jna.Function.(Function.java:179) at com.sun.jna.NativeLibrary.getFunction(NativeLibrary.java:347) at com.sun.jna.NativeLibrary.getFunction(NativeLibrary.java:327) at com.sun.jna.Library$Handler.invoke(Library.java:203) at $Proxy22.CreateSymbolicLinkW(Unknown Source) at hudson.util.jna.Kernel32Utils.createSymbolicLink(Kernel32Utils.java:85) at hudson.Util.createSymlink(Util.java:1048) at hudson.model.Run.execute(Run.java:1573) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Environment: windows XP Project: Jenkins Priority: Blocker Reporter: alexandre aubert This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17342) CVS Checkout does not respect "Use Head If Not Found" option
Timm H
updated JENKINS-17342
CVS Checkout does not respect "Use Head If Not Found" option
Change By:
Timm H
(25/Mar/13 3:26 PM)
Description:
I want to pass the branch of a project that uses cvs via environment var.Under some circumstances i want it to check out the HEAD revision instead of the branch.I entered $BRANCH as Branch and checked the option "Use Head If Not Found".The job itself is started by another job, which passes the parameters to it.The parameters are originally read from a file.This is the output on one of our slaves:{code}cvs checkout -f -P -r b9990 -D 25 Mar 2013 15:51:00 +0100 -d project projectJob cvs [checkout aborted]: no such tag b9990 ERROR: Cvs task failedSkipping sonar analysis due to bad build status FAILURE{code}It seems to work when enabling the "use update command" option:{code}cvs update -C -d -P -f -r b9990 -D 25 Mar 2013 15:26:19 +0100 project{code}Sadly, the update option itself seems to be broken and does not always update every file so this is not an option.
Edit: The branch b9990 does not exist in the repository, i use this as a workaround since i can't pass "HEAD" as the branch var if i want to checkout the HEAD.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17342) CVS Checkout does not respect "Use Head If Not Found" option
Timm H created JENKINS-17342 CVS Checkout does not respect "Use Head If Not Found" option Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: cvs Created: 25/Mar/13 3:05 PM Description: I want to pass the branch of a project that uses cvs via environment var. Under some circumstances i want it to check out the HEAD revision instead of the branch. I entered $BRANCH as Branch and checked the option "Use Head If Not Found". The job itself is started by another job, which passes the parameters to it. The parameters are originally read from a file. This is the output on one of our slaves: cvs checkout -f -P -r b9990 -D 25 Mar 2013 15:51:00 +0100 -d project projectJob cvs [checkout aborted]: no such tag b9990 ERROR: Cvs task failed Skipping sonar analysis due to bad build status FAILURE It seems to work when enabling the "use update command" option: cvs update -C -d -P -f -r b9990 -D 25 Mar 2013 15:26:19 +0100 project Sadly, the update option itself seems to be broken and does not always update every file so this is not an option. Environment: Linux 2.6.32-279.1.1.el6.x86_64, Jenkins 1.501, Concurrent Versions System (CVS) 1.11.23 (client/server) Project: Jenkins Priority: Major Reporter: Timm H This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-10184) wrong timestamps in build timeline
Damien Finck commented on JENKINS-10184 wrong timestamps in build timeline It's fixed for me for months. System : Windows 288 r2 Jenkins 1.507 user.timezone : Europe/Paris This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17341) Promoted builds throw NullPointerException after upgrade to 1.507
Mikhail Cheshkov updated JENKINS-17341 Promoted builds throw NullPointerException after upgrade to 1.507 Change By: Mikhail Cheshkov (25/Mar/13 2:41 PM) Environment: Ubuntu 12.04Jenkins 1.507 through APT from http://pkg.jenkins-ci.org/debian This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-5413) SCM polling getting hung
lacostej commented on JENKINS-5413 SCM polling getting hung Derek, Not sure if Dimensions plugin is using a native call or not hunder the hood. Could you make a threaddump and/or a list of processes ? J This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17341) Promoted builds throw NullPointerException after upgrade to 1.507
Mikhail Cheshkov
updated JENKINS-17341
Promoted builds throw NullPointerException after upgrade to 1.507
Change By:
Mikhail Cheshkov
(25/Mar/13 2:27 PM)
Description:
After upgrade Jenkins to 1.507 I dont see any job, found this in log
{noformat}
SEVERE: Failed Loading job java.lang.NullPointerException at hudson.plugins.promoted_builds.JobPropertyImpl.getItem(JobPropertyImpl.java:220) at hudson.plugins.promoted_builds.JobPropertyImpl.getItem(JobPropertyImpl.java:41) at hudson.model.AbstractProject.onLoad(AbstractProject.java:291) at hudson.model.Items.load(Items.java:221) at hudson.model.ItemGroupMixIn.loadChildren(ItemGroupMixIn.java:99) at hudson.plugins.promoted_builds.JobPropertyImpl.setOwner(JobPropertyImpl.java:145) at hudson.plugins.promoted_builds.JobPropertyImpl.setOwner(JobPropertyImpl.java:41) at hudson.model.Job.onLoad(Job.java:201) at hudson.model.AbstractProject.onLoad(AbstractProject.java:282) at hudson.model.Project.onLoad(Project.java:83) at hudson.model.Items.load(Items.java:221) at jenkins.model.Jenkins$17.run(Jenkins.java:2552) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:887) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679)
{noformat}
When I disable promoted builds plugin, jobs appear again, but w/o promotions, of course.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9271) "AdjunctManager is not installed for this application" upon failed boot
Daniel Mack resolved JENKINS-9271 as Fixed "AdjunctManager is not installed for this application" upon failed boot SORRY i had 1.506 installed - after a redeploy of 1.507 it works as expected ... but the bug certainly appeared on 1.506 - like i said : somebody keeps re-inserting the bug and someone keeps fixing it ... maybe stop the loop sometime Change By: Daniel Mack (25/Mar/13 2:19 PM) Status: Reopened Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17341) Promoted builds throw NullPointerException after upgrade to 1.507
Mikhail Cheshkov created JENKINS-17341 Promoted builds throw NullPointerException after upgrade to 1.507 Issue Type: Bug Assignee: Unassigned Components: promoted-builds Created: 25/Mar/13 2:15 PM Description: After upgrade Jenkins to 1.507 I dont see any job, found this in log SEVERE: Failed Loading job java.lang.NullPointerException at hudson.plugins.promoted_builds.JobPropertyImpl.getItem(JobPropertyImpl.java:220) at hudson.plugins.promoted_builds.JobPropertyImpl.getItem(JobPropertyImpl.java:41) at hudson.model.AbstractProject.onLoad(AbstractProject.java:291) at hudson.model.Items.load(Items.java:221) at hudson.model.ItemGroupMixIn.loadChildren(ItemGroupMixIn.java:99) at hudson.plugins.promoted_builds.JobPropertyImpl.setOwner(JobPropertyImpl.java:145) at hudson.plugins.promoted_builds.JobPropertyImpl.setOwner(JobPropertyImpl.java:41) at hudson.model.Job.onLoad(Job.java:201) at hudson.model.AbstractProject.onLoad(AbstractProject.java:282) at hudson.model.Project.onLoad(Project.java:83) at hudson.model.Items.load(Items.java:221) at jenkins.model.Jenkins$17.run(Jenkins.java:2552) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:887) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) When I disable promoted builds plugin, jobs appear again, but w/o promotions, of course. Environment: Ubuntu 12.04 Jenkins through APT from http://pkg.jenkins-ci.org/debian Project: Jenkins Priority: Major Reporter: Mikhail Cheshkov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14656) Jenkins cannot guarantee that it will push the exact same build through a build pipeline if some of the steps are triggered manually
Andreas John
commented on JENKINS-14656
Jenkins cannot guarantee that it will push the exact same build through a build pipeline if some of the steps are triggered manually
Heyho,
same problem here After reading Christopher's excellent analysis I create a groovy script that injects the variable for me. It simply loops over the causes until it find the cause with class name hudson.model.Cause$UpstreamCause and then injects a UPSTREAM_BUILD_NUMBER env variable. This can be used in the copyartifact step to copy "specific build number". And yes, you need additionally the groovy plugin and envinject.
=== 8< ===
import hudson.model.*
def upstreamBuildNumber
def build = Thread.currentThread().executable
def actions = build.getActions(hudson.model.CauseAction);
actions.each { action ->
action.causes.each { cause ->
if ( cause.class.name == 'hudson.model.Cause$UpstreamCause' ) {
upstreamBuildNumber = "${cause.getUpstreamBuild()}"
}
}
}
def map = [UPSTREAM_BUILD_NUMBER:upstreamBuildNumber]
return map
=== 8< ===
HTH,
Andreas
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9271) "AdjunctManager is not installed for this application" upon failed boot
Daniel Mack edited a comment on JENKINS-9271 "AdjunctManager is not installed for this application" upon failed boot apparently this bug regressed yet again - somebody keeps inserting the same error over and over again. It appears with the newest jenkins (1.507, .war) and debian 6.0.7 stable, together with Apache Tomcat/6.0.35 on JVM 1.6.0_18-b18 (Sun) catalina.out 25.03.2013 14:36:48 org.kohsuke.stapler.jelly.AdjunctTag doTag WARNUNG: AdjunctManager is not installed for this application. Skipping tags java.lang.Exception at org.kohsuke.stapler.jelly.AdjunctTag.doTag(AdjunctTag.java:74) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) 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.CallTagLibScript.run(CallTagLibScript.java:119) 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.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.CallTagLibScript.run(CallTagLibScript.java:119) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:666) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:162) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.apache.catalina.core.ApplicationFilterChain.i
[JIRA] (JENKINS-17340) Environment variables fail to get translated when encountered as part of a command execution.
Nipin Joshy created JENKINS-17340 Environment variables fail to get translated when encountered as part of a command execution. Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: envinject, publish-over-ssh Created: 25/Mar/13 2:07 PM Description: Hi, I am using Jenkins(v1.506) to create a build automation for Tivoli Omnibus Netcool v7.1 on a Solaris v10 machine. When I try to execute the Probe rules syntax check command '/opt/netcool/omnibus/probes/nco_p_syntax -rulesfile $NC_RULES_HOME/snmptrap.rules -server WAOSCV1', in which $NC_RULES_HOME is an environment variable '/opt/netcool/etc/rules/'. This enviroment variable is set using 'envinject' plugin. The command is executed using publish-over-ssh plugins The enviorment variable $NC_RULES_HOME is converted as '/opt/netcool/etc/rules/' in the given command, but when the files are read as part of the 'nco_p_syntax' command, the $NC_RULES_HOME is not decoded to '/opt/netcool/etc/rules/'. PFB the console output. Started by user anonymous [EnvInject] - Loading node environment variables. Building in workspace C:\Program Files\Jenkins\workspace\sytaxcheck2 [EnvInject] - Executing scripts and injecting environment variables after the SCM step. [EnvInject] - Injecting as environment variables the properties content NC_RULES_HOME=/opt/netcool/etc/rules [EnvInject] - Variables injected successfully. SSH: Connecting from host [TVMATP230977D] SSH: Connecting with configuration [ssweb0034.nsatest.in.telstra.com.au] ... SSH: EXEC: STDOUT/STDERR from command [/opt/netcool/omnibus/probes/nco_p_syntax -rulesfile /opt/netcool/etc/rules/snmptrap.rules -server WAOSCV1] ... 03/25/13 19:41:28: Warning: Failed to load properties file : No such file or directory 03/25/13 19:41:28: Information: Connecting ... 03/25/13 19:41:28: Information: Checking rules file ... 03/25/13 19:41:28: Debug: Reading /opt/netcool/etc/rules/snmptrap.rules 03/25/13 19:41:28: Debug: Plain text rules file detected. 03/25/13 19:41:28: Error: Rules file '/opt/netcool/etc/rules/snmptrap.rules' line 98: Failed to read lookup table file '$NC_RULES_HOME/include-snmptrap/CorrScore.snmptrap.lookup' 03/25/13 19:41:28: Information: Falling back to previous rules file. 03/25/13 19:41:28: Error: Error(s) in rules file 03/25/13 19:41:28: Information: Disconnecting ... 03/25/13 19:41:28: Warning: Disconnect malfunction - continuing shutdown anyway SSH: EXEC: completed after 811 ms SSH: Disconnecting configuration [ssweb0034.nsatest.in.telstra.com.au] ... ERROR: Exception when publishing, exception message [Exec exit status not zero. Status [2]] Build step 'Send files or execute commands over SSH' changed build result to UNSTABLE Finished: UNSTABLE Due Date: 27/Mar/13 12:00 AM Environment: Automation for Tivoli Omnibus Netcool v7.1 on a Solaris v10 machine. Project: Jenkins Priority: Blocker Reporter: Nipin Joshy This message is automatically generated by JIRA. 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.googl
[JIRA] (JENKINS-16584) Build Flow plugin does not work with Mask Passwords plugin
Olivier Kuhn commented on JENKINS-16584 Build Flow plugin does not work with Mask Passwords plugin Hello, I have the same need. I also want to add that in the Build Flow configuration, there is no "Build Environment" section, wherein you can activate the password mask for the Build Flow job itself. Thus you cannot mask in the Build flow log the passwords defined as Build Flow parameters. Regards This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9271) "AdjunctManager is not installed for this application" upon failed boot
Daniel Mack reopened JENKINS-9271 "AdjunctManager is not installed for this application" upon failed boot apparently this bug regressed yet again - somebody keeps inserting the same error over and over again. It appears with the newest jenkins (1.507, .war) and debian 6.0.7 stable, together with Apache Tomcat/6.0.35 on JVM 1.6.0_18-b18 (Sun) Change By: Daniel Mack (25/Mar/13 1:54 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/groups/opt_out.
[JIRA] (JENKINS-5413) SCM polling getting hung
Derek Seibert edited a comment on JENKINS-5413 SCM polling getting hung Our team encounters this issue almost daily using the Dimensions SCM plugin. We run a single instance Jenkins server which polls a Stream ever 30 minutes. I wanted to comment just to explain how we first noticed the issue was occurring in case anybody searching this issue starts in the same place. We select the Dimensions Polling Log for our job and see the following at maybe 9AM or 10AM. The polling has hung at this point and we need to restart our application server. Started on Mar 25, 2013 8:30:35 AM We expect to see something like. Started on Mar 25, 2013 8:30:35 AM Done. Took 19 sec No changes This is why this issue is so troubling. There is no notification trigger when "Started on..." has just been sitting there hung for a while, and no further polling can be done by that job without a restart of the application server. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-5413) SCM polling getting hung
Derek Seibert commented on JENKINS-5413 SCM polling getting hung Our team encounters this issue almost daily using the Dimensions SCM plugin. We run a single instance Jenkins server which polls a Stream ever 30 minutes. I wanted to comment just to explain how we first noticed the issue was occurring in case anybody searching this issue starts in the same place. We select the Dimensions Polling Log for our job and see the following at maybe 9AM or 10AM. The polling has hung at this point and we need to restart our application server. Started on Mar 25, 2013 8:30:35 AM We expect to see something like. Started on Mar 25, 2013 8:30:35 AM Done. Took 19 sec No changes This is why this issue is so troubling. There is no notification trigger when "Started on..." has just been sitting there hung for a while, and no further polling can be done by that job without a restart of the application server. Our lead is hesitant to use a script to kill SCM threads because we don't know/haven't fully investigated the source of the issue. I figured this would be the best place to discuss 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/groups/opt_out.
[JIRA] (JENKINS-15826) CVS plugin excluded regions no longer match on the file path
Michael Clarke closed JENKINS-15826 as Cannot Reproduce CVS plugin excluded regions no longer match on the file path I'm unable to replicate this either manually or through unit tests. Please re-open if you are still affected by this issue and have further information to help resolve it. Change By: Michael Clarke (25/Mar/13 1:33 PM) Status: Open Closed Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14711) Polling and Changelog do not pick up changes on CVS Tags
Michael Clarke closed JENKINS-14711 as Won't Fix Polling and Changelog do not pick up changes on CVS Tags Given my previous comment about the risks in trying to pick changes in a tag, I have decided that this issue will not be fixed. Moving a tag is regarded as bad practice and trying to introduce a method of finding these changes would significantly increase CPU and Memory usage of the CVS plugin which such a fix doesn't warrant. Change By: Michael Clarke (25/Mar/13 1:28 PM) Status: Reopened Closed Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17265) Builds disappearing from history
Jose Sa commented on JENKINS-17265 Builds disappearing from history Please notice that "Reload from disk" may be unsafe if you have actively running jobs as indicated in JENKINS-3265 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14711) Polling and Changelog do not pick up changes on CVS Tags
Michael Clarke updated JENKINS-14711 Polling and Changelog do not pick up changes on CVS Tags Change By: Michael Clarke (25/Mar/13 1:24 PM) Summary: No changelist in Polling and Changelog do not pick up changes on CVS plugin 2.5 using rlog, but "cli rlog" works fine Tags This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17252) JGit checkout poor performaces
Mark Waite closed JENKINS-17252 as Fixed JGit checkout poor performaces Reported resolved by original submitter. Change By: Mark Waite (25/Mar/13 12:32 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/groups/opt_out.
[JIRA] (JENKINS-17252) JGit checkout poor performaces
Mark Waite resolved JENKINS-17252 as Fixed JGit checkout poor performaces Confirmed fixed by original submitter Change By: Mark Waite (25/Mar/13 12:31 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13330) Jenkins slave hangs in post build phase
Simon Jagoe edited a comment on JENKINS-13330 Jenkins slave hangs in post build phase I am working on a system that uses COM to communicate with a backend service. There are some test cases that hang in certain rare cases when using COM, which cause other (concurrent) builds of the same project to not complete, hanging in the build post-processing. While we are working on trying to prevent hanging in our test cases, I do not think Jenkins should be waiting before sending emails. It makes Jenkins not very robust against problematic builds. In my opinion the build system should expect problems in the user scripts and be able to handle 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/groups/opt_out.
[JIRA] (JENKINS-13330) Jenkins slave hangs in post build phase
Simon Jagoe commented on JENKINS-13330 Jenkins slave hangs in post build phase I am working on a system that uses COM to communicate with a backend service. There are some test cases that hang in certain rare cases, which cause other (concurrent) builds of the same project to not complete, hanging in the build post-processing. While we are working on trying to prevent hanging in our test cases, I do not think Jenkins should be waiting before sending emails. It makes Jenkins not very robust against problematic builds. In my opinion the build system should expect problems in the user scripts and be able to handle 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/groups/opt_out.
to read /etc/init/jenkins.conf
I have installed Jenkins 1.507 on Ubuntu 12.10 in the folder /lunifera/jenkins/ I start Jenkins as Standalone with the following command: java -jar /lunifera/jenkins/jenkins.war --httpPort=8083 --logfile=/var/log/jenkins/jenkins.log How can I say to jenkins to use the following config-File: /etc/init/jenkins.conf -- View this message in context: http://jenkins.361315.n4.nabble.com/to-read-etc-init-jenkins-conf-tp4660382.html Sent from the Jenkins issues mailing list archive at Nabble.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/groups/opt_out.
[JIRA] (JENKINS-17310) URL in the project description without https:// don't work
Andrey Sorokovikov stopped work on JENKINS-17310 URL in the project description without https:// don't work Change By: Andrey Sorokovikov (25/Mar/13 11:46 AM) Status: In Progress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17314) Rebuild Job using GET method
Bruno Cunha commented on JENKINS-17314 Rebuild Job using GET method I've made a pull request with the fix for this issue. Waiting for release of version 2.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/groups/opt_out.
[JIRA] (JENKINS-17314) Rebuild Job using GET method
Bruno Cunha assigned JENKINS-17314 to Bruno Cunha Rebuild Job using GET method Change By: Bruno Cunha (25/Mar/13 11:21 AM) Assignee: Peter Hayes Bruno Cunha This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17336) in the jenkins 1.506 version My Views doesn't work
Andrey Sorokovikov updated JENKINS-17336 in the jenkins 1.506 version My Views doesn't work Change By: Andrey Sorokovikov (25/Mar/13 11:11 AM) Priority: Trivial Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17336) in the jenkins 1.506 version My Views doesn't work
Andrey Sorokovikov stopped work on JENKINS-17336 in the jenkins 1.506 version My Views doesn't work Change By: Andrey Sorokovikov (25/Mar/13 11:10 AM) Status: In Progress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17339) Matrix jobs not loaded with 1.507
sogabe resolved JENKINS-17339 as Duplicate Matrix jobs not loaded with 1.507 Change By: sogabe (25/Mar/13 11:09 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17337) Failed to load job on Matrix jobs
Andrew Cecil commented on JENKINS-17337 Failed to load job on Matrix jobs Same issue here on Windows 7. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17337) Failed to load job on Matrix jobs
John Dickinson commented on JENKINS-17337 Failed to load job on Matrix jobs Same here on Linux 2.6.32-279.19.1.el6.x86_64 #1 SMP Wed Dec 19 07:05:20 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux we have also had to revert to 1.506 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17337) Failed to load job on Matrix jobs
John Dickinson updated JENKINS-17337 Failed to load job on Matrix jobs Change By: John Dickinson (25/Mar/13 10:50 AM) Environment: Windows 7 CentOS 64 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17339) Matrix jobs not loaded with 1.507
Wolfgang Hauser created JENKINS-17339 Matrix jobs not loaded with 1.507 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: matrix Created: 25/Mar/13 10:45 AM Description: With 1.507 I got following load errors while starting Jenkins (1.506 don't have this problem): Mar 25, 2013 11:34:04 AM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job intapp_vehicle java.lang.NullPointerException at hudson.matrix.MatrixProject.getItem(MatrixProject.java:669) at hudson.matrix.MatrixProject.getItem(MatrixProject.java:662) at hudson.matrix.MatrixProject.getItem(MatrixProject.java:98) at hudson.model.AbstractProject.onLoad(AbstractProject.java:291) at hudson.model.Project.onLoad(Project.java:83) at hudson.matrix.MatrixConfiguration.onLoad(MatrixConfiguration.java:89) at hudson.matrix.MatrixProject.loadConfigurations(MatrixProject.java:541) at hudson.matrix.MatrixProject.loadConfigurations(MatrixProject.java:548) at hudson.matrix.MatrixProject.rebuildConfigurations(MatrixProject.java:585) at hudson.matrix.MatrixProject.onLoad(MatrixProject.java:476) at hudson.model.Items.load(Items.java:221) at jenkins.model.Jenkins$17.run(Jenkins.java:2552) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:887) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Environment: Debian lenny Jenkins 1.507 Fix Versions: current Project: Jenkins Priority: Blocker Reporter: Wolfgang Hauser This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14825) winstone.ClientSocketException: Failed to write to client after upgrade to 1.477
Hans-Juergen Hafner commented on JENKINS-14825 winstone.ClientSocketException: Failed to write to client after upgrade to 1.477 Similar error with 1.505, but cc.xml.jelly. It takes sometimes ages to load pages. Red Hat Enterprise Linux Server release 5.6, java version "1.6.0_33" javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/ci/cp/jenkins/home/war/WEB-INF/lib/jenkins-core-1.505.jar!/hudson/model/View/cc.xml.jelly:35:44: Failed to write to client This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17252) JGit checkout poor performaces
Olivier Kuhn commented on JENKINS-17252 JGit checkout poor performaces Yes, with 1.0.5 the checkout time is like with 1.0.3 (fast ) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13865) Jenkins /queue/api does not produce properly formatted JSON when a build in queue where the destination node/s are busy.
Bernd bep commented on JENKINS-13865 Jenkins /queue/api does not produce properly formatted JSON when a build in queue where the destination node/s are busy. 1.480.3 fixes the XML related issue reported by me above. thanks everyone! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17286) Triggered jobs should run synchronously as mentioned or listed when using the "Trigger/Call builds on another project" item
siddu D commented on JENKINS-17286 Triggered jobs should run synchronously as mentioned or listed when using the "Trigger/Call builds on another project" item it works with executor 2. Is this expected behavior? If so then it is good to have option called serial and concurrent. If the option is serial then jobs should get triggered in the order as mentioned in the projects list serially one after another once the job is completed. When option is concurrent then it is not required to maintain the project order given that executor is set more as per the requirement. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-3265) Reload Configuration from Disk (or POSTing config.xml) loses info on running builds
Ville Nummela commented on JENKINS-3265 Reload Configuration from Disk (or POSTing config.xml) loses info on running builds Is this hotfix included in 1.507? I get that NullPointerException with 1.507 so either the fix is not there or it doesn't 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/groups/opt_out.
