-
Suggestion
-
Resolution: Timed out
-
None
-
0
-
2
-
Issue
Currently, Bamboo does not provide an endpoint listing repositories (https://jira.atlassian.com/browse/BAM-20007 - (REST) No endpoint available for retrieving Linked Repository ID(s)). Even after gathering the repository ID information, extracted from Bamboo UI or web scraping, testing repository connection still need to much effort from users through REST API.
How to repository test connection
Based on Bamboo REST API documentation, there is an endpoint (http://myhost.com:8085/bamboo/rest/api/latest/repository/testConnection [PUT]) in which should provide this information easily, however, it is required to provide not only the repository ID information but also the pluginKey and repositoryURL (when testing connection against Git repository as Repository Host)
# replace "5341185" with "repository id" # replace "file:///nothing" with repository URL curl -k -u admin:admin \ -H 'Content-type: application/json' \ -H 'Accept: application/json' \ -d '{"repositoryId":"5341185","selectedRepository":"com.atlassian.bamboo.plugins.atlassian-bamboo-plugin-git:gitv2","repository.git.repositoryUrl":"file:///nothing"}' \ -X PUT http://localhost:8085/rest/api/latest/repository/testConnection
- selectedRepository attribute from payload is not available in Bamboo's UI, making it difficult for user to make use of the endpoint
- repository.git.repositoryUrl since providing repositoryID information, repository URL seems to be a redundant attribute since repository IDs are unique across Bamboo
Suggestion
The endpoint should only consume the repository ID, e.g:
curl -k -u admin:admin \ -H 'Accept: application/json' \ -X PUT http://localhost:8085/rest/api/latest/repository/{repositoryId}/testConnection
As response, Bamboo should provide information about the repository, e.g:
{ "repositoryID": "1234567890", "repositoryName": "Name given in Bamboo" "repositoryHost": "Git", "repositoryURL": "ssh://git@hostname/proj/repository.git", "branch": "master", "testConnection": "Successful" }
Form Name |
---|
Hi,
Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.
This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers).
Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Bamboo team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested.
Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.
Thank you,
Bamboo Team