[JIRA] [acceptance-test-harness] (JENKINS-22988) IllegalArgumentException: URI is not hierarchical (from Docker.build)
Jesse Glick created JENKINS-22988 IllegalArgumentException: URI is not hierarchical (from Docker.build) Issue Type: Bug Assignee: Oliver Gondža Components: acceptance-test-harness Created: 12/May/14 8:26 PM Description: Ubuntu 14.04 x64. TYPE=winstone_docker JENKINS_WAR=.../jenkins.war BROWSER=htmlunit mvn test fails with: com.google.inject.ProvisionException: Guice provision errors: 1) Error in custom provider, java.lang.IllegalArgumentException: URI is not hierarchical at org.jenkinsci.test.acceptance.FallbackConfig.createController(Unknown Source) (via modules: org.jenkinsci.test.acceptance.guice.World - com.google.inject.util.Modules$OverrideModule - com.google.inject.util.Modules$OverrideModule - org.jenkinsci.test.acceptance.FallbackConfig) at org.jenkinsci.test.acceptance.FallbackConfig.createController(Unknown Source) (via modules: org.jenkinsci.test.acceptance.guice.World - com.google.inject.util.Modules$OverrideModule - com.google.inject.util.Modules$OverrideModule - org.jenkinsci.test.acceptance.FallbackConfig) while locating org.jenkinsci.test.acceptance.controller.JenkinsController for parameter 1 at org.jenkinsci.test.acceptance.po.Jenkins.init(Unknown Source) at org.jenkinsci.test.acceptance.po.Jenkins.class(Unknown Source) while locating org.jenkinsci.test.acceptance.po.Jenkins for field at org.jenkinsci.test.acceptance.junit.AbstractJUnitTest.jenkins(Unknown Source) while locating com.cloudbees.jenkins.test.acceptance.BackupPluginTest 1 error at com.google.inject.internal.Errors.throwProvisionExceptionIfErrorsExist(Errors.java:465) at com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:67) at com.google.inject.internal.InjectorImpl.injectMembers(InjectorImpl.java:968) at org.jenkinsci.test.acceptance.junit.JenkinsAcceptanceTestRule$1.evaluate(JenkinsAcceptanceTestRule.java:46) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) Caused by: java.lang.IllegalArgumentException: URI is not hierarchical at java.io.File.init(File.java:418) at org.jenkinsci.test.acceptance.docker.Docker.build(Docker.java:108) at org.jenkinsci.test.acceptance.docker.Docker.build(Docker.java:93) at org.jenkinsci.test.acceptance.controller.WinstoneDockerController.startProcess(WinstoneDockerController.java:62) at org.jenkinsci.test.acceptance.controller.LocalController.bringItUp(LocalController.java:312) at
[JIRA] [acceptance-test-harness] (JENKINS-22989) Default value for $BROWSER should be htmlunit
Jesse Glick created JENKINS-22989 Default value for $BROWSER should be htmlunit Issue Type: Bug Assignee: Oliver Gondža Components: acceptance-test-harness Created: 12/May/14 8:28 PM Description: Why should BROWSER=firefox be the default? I do not even have Firefox installed. htmlunit seems the most sensible default: should work on any system, even from CI, without a display. Environment: 1.1 Project: Jenkins Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-22990) NPE from PluginManager.isInstalled
Jesse Glick created JENKINS-22990 NPE from PluginManager.isInstalled Issue Type: Bug Assignee: Oliver Gondža Components: acceptance-test-harness Created: 12/May/14 8:32 PM Description: A test @kohsuke wrote using @WithPlugins fails with java.lang.NullPointerException at org.jenkinsci.test.acceptance.po.PluginManager.isInstalled(PluginManager.java:78) at org.jenkinsci.test.acceptance.po.PluginManager.installPlugin(PluginManager.java:107) at org.jenkinsci.test.acceptance.junit.WithPlugins$RuleImpl$1.installPlugins(WithPlugins.java:64) at org.jenkinsci.test.acceptance.junit.WithPlugins$RuleImpl$1.evaluate(WithPlugins.java:57) at org.jenkinsci.test.acceptance.junit.JenkinsAcceptanceTestRule$1.evaluate(JenkinsAcceptanceTestRule.java:50) at ... The line of code in question: String version = getVersionFromWpValue(n) != null ? getVersionFromWpValue(n) : ucmd.get().plugins.get(n).version; I am not sure which of ucmd, get(), plugins, or get(...) is null, but if there is something wrong in the environment or test setup, a proper AssertionError should be thrown. Environment: 1.1 Project: Jenkins Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22685) Jenkins cannot restart Windows service
JCK edited a comment on JENKINS-22685 Jenkins cannot restart Windows service no longer applicable This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22685) Jenkins cannot restart Windows service
JCK edited a comment on JENKINS-22685 Jenkins cannot restart Windows service Here's what's happening: 1. Restarting Jenkins (after plugin-update or by calling /restart) spawns a new process to execute "jenkins.exe restart" (i.e., restarting via the Windows Service wrapper). The Parent Process ID of this new process equals the Process ID that is running jenkins.war. 2. Jenkins.exe's "restart" command is a three-part process: A) stop the jenkins.war PID and all children PID; B) Wait for jenkins.war PID to stop; C) launch jenkins.war in a new process. 3. Since this execution of "jenkins.exe restart" is itself a child process of jenkins.war, the Jenkins service is killing it as part of 2A. This results in: 3A. Killing "jenkins.exe restart" (via SIGINT) causes that process to return w/ errorlevel=1. The WindowsServiceLifecycle restart method is checking the errorlevel from running "jenkins.exe restart" and seeing that it is not 0, and therefore throws an IOException. This is the error message seen in jenkins.err.log. 3B. Since the process running "jenkins.exe restart" gets killed as part of Step 2A, it does not get a change to complete the restart process, so Jenkins remains stopped. Solution: From looking at the WinSW project, this issue was expected. A "restart!" command (vs. the standard "restart") was added that launches a new process to handle restart. WindowsServiceLifecycle should use the new command. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-22990) NPE from PluginManager.isInstalled
Ulli Hafner assigned JENKINS-22990 to Matthias Karl NPE from PluginManager.isInstalled Can you please have a look if the error handling could be improved? Change By: Ulli Hafner (12/May/14 9:38 PM) Assignee: OliverGondža MatthiasKarl This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-22990) NPE from PluginManager.isInstalled
Ulli Hafner edited a comment on JENKINS-22990 NPE from PluginManager.isInstalled @itgkarl: Can you please have a look if the error handling could be improved? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-22990) NPE from PluginManager.isInstalled
Ulli Hafner edited a comment on JENKINS-22990 NPE from PluginManager.isInstalled @Matthias Karl: Can you please have a look if the error handling could be improved? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-22990) NPE from PluginManager.isInstalled
Ulli Hafner commented on JENKINS-22990 NPE from PluginManager.isInstalled @Jesse: which test? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-22989) Default value for $BROWSER should be htmlunit
Ulli Hafner commented on JENKINS-22989 Default value for $BROWSER should be htmlunit Hmm, I don't think that htmlunit works at all, since it can't handle _javascript_... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-18298) Jenkins (Github Plugin) post-commit hook fails to build with ssh config aliases
Keith Stevens commented on JENKINS-18298 Jenkins (Github Plugin) post-commit hook fails to build with ssh config aliases Just got bitten by this, as well. Any workaround or proposed 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/d/optout.
[JIRA] [core] (JENKINS-17420) ComputerListener.onOffline not very useful
Jesse Glick commented on JENKINS-17420 ComputerListener.onOffline not very useful Duplicate of the second problem, not the first. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-22989) Default value for $BROWSER should be htmlunit
Jesse Glick commented on JENKINS-22989 Default value for $BROWSER should be htmlunit It handles _javascript_ fine in JenkinsRule. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-22988) IllegalArgumentException: URI is not hierarchical (from Docker.build)
Kohsuke Kawaguchi commented on JENKINS-22988 IllegalArgumentException: URI is not hierarchical (from Docker.build) Confirmed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-22988) IllegalArgumentException: URI is not hierarchical (from Docker.build)
Kohsuke Kawaguchi assigned JENKINS-22988 to Kohsuke Kawaguchi IllegalArgumentException: URI is not hierarchical (from Docker.build) Change By: Kohsuke Kawaguchi (12/May/14 10:11 PM) Assignee: OliverGondža KohsukeKawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vsphere-cloud] (JENKINS-21810) Additional options on slave disconnection
Jason Swager commented on JENKINS-21810 Additional options on slave disconnection Please try the latest v1.1.19 and try the Revert and Reset/Revert and Restart options. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-22989) Default value for $BROWSER should be htmlunit
Kohsuke Kawaguchi commented on JENKINS-22989 Default value for $BROWSER should be htmlunit I don't feel strongly one way or another, as this is just a default value. I just thought Firefox was adequate default, because this was an acceptance test and I never fully trusted HtmlUnit's browser emulation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22028) HTML in job description does not get rendered (all html tags escaped)
dogfood commented on JENKINS-22028 HTML in job description does not get rendered (all html tags escaped) Integrated in jenkins_main_trunk #3374 FIX JENKINS-22028 Allow MarkupFormatter without enabling security (Revision ac3a5cd61461c5f7f063c57fba81a5aec6409664) JENKINS-22028 Noting merge of #1235. (Revision f3943a4ef707697e4cd512463c81b07f9bec95bc) Result = SUCCESS daniel-beck : ac3a5cd61461c5f7f063c57fba81a5aec6409664 Files : core/src/main/resources/hudson/security/GlobalSecurityConfiguration/index.groovy core/src/main/java/hudson/security/GlobalSecurityConfiguration.java core/src/main/java/jenkins/model/Jenkins.java Jesse Glick : f3943a4ef707697e4cd512463c81b07f9bec95bc Files : changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-22074) Jobs within a Multijob are placed incorrectly in Build Pipeline Plugin display
James Levinson commented on JENKINS-22074 Jobs within a Multijob are placed incorrectly in Build Pipeline Plugin display I came to the same conclusion / workaround. Both plugins have display issues but the ability to parallelize many jobs is the killer feature that keeps bringing back to the multi-job. To me, it seems like simple cases, like this one job kicks of this one job (like the picture at https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin), work well, but complex cases that have jobs that kick off multiple jobs, not so much. If only someone savvier than I could combine the two. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22867) localized help messages not found for Invoke top-level Maven targets
dogfood commented on JENKINS-22867 localized help messages not found for Invoke top-level Maven targets Integrated in jenkins_main_trunk #3375 FIX JENKINS-22867 Fix localization and relative links. (Revision 5188b26a5a38a57c60e275f5c3793b855c8ded4b) JENKINS-22867 Noting merge of #1232. (Revision d06e2dc67fd3e7e796015798a301d83920f391c2) Result = SUCCESS daniel-beck : 5188b26a5a38a57c60e275f5c3793b855c8ded4b Files : core/src/main/resources/hudson/tasks/Maven/help_ru.jelly core/src/main/resources/hudson/tasks/Maven/help_ru.properties core/src/main/resources/hudson/tasks/Maven/help_de.jelly core/src/main/resources/hudson/tasks/Maven/help.jelly core/src/main/resources/hudson/tasks/Maven/help_tr.jelly core/src/main/resources/hudson/tasks/Maven/help_pt_BR.properties core/src/main/resources/hudson/tasks/Maven/help_pt_BR.jelly core/src/main/resources/hudson/tasks/Maven/help_zh_TW.jelly core/src/main/resources/hudson/tasks/Maven/help_fr.properties core/src/main/resources/hudson/tasks/Maven/help_tr.properties core/src/main/resources/hudson/tasks/Maven/help_ja.jelly core/src/main/resources/hudson/tasks/Maven/help.properties core/src/main/resources/hudson/tasks/Maven/help_ja.properties core/src/main/resources/hudson/tasks/Maven/help_de.properties core/src/main/resources/hudson/tasks/Maven/help_fr.jelly core/src/main/resources/hudson/tasks/Maven/help_zh_TW.properties Jesse Glick : d06e2dc67fd3e7e796015798a301d83920f391c2 Files : changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22991) Restart would not properly display username if user was not loaded.
Steven Christou created JENKINS-22991 Restart would not properly display username if user was not loaded. Issue Type: Bug Assignee: Unassigned Components: core Created: 13/May/14 12:14 AM Description: This issue was fixed in https://github.com/jenkinsci/jenkins/pull/1167. I created this jira to mark this fix for backporting. Project: Jenkins Labels: lts-candidate Priority: Minor Reporter: Steven Christou This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-22990) NPE from PluginManager.isInstalled
Kohsuke Kawaguchi assigned JENKINS-22990 to Kohsuke Kawaguchi NPE from PluginManager.isInstalled Change By: Kohsuke Kawaguchi (13/May/14 12:45 AM) Assignee: MatthiasKarl KohsukeKawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-22988) IllegalArgumentException: URI is not hierarchical (from Docker.build)
Kohsuke Kawaguchi resolved JENKINS-22988 as Fixed IllegalArgumentException: URI is not hierarchical (from Docker.build) Fixed. Change By: Kohsuke Kawaguchi (13/May/14 12:45 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-22990) NPE from PluginManager.isInstalled
Kohsuke Kawaguchi commented on JENKINS-22990 NPE from PluginManager.isInstalled As this test is in our internal repository, I'm taking this over. I got the problem reproduced. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22685) Jenkins cannot restart Windows service
JCK edited a comment on JENKINS-22685 Jenkins cannot restart Windows service Pull request: https://github.com/jenkinsci/jenkins/pull/1238 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-22990) NPE from PluginManager.isInstalled
Kohsuke Kawaguchi resolved JENKINS-22990 as Fixed NPE from PluginManager.isInstalled Fixed in 1.2 Change By: Kohsuke Kawaguchi (13/May/14 1:41 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [people-redirector] (JENKINS-22992) people cannot show users,
desmond mak created JENKINS-22992 people cannot show users, Issue Type: Bug Assignee: Unassigned Attachments: computation in progress.png Components: people-redirector Created: 13/May/14 1:52 AM Description: When i go to People, only part of the users but not all users are shown. The computation bar is red in colour for more than 15mins. Does it mean it cannot load the users? I cannot delete users and modify users' passwords. Please help. Environment: centos 6.4 Project: Jenkins Priority: Critical Reporter: desmond mak This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-19845) EC2 plugin incorrectly reports current instance count
David Walend commented on JENKINS-19845 EC2 plugin incorrectly reports current instance count I've got similar symptoms, but not exactly the same. Everything was fine up until about a month ago. I didn't originally set a cap, tried setting the cap to 5, (with only the Jenkins server and one other machine are running in this account). No machine is starting when I start a new build (but the new job is queued). I get the log I've pasted below. I upgraded everything. No luck. Any thoughts? Thanks, Dave May 13, 2014 3:20:51 AM INFO hudson.plugins.ec2.EC2Cloud provision Excess workload after pending Spot instances: 1 May 13, 2014 3:20:51 AM INFO hudson.plugins.ec2.EC2Cloud addProvisionedSlave AMI Instance cap of 1 reached for ami ami-e318378a, not provisioning. May 13, 2014 3:20:51 AM INFO hudson.plugins.ec2.EC2Cloud provision Excess workload after pending Spot instances: 1 May 13, 2014 3:20:51 AM INFO hudson.plugins.ec2.EC2Cloud addProvisionedSlave AMI Instance cap of 1 reached for ami ami-e318378a, not provisioning. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-step] (JENKINS-22987) Fork of docker-java under jenkins namespace?
Marcus Linke resolved JENKINS-22987 as Duplicate Fork of docker-java under jenkins namespace? Change By: Marcus Linke (13/May/14 5:22 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/d/optout.
[JIRA] [docker-build-step] (JENKINS-22986) Fork of docker-java under jenkins namespace?
Marcus Linke closed JENKINS-22986 as Duplicate Fork of docker-java under jenkins namespace? Change By: Marcus Linke (13/May/14 5:23 AM) Status: Open Closed Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22867) localized help messages not found for Invoke top-level Maven targets
Harald Albers resolved JENKINS-22867 as Fixed localized help messages not found for Invoke top-level Maven targets Thanks! Change By: Harald Albers (13/May/14 5:57 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
