Closed majodev closed 1 year ago
Do you only refer to hosted BitBucket or also to the self-hosted BitBucket Server (Stash)?
Do you only refer to hosted BitBucket
AFAIK the "cloud" variant of Bitbucket has this branches API endpoint which you currently use (I've not tested those).
or also to the self-hosted BitBucket Server (Stash)?
yes, my issue only refers to self-hosted Bitbucket (formerly Stash, available as Server
or Data Center
license) and the branches endpoint here.
@majodev Created #1698, however, I can't test it as I don't have access to a Bitbucket server. It would be very nice if you could try :)
Component
server
Describe the bug
Hi,
I'm currently in the process of migrating a fairly old Bitbucket Server 7.x (non-cloud) instance to Bitbucket Data Center 8.8. As part of this, I'm also investigating migration of a super old woodpecker instance (
v0.8.105
) tov0.15.7
and now tonext
.Apart from the typical to be expected DB migrations and breaking
ENV
configuration changes, the branch list integration introduced with #907 (more exactly the<base>/2.0/repositories/<owner>/<name>/refs/branches
template string here) is actually something still blocking us currently. It404
s on Bitbucket Server / Data Center and consequently500
within Woodpecker.AFAIK for both Bitbucket Server / Data Center 7.x and 8.x (non-cloud) the proper integration endpoint should be
GET <base>/rest/api/latest/projects/<owner>/repos/<name>/branches
. Sample Bitbucket Response of this endpoint is:Sources:
System Info
Additional context
Woodpecker Server Log:
Browser Console / UI:
Validations
next
version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]