[JIRA] (JENKINS-16844) Triggering a build from the context menu produces a warning when security is enabled
Jesse Glick commented on JENKINS-16844 Triggering a build from the context menu produces a warning when security is enabled @dcheckoway: any related bugs should be filed separately. 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-16844) Triggering a build from the context menu produces a warning when security is enabled
Dan Checkoway commented on JENKINS-16844 Triggering a build from the context menu produces a warning when security is enabled @Jesse Glick, I did.https://issues.jenkins-ci.org/browse/JENKINS-17110 Just noted it here since I'm pretty sure the bug was introduced with JENKINS-16844's 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-16844) Triggering a build from the context menu produces a warning when security is enabled
Dan Checkoway commented on JENKINS-16844 Triggering a build from the context menu produces a warning when security is enabled Heads-up...while this fix is much appreciated and does fix the hover-over "Build Now" in general, it has borked something else. You can no longer use the hover-over "Build Now" option on parameterized builds. It works great on non-parameterized builds, but with parameterized builds you just get a "Done." tooltippy floater and nothing happens. And this gets logged: SEVERE: Error while serving http://localhost:8082/view/Stage/job/STAGE%20-%20Deploy%20API/build java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor260.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) 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:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) 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.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 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
[JIRA] (JENKINS-16844) Triggering a build from the context menu produces a warning when security is enabled
Jesse Glick assigned JENKINS-16844 to Jesse Glick Triggering a build from the context menu produces a warning when security is enabled Change By: Jesse Glick (21/Feb/13 3:13 PM) Assignee: JesseGlick 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-16844) Triggering a build from the context menu produces a warning when security is enabled
Jesse Glick updated JENKINS-16844 Triggering a build from the context menu produces a warning when security is enabled Change By: Jesse Glick (21/Feb/13 3:15 PM) Component/s: gui Component/s: security Component/s: ldap 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-16844) Triggering a build from the context menu produces a warning when security is enabled
recampbell updated JENKINS-16844 Triggering a build from the context menu produces a warning when security is enabled My suggested patch for this. It just verifies that the referrer is the same host as what Jenkins is listening to. Change By: recampbell (21/Feb/13 10:48 PM) Attachment: allow-local-build.patch 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-16844) Triggering a build from the context menu produces a warning when security is enabled
Jesse Glick commented on JENKINS-16844 Triggering a build from the context menu produces a warning when security is enabled That suffices as a short-term workaround but the real fix is to make menu items support POST. I am working on 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-16844) Triggering a build from the context menu produces a warning when security is enabled
SCM/JIRA link daemon resolved JENKINS-16844 as Fixed Triggering a build from the context menu produces a warning when security is enabled Change By: SCM/JIRA link daemon (22/Feb/13 12:18 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/groups/opt_out.
[JIRA] (JENKINS-16844) Triggering a build from the context menu produces a warning when security is enabled
dogfood commented on JENKINS-16844 Triggering a build from the context menu produces a warning when security is enabled Integrated in jenkins_main_trunk #2291 FIXED JENKINS-16844 MenuItem.post allows context menu items like Build Now to send a POST request. (Revision b9c18a7b4c6d194645a20312352cd4d4994eafb4) Result = SUCCESS Jesse Glick : b9c18a7b4c6d194645a20312352cd4d4994eafb4 Files : changelog.html core/src/main/resources/lib/layout/task.jelly core/src/main/resources/lib/layout/breadcrumbs.js core/src/main/resources/hudson/model/AbstractProject/sidepanel.jelly core/src/main/java/jenkins/model/ModelObjectWithContextMenu.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-16844) Triggering a build from the context menu produces a warning when security is enabled
Balthasar Nebel commented on JENKINS-16844 Triggering a build from the context menu produces a warning when security is enabled I am having the same problem with Jenkins 1.502 on Linux (Oracle JDK 1.6.0_39). For some unknown reason not all my jobs are having this 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-16844) Triggering a build from the context menu produces a warning when security is enabled
Balthasar Nebel edited a comment on JENKINS-16844 Triggering a build from the context menu produces a warning when security is enabled I am having the same problem with Jenkins 1.502 on Linux (Oracle JDK 1.6.0_39). For some unknown reason not all my jobs are having this problem. The problem disappeared after going back to Jenkins 1.501. 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-16844) Triggering a build from the context menu produces a warning when security is enabled
Antonios Chalkiopoulos commented on JENKINS-16844 Triggering a build from the context menu produces a warning when security is enabled Same on here, updating to 1.502 from 1.501 makes this warning also visible. I have repository hooks that trigger the following url: curl https://ci.mysite.com/job/myjob/build?token=MY_TOKEN and this action is not performed due to the warning getting displayed 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-16844) Triggering a build from the context menu produces a warning when security is enabled
Sami Salonen updated JENKINS-16844 Triggering a build from the context menu produces a warning when security is enabled Change By: Sami Salonen (17/Feb/13 9:56 PM) Summary: Triggeringabuildfromthecontextmenuproducesawarning whensecurityisenabled Description: Hoveringmouseoverajobnamebringsupacontextmenu.Clicking BuildNow _BuildNow_ fromthecontextmenuproducesthefollowingwarninganda Proceed _Proceed_ button.Buildstartsonlyif Proceed _Proceed_ buttonispressed.Contextmenuisaccessibleatleastinjoblistview(e.g.default All _All_ view)andfromthebreadcrumb.Clicking BuildNow _BuildNow_ ontheleftmenuonajobpageworksnormally ,i . e.withoutwarnings. {{YoumustusePOSTmethodtotriggerbuilds.(Fromscriptsyoumayinsteadpassaper-projectauthenticationtoken,orauthenticatewithyourAPItoken.)Ifyouseethispage,itmaybebecauseapluginofferedaGETlink;fileabugreportforthatplugin.}} Component/s: core Component/s: security 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-16844) Triggering a build from the context menu produces a warning when security is enabled
Sami Salonen edited a comment on JENKINS-16844 Triggering a build from the context menu produces a warning when security is enabled Steps to reproduce: Start Jenkins (java -jar jenkins.war) Create a free-style project (just give a name, default configuration is fine) Trigger a build from a context menu. Works fine. Add directory server based authentication: Click Enable security in global configuration From Access Control section, select LDAP under Security Realm Fill in Server, root DN, User search base, User search filter, Group search base, Manager DN, Manager Password (For Authorization, I tried both Anyone can do anything and Matrix-based security with same effect) Trigger a build from a context menu. Warning message is displayed. 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-16844) Triggering a build from the context menu produces a warning when security is enabled
Sami Salonen updated JENKINS-16844 Triggering a build from the context menu produces a warning when security is enabled Change By: Sami Salonen (18/Feb/13 7:27 AM) Component/s: gui 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.