[JIRA] [core] (JENKINS-20682) Starting Jenkins with defined --webroot or JETTY_HOME not working.
Simon Westcott assigned JENKINS-20682 to Unassigned Starting Jenkins with defined --webroot or JETTY_HOME not working. Change By: Simon Westcott (12/Dec/13 10:50 PM) Assignee: SimonWestcott This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-12765) ChromeDriver won't install on slave
Simon Westcott commented on JENKINS-12765 ChromeDriver wont install on slave Same issue for me, Installing chromedriver to /var/lib/jenkins/slaves/tools/chromedriver ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins. java.lang.NullPointerException at org.jenkinsci.plugins.chromedriver.DownloadableImpl.getType(DownloadableImpl.java:91) at org.jenkinsci.plugins.chromedriver.DownloadableImpl.select(DownloadableImpl.java:78) at org.jenkinsci.plugins.chromedriver.DownloadableImpl.resolve(DownloadableImpl.java:35) at org.jenkinsci.plugins.chromedriver.ComputerListenerImpl.process(ComputerListenerImpl.java:43) at org.jenkinsci.plugins.chromedriver.ComputerListenerImpl.preOnline(ComputerListenerImpl.java:34) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:370) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:317) at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:454) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:293) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:200) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) ERROR: Connection terminated This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14469) anit-pattern for build exclusions
Simon Westcott updated JENKINS-14469 anit-pattern for build exclusions Change By: Simon Westcott (10/Aug/12 5:48 PM) Issue Type: Improvement NewFeature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14712) Bulk Builder plugin doesn't show views created within a nested view
Simon Westcott commented on JENKINS-14712 Bulk Builder plugin doesnt show views created within a nested view Hi Tillu, I'm not familiar with nested views. Are these native to Jenkins or are you using the Nested View plugin @ https://wiki.jenkins-ci.org/display/JENKINS/Nested+View+Plugin? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14712) Bulk Builder plugin doesn't show views created within a nested view
Simon Westcott updated JENKINS-14712 Bulk Builder plugin doesnt show views created within a nested view Ah, I see. Updating the type to new feature as integration with other plugins was not previously planned. Change By: Simon Westcott (08/Aug/12 3:41 PM) Issue Type: Bug NewFeature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14712) Bulk Builder plugin doesn't show views created within a nested view
Simon Westcott commented on JENKINS-14712 Bulk Builder plugin doesnt show views created within a nested view Note to self: https://wiki.jenkins-ci.org/display/JENKINS/Dependencies+among+plugins This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14712) Bulk Builder plugin doesn't show views created within a nested view
Simon Westcott commented on JENKINS-14712 Bulk Builder plugin doesnt show views created within a nested view I don't dispute that, however adding support for the nested view plugin is a new feature rather than a bug. Patches on Github are most welcome if this is causing particular pain for yourself. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14697) Can't use an existing view in a nested view - Nested view component
Simon Westcott commented on JENKINS-14697 Cant use an existing view in a nested view - Nested view component Is this a dup of JENKINS-6961? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13321) Fitnesse tests with no result doesn't fail the build
Simon Westcott created JENKINS-13321: Summary: Fitnesse tests with no result doesn't fail the build Key: JENKINS-13321 URL: https://issues.jenkins-ci.org/browse/JENKINS-13321 Project: Jenkins Issue Type: Bug Components: fitnesse Reporter: Simon Westcott Fitnesse plugin 1.6 When Fitnesse returns the following result (no tests executed), Jenkins should probably mark the build as failed/unstable. {noformat} testResults FitNesseVersionv20110104/FitNesseVersion rootPathStagingRegression/rootPath finalCounts right0/right wrong0/wrong ignores0/ignores exceptions0/exceptions /finalCounts totalRunTimeInMillis0/totalRunTimeInMillis /testResults {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12779) Error when try to run all jobs in a view
[ https://issues.jenkins-ci.org/browse/JENKINS-12779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159816#comment-159816 ] Simon Westcott commented on JENKINS-12779: -- Hi Alper, I've not been able to replicate this yet. Could you tell me what version of bulk builder you're using and the full name of the view you're attempting to build? Thanks. Error when try to run all jobs in a view Key: JENKINS-12779 URL: https://issues.jenkins-ci.org/browse/JENKINS-12779 Project: Jenkins Issue Type: Bug Components: bulk-builder Affects Versions: current Environment: Ubuntu 10.04 Server Reporter: Alper Tekinap Assignee: Simon Westcott When try to run all jobs in a view it gives an error like: Status Code: 500 Exception: Stacktrace: java.lang.IllegalArgumentException: No enum const class org.jvnet.hudson.plugins.bulkbuilder.model.BuildType.ON at java.lang.Enum.valueOf(Enum.java:214) at org.jvnet.hudson.plugins.bulkbuilder.model.BuildType.valueOf(BuildType.java:31) at org.jvnet.hudson.plugins.bulkbuilder.BulkBuilderAction.doBuild(BulkBuilderAction.java:93) 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:616) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:282) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:149) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:88) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:477) at org.kohsuke.stapler.Stapler.service(Stapler.java:159) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:244) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at java.lang.Thread.run(Thread.java:636) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12968) Bulk-Builder does not passed parameters to builds
[ https://issues.jenkins-ci.org/browse/JENKINS-12968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Westcott resolved JENKINS-12968. -- Resolution: Fixed Resolved on master Bulk-Builder does not passed parameters to builds - Key: JENKINS-12968 URL: https://issues.jenkins-ci.org/browse/JENKINS-12968 Project: Jenkins Issue Type: Bug Components: bulk-builder Affects Versions: current Reporter: Chris Stylianou Assignee: Simon Westcott When using the webform or directly through the external interface, parameters are not being passed to the build jobs -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12968) Bulk-Builder does not passed parameters to builds
[ https://issues.jenkins-ci.org/browse/JENKINS-12968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159819#comment-159819 ] Simon Westcott commented on JENKINS-12968: -- Version 1.5 is available @ http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jvnet/hudson/plugins/bulk-builder/1.5/. This should be available in the update center within 24/48hrs. Bulk-Builder does not passed parameters to builds - Key: JENKINS-12968 URL: https://issues.jenkins-ci.org/browse/JENKINS-12968 Project: Jenkins Issue Type: Bug Components: bulk-builder Affects Versions: current Reporter: Chris Stylianou Assignee: Simon Westcott When using the webform or directly through the external interface, parameters are not being passed to the build jobs -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12968) Bulk-Builder does not passed parameters to builds
[ https://issues.jenkins-ci.org/browse/JENKINS-12968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Westcott closed JENKINS-12968. Bulk-Builder does not passed parameters to builds - Key: JENKINS-12968 URL: https://issues.jenkins-ci.org/browse/JENKINS-12968 Project: Jenkins Issue Type: Bug Components: bulk-builder Affects Versions: current Reporter: Chris Stylianou Assignee: Simon Westcott When using the webform or directly through the external interface, parameters are not being passed to the build jobs -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10870) Fitnesse exceptions not failing a build
[ https://issues.jenkins-ci.org/browse/JENKINS-10870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Westcott resolved JENKINS-10870. -- Resolution: Fixed Fixed in 1.5 Fitnesse exceptions not failing a build --- Key: JENKINS-10870 URL: https://issues.jenkins-ci.org/browse/JENKINS-10870 Project: Jenkins Issue Type: Bug Components: fitnesse Environment: Plugins version 1.4 Reporter: Simon Westcott Assignee: Simon Westcott The plugin is not treating Fitnesse exceptions as failures, instead they are being reported as ignored/skipped and the build is remains green. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10870) Fitnesse exceptions not failing a build
[ https://issues.jenkins-ci.org/browse/JENKINS-10870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Westcott closed JENKINS-10870. Fitnesse exceptions not failing a build --- Key: JENKINS-10870 URL: https://issues.jenkins-ci.org/browse/JENKINS-10870 Project: Jenkins Issue Type: Bug Components: fitnesse Environment: Plugins version 1.4 Reporter: Simon Westcott Assignee: Simon Westcott The plugin is not treating Fitnesse exceptions as failures, instead they are being reported as ignored/skipped and the build is remains green. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira