Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
2.6.9
-
Bitbucket 4.8.0 on Ubuntu 18.04 x64, Windows 10 1803 x64
-
Severity 2 - Major
Description
We have problems receiving the list of remote repositories from Bitbucket 4.8.0 using sourcetree. Sourcetree is successful connect to the Bitbucket server but the list of available repositories is empty.
In our environment the Bitbucket server is "qm-Bitbucket2018", nslookup and reverse lookup is working fine.
Sourcetree call the url "http://qm-bitbucket2018/rest/api/1.0/projects?limit=1000&start=0" and Bitbucket return the correct list of projects.
{
"size": 1,
"limit": 1000,
"isLastPage": true,
"values": [{
"key": "SCT",
"id": 1,
"name": "ScanTools",
"description": "ScanTools Standardsystem",
"public": false,
"type": "NORMAL",
"links": {
"self": [
]
}
}],
"start": 0
}
After that call sourcetree calls the url "http://qm-bitbucket2018/rest/api/1.0/projects/SCT/repos?limit=30&start=1" to get the list of repositories belongs to project (in that case SCT). Bitbucket return an empty list of repositories, but there exist one repository that is accessable by user. Using browser as well as git bash clone, commit, push, pull is working without any problems.
{ "size": 0, "limit": 30, "isLastPage": true, "values": [], "start": 1 }If I do the same with a browser (Firefox) and replace "start=1" with "start=0" Bitbucket send the correct list of repositories.
{
"size": 1,
"limit": 30,
"isLastPage": true,
"values": [{
"slug": "mediaform",
"id": 1,
"name": "Mediaform",
"scmId": "git",
"state": "AVAILABLE",
"statusMessage": "Available",
"forkable": true,
"project": {
"key": "SCT",
"id": 1,
"name": "ScanTools",
"description": "ScanTools Standardsystem",
"public": false,
"type": "NORMAL",
"links": {
"self": [
]
}
},
"public": false,
"links": {
"clone": [
,
],
"self": [
]
}
}],
"start": 0
}
If I do the same with an old sourcetree (v 1.10.23) all works fine, because of sourcetree use "start=0" and the list of available repositories are displayed.
Why the newer versions of sourcetree is using startindex 1 instead of startindex 0.
To complete the confusion. We have a second Bitbucket with the same version and with this Bitbucket it works using startindex 1. The only one difference is the OS (Ubuntu 14.04 instead of 18.04).
What's going wrong. I do not have any idea more.
Best Regards
Franz