[JIRA] (JENKINS-61236) Cannot use HTTP endpoint and custom port

[cl...@amazon.com (JIRA)]

Title: Message Title

James Clem updated an issue   Jenkins / JENKINS-61236 Cannot use HTTP endpoint and custom port Change By: James Clem The Bitbucket plugin does not appear to retain custom port/protocol configurations for Bitbucket Server. Instead it always defaults back to HTTPS/port 443. This wouldn't typically be an issue, but I'm using an internal self-signed cert and even though it's been imported into my Java keystore, I still can't seem to connect via that method (separate issue). As a workaround, I am trying to connect to an internally-exposed Kubernetes service endpoint [http://bitbucket-svc:7990.|http://bitbucket-svc:79990.] I am able to connect to the endpoint at the Manage System configuration page and even when I'm creating my Jenkins pipeline job. However, when I try to build the project, I can see in the logs it's connecting via HTTPS. Steps to replicate: * Configure the Bitbucket server location to use the default Bitbucket HTTP port 7990. * Connect successfully from Manage System and pipeline job configuration * Click "Build Now" and observe the protocol/port the plugin tries to connect to Add Comment   This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204791.1582725290000.7155.1582726800231%40Atlassian.JIRA.