[JIRA] [github] (JENKINS-23662) Github Plugin 1.9 broke webhook trigger
Reynald Borer commented on JENKINS-23662 Github Plugin 1.9 broke webhook trigger Same here with Jenkins LTS 1.532.2 (not the latest LTS btw). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21881) Make X-Frame-Options configurable
Reynald Borer commented on JENKINS-21881 Make X-Frame-Options configurable As Jesse said, setting the header to ALLOW-FROM URI is not supported by all browsers (at least Chrome and Safari does not support it), so I think a better option would be to have a way to disable this header in core directly instead, like the CSRF prevention. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [core] (JENKINS-21881) Make X-Frame-Options configurable
Reynald Borer commented on JENKINS-21881 Make X-Frame-Options configurable @jglick setting a blank header seems to work for Chrome. It's a big hack IMHO, but at least it helps solving the issue This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [security] (JENKINS-21842) Jenkins Dashboard/Panel not visible in IFRAMES anymore since 1.551
Reynald Borer commented on JENKINS-21842 Jenkins Dashboard/Panel not visible in IFRAMES anymore since 1.551 I'm having the same issue here, and unfortunately the X-Frame-Filter plugin cannot help as it's adding another X-Frame-Options header. This plugin should use st:setHeader ... to replace the header content instead (https://github.com/stapler/stapler/blob/master/jelly/src/main/java/org/kohsuke/stapler/jelly/SetHeaderTag.java) That of course does not solve this issue, seems stapler does not provide any tag to remove a header. And the HttpServletResponse API does not provide this ability too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [security] (JENKINS-21842) Jenkins Dashboard/Panel not visible in IFRAMES anymore since 1.551
Reynald Borer commented on JENKINS-21842 Jenkins Dashboard/Panel not visible in IFRAMES anymore since 1.551 Ok thanks for the clarification and sorry for my misunderstanding then. I also vote in favor of a configuration parameter as proposed in x-frame-filter 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] [email-ext] (JENKINS-17910) groovy.lang.MissingMethodException in sidepanel.jelly
Reynald Borer commented on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly Thanks for the fix, I may test it on my Jenkins installation if you can provide me the hpi to use. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [dashboard-view] (JENKINS-18023) dashboard -view does not honour the prefix commandline parameter
Reynald Borer commented on JENKINS-18023 dashboard -view does not honour the prefix commandline parameter Same problem here, was also working with previous version of the plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dashboard-view] (JENKINS-18023) dashboard -view does not honour the prefix commandline parameter
Reynald Borer commented on JENKINS-18023 dashboard -view does not honour the prefix commandline parameter It's a regression from the following pull request: https://github.com/jenkinsci/dashboard-view-plugin/pull/15/ If I revert the jobLink.jelly manually on my installation, icons work as expected again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [email-ext] (JENKINS-17910) groovy.lang.MissingMethodException in sidepanel.jelly
Reynald Borer commented on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly I can confirm that downgrading Email-ext plugin to version 2.28 solved my problem. Jenkins has been running this version since more than 8 hours, sending lots of email using groovy template, and no problem so far. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [dashboard-view] (JENKINS-18025) View: when Recurse in subfolders is true, view is empty and logs full of java.lang.ClassCastException: hudson.maven.MavenModule cannot be cast to hudson.model
Reynald Borer created JENKINS-18025 View: when Recurse in subfolders is true, view is empty and logs full of java.lang.ClassCastException: hudson.maven.MavenModule cannot be cast to hudson.model.TopLevelItem Issue Type: Bug Assignee: Peter Hayes Components: dashboard-view Created: 21/May/13 11:49 AM Description: One of my dashboard view is defined like the following hudson.plugins.view.dashboard.Dashboard plugin="dashboard-view@2.5" owner class="hudson" reference="../../.."/ name+Continuous Integration/name filterExecutorsfalse/filterExecutors filterQueuefalse/filterQueue properties class="hudson.model.View$PropertyList"/ jobNames comparator class="hudson.util.CaseInsensitiveComparator"/ /jobNames jobFilters/ columns hudson.views.StatusColumn/ hudson.views.WeatherColumn/ hudson.views.JobColumn/ hudson.views.LastSuccessColumn/ hudson.views.LastFailureColumn/ hudson.views.LastDurationColumn/ hudson.views.BuildButtonColumn/ de.fspengler.hudson.pview.ConsoleViewColumn plugin="hudson-pview-plugin@1.8"/ hudson.plugins.projectstats.column.NumBuildsColumn plugin="project-stats-plugin@0.4"/ /columns includeRegex(?!(_env_.*|.*single_selenium_test.*|stx2|apache|check|nexus|ocs)).*/includeRegex recursetrue/recurse useCssStylefalse/useCssStyle includeStdJobListfalse/includeStdJobList leftPortletWidth50%/leftPortletWidth rightPortletWidth50%/rightPortletWidth leftPortlets/ rightPortlets/ topPortlets hudson.plugins.view.dashboard.core.JobsPortlet iddashboard_portlet_6828/id nameJobs Grid/name /hudson.plugins.view.dashboard.core.JobsPortlet /topPortlets bottomPortlets/ /hudson.plugins.view.dashboard.Dashboard When I try to load this view, the job list is empty. The logs are full of the following exception: WARNING: Caught exception evaluating: it.allViewJobNamesAsJson in /jenkins/. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.parser.EscapingExpression.evaluate(EscapingExpression.java:24) at org.apache.commons.jelly.impl.ExpressionScript.run(ExpressionScript.java:66) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at
[JIRA] [core] (JENKINS-17910) groovy.lang.MissingMethodException in sidepanel.jelly
Reynald Borer commented on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly Same issue here with Jenkins 1.514. javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/run/jenkins/war/WEB-INF/lib/jenkins-core-1.514.jar!/hudson/model/View/sidepanel.jelly:75:50: st:include No signature of method: java.lang.String.queue() is applicable for argument types: (java.util.LinkedHashMap) values: [[items:[hudson.model.Queue$BlockedItem:hudson.model.FreeStyleProject@4e416cf7[_TnAT_at1_selenium_NTJ_IKKI]:A lready running 2 builds across all nodes, ...]]] Possible solutions: use([Ljava.lang.Object;), size(), next(), grep(), size(), every() at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) 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.tryInvoke(Stapler.java:736) 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: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.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:36) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:32) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:206) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) 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:48) 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.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at
[JIRA] (JENKINS-14362) 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException
Reynald Borer commented on JENKINS-14362 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException Hi, I'm also experiencing this issue with Jenkins version 1.506 on the following environment: Jenkins 1.506 Debian Squeeze 64 bits (Linux buildsrv1 3.2.0-0.bpo.2-amd64) Java(TM) SE Runtime Environment (build 1.6.0_37-b06) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-15734) NullPointerException in ScmSyncConfigurationPlugin.getInstance
Reynald Borer created JENKINS-15734 NullPointerException in ScmSyncConfigurationPlugin.getInstance Issue Type: Bug Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 06/Nov/12 9:44 AM Description: Hi, I've the following NPE happening when scm-sync-configuration-plugin, making my Jenkins installation unusable (I've disabled this plugin). WARNING: Untrapped Error in Servlet java.lang.NullPointerException at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationPlugin.getInstance(ScmSyncConfigurationPlugin.java:272) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:25) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) 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.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:135) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) 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 org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) 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:215) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:138) at
[JIRA] (JENKINS-15734) NullPointerException in ScmSyncConfigurationPlugin.getInstance
Reynald Borer updated JENKINS-15734 NullPointerException in ScmSyncConfigurationPlugin.getInstance Change By: Reynald Borer (06/Nov/12 9:45 AM) Environment: Jenkins1.489onDebianSqueeze,scm-sync-configuration-pluginversion0. 0. 6.1 This message is automatically generated by JIRA. 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-13546) buildWithParameters: return a JSON string when client request it through content-type header
Reynald Borer created JENKINS-13546: --- Summary: buildWithParameters: return a JSON string when client request it through content-type header Key: JENKINS-13546 URL: https://issues.jenkins-ci.org/browse/JENKINS-13546 Project: Jenkins Issue Type: Improvement Components: core Affects Versions: current Environment: Jenkins 1.460 on Debian Squeeze Reporter: Reynald Borer Right now, every call on the buildWithParameters URL will always redirect to the job page on success. If this API is queried through an Ajax call, it should return a JSON output of the current job instead. This can easily be detected based on the Content-Type http header sent by the client. This is useful for example if one wants to trigger a parametrized build from jQuery, and parse the result. Right now, jQuery will always get back the HTML page of the job, which makes it hard to do any error handling. -- 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-10846) Show unstable builds as yellow (small change to 2 files)
[ https://issues.jenkins-ci.org/browse/JENKINS-10846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161747#comment-161747 ] Reynald Borer commented on JENKINS-10846: - I've made a similar patch myself, before discovering this one was already available. Anyway, I think this feature should really be merged, without it it's hard to make a distinction between failed builds and unstable builds. Show unstable builds as yellow (small change to 2 files) Key: JENKINS-10846 URL: https://issues.jenkins-ci.org/browse/JENKINS-10846 Project: Jenkins Issue Type: Patch Components: radiatorview Reporter: Oliver Drake Assignee: howama Priority: Minor Attachments: making_unstable_builds_yellow.diff Added a new css entry (.unstable) and changed getStatus() to return an unstable string. Currently the colors for unstable and claimed are identical which is probably not ideal. I'm currently working on a slightly different color scheme on my local copy (same as this but claimed is orange, and unstable is yellow). I might submit a seperate patch for this once I'm happy with it. Might be nice to make all the colors configurable, I'd be happy to give this a go. Addresses: https://issues.jenkins-ci.org/browse/JENKINS-10614 https://issues.jenkins-ci.org/browse/JENKINS-9772 diff taken from: plugins/radiatorview/src. Let me know if you need anything else :) -- 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-13504) Use HTTP FitNesse timeout for the connection
Reynald Borer created JENKINS-13504: --- Summary: Use HTTP FitNesse timeout for the connection Key: JENKINS-13504 URL: https://issues.jenkins-ci.org/browse/JENKINS-13504 Project: Jenkins Issue Type: Improvement Components: fitnesse Affects Versions: current Environment: Jenkins 1.460 on Debian Squeeze Reporter: Reynald Borer Priority: Minor FitNesse plugin allow to define a timeout for remote tests execution. This pull request reuse this defined timeout inside the HTTP connection too. This is useful if the default HTTP read timeout of the JVM has been defined. -- 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-13504) Use HTTP FitNesse timeout for the connection
[ https://issues.jenkins-ci.org/browse/JENKINS-13504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161748#comment-161748 ] Reynald Borer commented on JENKINS-13504: - Made a pull request with a patch proposal at https://github.com/jenkinsci/fitnesse-plugin/pull/1 Use HTTP FitNesse timeout for the connection Key: JENKINS-13504 URL: https://issues.jenkins-ci.org/browse/JENKINS-13504 Project: Jenkins Issue Type: Improvement Components: fitnesse Affects Versions: current Environment: Jenkins 1.460 on Debian Squeeze Reporter: Reynald Borer Priority: Minor FitNesse plugin allow to define a timeout for remote tests execution. This pull request reuse this defined timeout inside the HTTP connection too. This is useful if the default HTTP read timeout of the JVM has been defined. -- 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-12514) .hpi versus .jpi causes inability to upgrade Subversion Plugin
[ https://issues.jenkins-ci.org/browse/JENKINS-12514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161248#comment-161248 ] Reynald Borer commented on JENKINS-12514: - Still happening with Jenkins 1.458 running under debian squeeze (with the debian package). .hpi versus .jpi causes inability to upgrade Subversion Plugin -- Key: JENKINS-12514 URL: https://issues.jenkins-ci.org/browse/JENKINS-12514 Project: Jenkins Issue Type: Bug Components: update-center Environment: Ubuntu 11.10, OpenJDK 1.6.0_23, Tomcat 7.0.21, Jenkins 1.448 1.449 Jenkins 1.456 on Windows Server 2003 64-bit, Sun JDK 6.0.260.3 Reporter: Charlie Huggard Assignee: Kohsuke Kawaguchi Priority: Blocker Reproduction: $JENKINS_HOME/plugins: subversion (directory), subversion.hpi 1) Open http://root/pluginManager. Update Subversion plugin from 1.34 - 1.37 using download now and install after restart button. $JENKINS_HOME/plugins: subversion (directory), subversion.bak (1.34), subversion.hpi.pinned, subversion.jpi (1.37) 2) Restart Tomcat/Jenkins $JENKINS_HOME/plugins: subversion (directory), subversion.bak (1.34), subversion.hpi (1.34) subversion.hpi.pinned, subversion.jpi (1.37) 3) PluginManager still reports old version Should note that the logs report: INFO: Ignoring /ci/jenkins-home/plugins/subversion.jpi because /ci/jenkins-home/plugins/subversion.hpi is already loaded Also the plugin is broken at this point with a NoClassDefFound on org/tmatesoft/svn/core/SVNException Clean State: 1) /etc/init.d/tomcat7 stop 2) cd $JENKINS_HOME/plugins 3) rm subversion* 4) /etc/init.d/tomcat7 start Workaround: 1) Restore clean state 2) Update plugin 3) Stop tomcat/jenkins 4) cd $JENKINS_HOME/plugins 5) mv subversion.jpi subversion.hpi 6) Start tomcat/jenkins -- 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-12787) LOADING overlay does not go away on the Configure System page
[ https://issues.jenkins-ci.org/browse/JENKINS-12787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160293#comment-160293 ] Reynald Borer commented on JENKINS-12787: - Mmhh, now my issue with the Jira plugin is fixed with Jenkins 1.455... LOADING overlay does not go away on the Configure System page - Key: JENKINS-12787 URL: https://issues.jenkins-ci.org/browse/JENKINS-12787 Project: Jenkins Issue Type: Bug Components: gui Affects Versions: current Environment: Jenkins Reporter: Joshua Davis Priority: Blocker Labels: gui, jenkins After navigating to Manage-Configure System, the LOADING overlay never goes away. It is impossible to save any configuration changes. EXPECTED: * You can save your global configuration. Here is the stack trace from Chrome's JS console: {code} Uncaught TypeError: Object #Object has no method 'findMatchingInput' (anonymous function) e.targetUrl hudson-behavior.js:338 registerValidator hudson-behavior.js:343 apply behavior.js:73 (anonymous function) behavior.js:79 Behaviour.applySubtree behavior.js:68 Behaviour.applybehavior.js:54 (anonymous function)behavior.js:49 window.onload {code} -- 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-12787) LOADING overlay does not go away on the Configure System page
[ https://issues.jenkins-ci.org/browse/JENKINS-12787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159845#comment-159845 ] Reynald Borer commented on JENKINS-12787: - Same happens here with Jenkins 1.452 and FF10, pretty annoying. LOADING overlay does not go away on the Configure System page - Key: JENKINS-12787 URL: https://issues.jenkins-ci.org/browse/JENKINS-12787 Project: Jenkins Issue Type: Bug Components: gui Affects Versions: current Environment: Jenkins Reporter: Joshua Davis Labels: gui, jenkins After navigating to Manage-Configure System, the LOADING overlay never goes away. It is impossible to save any configuration changes. EXPECTED: * You can save your global configuration. Here is the stack trace from Chrome's JS console: {code} Uncaught TypeError: Object #Object has no method 'findMatchingInput' (anonymous function) e.targetUrl hudson-behavior.js:338 registerValidator hudson-behavior.js:343 apply behavior.js:73 (anonymous function) behavior.js:79 Behaviour.applySubtree behavior.js:68 Behaviour.applybehavior.js:54 (anonymous function)behavior.js:49 window.onload {code} -- 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-12787) LOADING overlay does not go away on the Configure System page
[ https://issues.jenkins-ci.org/browse/JENKINS-12787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159847#comment-159847 ] Reynald Borer commented on JENKINS-12787: - This seems related to the JIRA Plugin. If I disable it then I can access again the configuration page. LOADING overlay does not go away on the Configure System page - Key: JENKINS-12787 URL: https://issues.jenkins-ci.org/browse/JENKINS-12787 Project: Jenkins Issue Type: Bug Components: gui Affects Versions: current Environment: Jenkins Reporter: Joshua Davis Labels: gui, jenkins After navigating to Manage-Configure System, the LOADING overlay never goes away. It is impossible to save any configuration changes. EXPECTED: * You can save your global configuration. Here is the stack trace from Chrome's JS console: {code} Uncaught TypeError: Object #Object has no method 'findMatchingInput' (anonymous function) e.targetUrl hudson-behavior.js:338 registerValidator hudson-behavior.js:343 apply behavior.js:73 (anonymous function) behavior.js:79 Behaviour.applySubtree behavior.js:68 Behaviour.applybehavior.js:54 (anonymous function)behavior.js:49 window.onload {code} -- 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