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

[clemj@amazon.com (JIRA)]

James Clem created an issue

Jenkins / JENKINS-61236 Cannot use HTTP endpoint and custom port Issue Type: Bug Assignee: Kristy Hughes Attachments: jenkins-bitbucket-plugin.png, Screen Shot 2020-02-26 at 8.51.31 AM.png Components: atlassian-bitbucket-server-integration-plugin Created: 2020-02-26 13:54 Environment: Jenkins 2.219 running containerized in Red Hat UBI7 7.7 base image Bitbucket Server Integration 1.0.4 Priority: Blocker Reporter: 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. As a workaround, I am trying to connect to an internally-exposed Kubernetes service endpoint http://bitbucket-svc:7990. 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 endpoint the plugin tries to connect to Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[clemj@amazon.com (JIRA)]

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 endpoint the plugin tries to connect to

Add Comment

[clemj@amazon.com (JIRA)]

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 endpoint protocol/port the plugin tries to connect to

Add Comment

[clemj@amazon.com (JIRA)]

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.

I am trying to connect to an internally-exposed Kubernetes service endpoint [http://bitbucket-svc:7990.|http://bitbucket-svc:79990.]

I am able to can 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

[clemj@amazon.com (JIRA)]

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

[dkjellin@atlassian.com (JIRA)]

Daniel Kjellin assigned an issue to Unassigned

Jenkins / JENKINS-61236 Cannot use HTTP endpoint and custom port

Change By: Daniel Kjellin Assignee: Kristy Hughes

Add Comment

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

[bplump@atlassian.com (JIRA)]

B Plump updated an issue

Jenkins / JENKINS-61236 Cannot use HTTP endpoint and custom port

Change By: B Plump Labels: tracked-by-atlassian

Add Comment