You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@devlake.apache.org by Richie <da...@gmail.com> on 2026/07/07 03:19:56 UTC

[Bug][Bamboo] Connection test fails because PrepareApiClient checks /info.json and receives 404

Hi Apache DevLake team,

I would like to report a Bamboo plugin connection issue.

Environment:
- DevLake backend: v1.0.3-beta13
- DevLake config-ui: v1.0.3-beta13
- DevLake dashboard: v1.0.3-beta13
- Deployment method: Docker Compose
- MySQL: mysql:8
- Bamboo Base URL: http://<bamboo-host>:8085
- Bamboo version: Atlassian Bamboo 10.2.12 build 100218 - 08 Dec 25

Issue:
The Bamboo connection test fails with HTTP 404.

Stack trace:
github.com/apache/incubator-devlake/plugins/bamboo/models.(*BambooConn).PrepareApiClient
/app/plugins/bamboo/models/connection.go:84
github.com/apache/incubator-devlake/helpers/pluginhelper/api.NewApiClientFromConnection
/app/helpers/pluginhelper/api/api_client.go:88
github.com/apache/incubator-devlake/plugins/bamboo/api.testConnection
/app/plugins/bamboo/api/connection_api.go:44
github.com/apache/incubator-devlake/plugins/bamboo/api.TestExistingConnection
/app/plugins/bamboo/api/connection_api.go:98

Error:
unexpected status code: 404

Verification:
The Bamboo Base URL and REST API are reachable.

The following Bamboo REST API endpoint works:

curl -i -u '<user>:<password>' http://
<bamboo-host>:8085/rest/api/latest/server

Response:

HTTP/1.1 200
Content-Type: application/xml

<restServerStatusInfo>
  <askedNodeState>RUNNING</askedNodeState>
  <clusterState>RUNNING</clusterState>
  <reindexInProgress>false</reindexInProgress>
</restServerStatusInfo>

However, this endpoint returns 404:

curl -i -u '<user>:<password>' http://<bamboo-host>:8085/info.json

Response:

HTTP/1.1 404
Content-Type: text/html;charset=UTF-8

Page not found

This suggests that the Bamboo plugin connection check may be using
/info.json during PrepareApiClient, but this endpoint is not available on
this Bamboo instance.

Expected behavior:
DevLake should validate the Bamboo connection using a standard Bamboo REST
API endpoint, such as:

/rest/api/latest/server

or:

/rest/api/latest/status

instead of failing when /info.json is not available.

Additional note:
The same issue occurred on v1.0.3-beta12. After upgrading to v1.0.3-beta13,
the issue still occurs.

Could you please confirm whether /info.json is expected to be available on
Bamboo 10.2.12, or whether the Bamboo plugin connection check should use a
standard Bamboo REST API endpoint?

Thank you.

Re: [Bug][Bamboo] Connection test fails because PrepareApiClient checks /info.json and receives 404

Posted by Klesh Wong <kl...@qq.com>.
Hi Richie,

Thanks for reporting the issue. Could you kindly file it on our GitHub 
Issues page as well?

Thank you for your support.

Best,

Klesh Wong


On 7/7/26 11:19 AM, Richie wrote:
> Hi Apache DevLake team,
>
> I would like to report a Bamboo plugin connection issue.
>
> Environment:
> - DevLake backend: v1.0.3-beta13
> - DevLake config-ui: v1.0.3-beta13
> - DevLake dashboard: v1.0.3-beta13
> - Deployment method: Docker Compose
> - MySQL: mysql:8
> - Bamboo Base URL: http://<bamboo-host>:8085
> - Bamboo version: Atlassian Bamboo 10.2.12 build 100218 - 08 Dec 25
>
> Issue:
> The Bamboo connection test fails with HTTP 404.
>
> Stack trace:
> github.com/apache/incubator-devlake/plugins/bamboo/models.(*BambooConn).PrepareApiClient
> /app/plugins/bamboo/models/connection.go:84
> github.com/apache/incubator-devlake/helpers/pluginhelper/api.NewApiClientFromConnection
> /app/helpers/pluginhelper/api/api_client.go:88
> github.com/apache/incubator-devlake/plugins/bamboo/api.testConnection
> /app/plugins/bamboo/api/connection_api.go:44
> github.com/apache/incubator-devlake/plugins/bamboo/api.TestExistingConnection
> /app/plugins/bamboo/api/connection_api.go:98
>
> Error:
> unexpected status code: 404
>
> Verification:
> The Bamboo Base URL and REST API are reachable.
>
> The following Bamboo REST API endpoint works:
>
> curl -i -u '<user>:<password>' http://
> <bamboo-host>:8085/rest/api/latest/server
>
> Response:
>
> HTTP/1.1 200
> Content-Type: application/xml
>
> <restServerStatusInfo>
>    <askedNodeState>RUNNING</askedNodeState>
>    <clusterState>RUNNING</clusterState>
>    <reindexInProgress>false</reindexInProgress>
> </restServerStatusInfo>
>
> However, this endpoint returns 404:
>
> curl -i -u '<user>:<password>' http://<bamboo-host>:8085/info.json
>
> Response:
>
> HTTP/1.1 404
> Content-Type: text/html;charset=UTF-8
>
> Page not found
>
> This suggests that the Bamboo plugin connection check may be using
> /info.json during PrepareApiClient, but this endpoint is not available on
> this Bamboo instance.
>
> Expected behavior:
> DevLake should validate the Bamboo connection using a standard Bamboo REST
> API endpoint, such as:
>
> /rest/api/latest/server
>
> or:
>
> /rest/api/latest/status
>
> instead of failing when /info.json is not available.
>
> Additional note:
> The same issue occurred on v1.0.3-beta12. After upgrading to v1.0.3-beta13,
> the issue still occurs.
>
> Could you please confirm whether /info.json is expected to be available on
> Bamboo 10.2.12, or whether the Bamboo plugin connection check should use a
> standard Bamboo REST API endpoint?
>
> Thank you.
>