[JIRA] (JENKINS-61854) "Test Ldap Settings" button stopped functioning.
Title: Message Title William Gillaspy commented on JENKINS-61854 Re: "Test Ldap Settings" button stopped functioning. Ramon Leon looks like it is working as expected. Thank y'all for the fix! William Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205717.1586439894000.15666.1587552420373%40Atlassian.JIRA.
[JIRA] (JENKINS-61854) "Test Ldap Settings" button stopped functioning.
Title: Message Title
William Gillaspy edited a comment on JENKINS-61854
Re: "Test Ldap Settings" button stopped functioning.
Thanks Baptiste.Button and form is functional. Testing with the same user/password that I'm already logged in as results in:!image-2020-04-18-07-06-52-382.png|width=784,height=154!Looking for that id in the l og log :{code:java}Apr 18, 2020 7:04:03 AM WARNING hudson.init.impl.InstallUncaughtExceptionHandler handleExceptionCaught unhandled exception with ID 7a959e7f-f9aa-4909-a7ed-aae6384e4054net.sf.json.JSONException: null object at net.sf.json.JSONObject.verifyIsNull(JSONObject.java:2688) at net.sf.json.JSONObject.getJSONObject(JSONObject.java:1998) at hudson.security.LDAPSecurityRealm$DescriptorImpl.doValidate(LDAPSecurityRealm.java:1629) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:755) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1617) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at com.splunk.splunkjenkins.WebPostAccessLogger.doFilter(WebPostAccessLogger.java:39) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:248) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.security.ResourceDomainFilter.doFilter(ResourceDomainFilter.java:76) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:239) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:215) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:88) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:114) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151)
[JIRA] (JENKINS-61854) "Test Ldap Settings" button stopped functioning.
Title: Message Title William Gillaspy commented on JENKINS-61854 Re: "Test Ldap Settings" button stopped functioning. Thanks Baptiste. Button and form is functional. Testing with the same user/password that I'm already logged in as results in: Looking for that id in the l og: Apr 18, 2020 7:04:03 AM WARNING hudson.init.impl.InstallUncaughtExceptionHandler handleExceptionCaught unhandled exception with ID 7a959e7f-f9aa-4909-a7ed-aae6384e4054 net.sf.json.JSONException: null object at net.sf.json.JSONObject.verifyIsNull(JSONObject.java:2688) at net.sf.json.JSONObject.getJSONObject(JSONObject.java:1998) at hudson.security.LDAPSecurityRealm$DescriptorImpl.doValidate(LDAPSecurityRealm.java:1629) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:755) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1617) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at com.splunk.splunkjenkins.WebPostAccessLogger.doFilter(WebPostAccessLogger.java:39) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:248) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.security.ResourceDomainFilter.doFilter(ResourceDomainFilter.java:76) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:239) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:215) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:88) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:114) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.telemetry
[JIRA] (JENKINS-61854) "Test Ldap Settings" button stopped functioning.
Title: Message Title William Gillaspy updated an issue Jenkins / JENKINS-61854 "Test Ldap Settings" button stopped functioning. Change By: William Gillaspy Attachment: image-2020-04-18-07-06-52-382.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205717.1586439894000.13517.1587208020549%40Atlassian.JIRA.
[JIRA] (JENKINS-61854) "Test Ldap Settings" button stopped functioning.
Title: Message Title William Gillaspy created an issue Jenkins / JENKINS-61854 "Test Ldap Settings" button stopped functioning. Issue Type: Bug Assignee: Unassigned Components: ldap-plugin Created: 2020-04-09 13:44 Environment: Jenkins 2.230 Labels: ldap Priority: Critical Reporter: William Gillaspy Clicking the "Test LDAP Settings" button in the "Configure Global Security" page no longer functions. Expected: A form to appear requesting a user to test against. F12 console reveals: Uncaught TypeError: Connot read property 'realm' of undefined. at ldapValidateButton (validate.js:24) at HTMLButtonElement.onClick((index):140) Add Comment
[JIRA] (JENKINS-58862) Github Branch Source Plugin always references https://api.github.com
Title: Message Title William Gillaspy commented on JENKINS-58862 Re: Github Branch Source Plugin always references https://api.github.com Looks good. Thanks for the help! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201177.1565278734000.3699.1565897160477%40Atlassian.JIRA.
[JIRA] (JENKINS-58862) Github Branch Source Plugin always references https://api.github.com
Title: Message Title William Gillaspy commented on JENKINS-58862 Re: Github Branch Source Plugin always references https://api.github.com Karl Shultz I'm using the "Clone or Download" button and copying the "Clone with HTTPS" url of the repository. Example: https://git.company.com/TheOrg/TheProject.git Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201177.1565278734000.11387.1565363100168%40Atlassian.JIRA.
[JIRA] (JENKINS-58862) Github Branch Source Plugin always references https://api.github.com
Title: Message Title William Gillaspy commented on JENKINS-58862 Re: Github Branch Source Plugin always references https://api.github.com Devin Nusbaum Yes, it does not seem to be computing the API URI when the local github URL is put into the Repository HTTPS URL field. The only other information I can think to add is that I am using credentials. Which always fails since it's trying against https://api.github.com instead of https://git.company.com/api/v3/ even when the Repository HTTPS URL is set to https://git.company.com/owner/repo Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201177.1565278734000.11365.1565360160214%40Atlassian.JIRA.
[JIRA] (JENKINS-58862) Github Branch Source Plugin always references https://api.github.com
Title: Message Title William Gillaspy commented on JENKINS-58862 Re: Github Branch Source Plugin always references https://api.github.com Devin Nusbaum I didn't put two and two together on the Repository Scan radio button. That does work. Since that feature is deprecated, what is the recommendation for setting the API endpoint in the future? Thank y'all for the assistance. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201177.1565278734000.11352.1565358540337%40Atlassian.JIRA.
[JIRA] (JENKINS-58862) Github Branch Source Plugin always references https://api.github.com
Title: Message Title William Gillaspy commented on JENKINS-58862 Re: Github Branch Source Plugin always references https://api.github.com Hello Vivek Pandey. Sorry about that. Steps: New Item > Multi-branch Pipeline > Branch Source > Add source > GitHub 2.5.4 -> Allows user to choose API Endpoint 2.5.5 -> API Endpoint field is missing, defaults to https://api.github.com in the config.xml I've added some images to illustrate the change. Thanks! And please let me know if I need to clarify further. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201177.1565278734000.11316.1565354220195%40Atlassian.JIRA.
[JIRA] (JENKINS-58862) Github Branch Source Plugin always references https://api.github.com
Title: Message Title William Gillaspy updated an issue Jenkins / JENKINS-58862 Github Branch Source Plugin always references https://api.github.com Change By: William Gillaspy Attachment: GHBS-2.5.4.PNG Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201177.1565278734000.11308.1565354100299%40Atlassian.JIRA.
[JIRA] (JENKINS-58862) Github Branch Source Plugin always references https://api.github.com
Title: Message Title William Gillaspy updated an issue Jenkins / JENKINS-58862 Github Branch Source Plugin always references https://api.github.com Change By: William Gillaspy Attachment: GHBS-2.5.5.PNG Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201177.1565278734000.11309.1565354100314%40Atlassian.JIRA.
[JIRA] (JENKINS-58862) Github Branch Source Plugin always references https://api.github.com
Title: Message Title William Gillaspy created an issue Jenkins / JENKINS-58862 Github Branch Source Plugin always references https://api.github.com Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2019-08-08 15:38 Environment: Jenkins ver. 2.189, Github Branch Plugin ver. 2.5.5 Priority: Major Reporter: William Gillaspy Lost ability to choose self hosted github enterprise api URL (API endpoint field) in version 2.5.5. Expect to be able to set "API endpoint" (apiURL in the config.xml) to company's git enterprise api url via the project setup. In version 2.5.5 apiURL is always set to https://api.github.com I'm able to work around this problem by cloning existing projects. However, making a new project does not allow me to choose our locally host github enterprise server (the API endpoint field is gone in 2.5.5) so the project fails on repository scan since it's pointed to https://api.github.com by default instead of [https://git.company.com/api/v3 StartedStarted[Thu Aug 08 10:52:57 EDT 2019] Starting branch indexing...ERROR: [Thu Aug 08 10:52:57 EDT 2019] Could not update folder level actions from source 27a03b35-22a6-4d0c-a9f6-bc0dceb6e97bhudson.AbortException: Invalid scan credentials BUSINESS_USER/** (BUSINESS_USER_PASS_AS_TOKEN) to connect to https://api.github.com, skipping at org.jenkinsci.plugins.github_branch_source.Connector.checkConnectionValidity(Connector.java:553) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieveActions(GitHubSCMSource.java:1874) at jenkins.scm.api.SCMSource.fetchActions(SCMSource.java:848) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:592) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277) at
