\n\nAnd here is the outcome on BitBucket:\n\u003Cimg width=\"479\" height=\"182\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/11c2a65d-cbf2-4162-9805-3d035bdac04e\" />\n\n\n### Steps to reproduce\n\n1. Run Woodpecker with BitBucket Cloud forge\n2. Create a pipeline that uses a matrix\n3. Let the pipeline finish on Woodpecker\n4. Observe the build statuses on the commit in BitBucket\n\n### Expected behavior\n\nBoth pipelines should show completed.\n\n### System Info\n\n```shell\nWoodpecker version: v3.8.0\n```\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [x] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [x] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\n- [x] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/versions]",[3185,3186],{"name":3140,"color":3141},{"name":3187,"color":3188},"forge/bitbucket","E96280",5338,"closed","Build status not completing on matrix pipelines with BitBucket","2025-08-10T17:51:17Z","https://github.com/woodpecker-ci/woodpecker/issues/5338",0.6169588,{"description":3196,"labels":3197,"number":3200,"owner":3143,"repository":3144,"state":3190,"title":3201,"updated_at":3202,"url":3203,"score":3204},"### Component\n\nserver\n\n### Describe the bug\n\nWhen build finishes(either successfully or with failure) the status doesn't get updated, even though the commit status of the last commit on the PR is updated just fine.\n\nI was able to trace back this bug to this PR: https://github.com/woodpecker-ci/woodpecker/pull/4724\n\nNow I see the need for the `Ref` to be set when updating the build status but it turns out that `pipeline.Ref` doesn't have a correct value. In my case it would set only the ref as follows: `refs/pull-requests/\u003CpullRequestID>/from`. I was able to find that `Ref` gets set [here](https://github.com/woodpecker-ci/woodpecker/blob/main/server/forge/bitbucketdatacenter/convert.go#L122) and I believe this is wrong, it's not a \"valid\" git ref and if ref is set to an invalid value BitBucket will not set the build status for that PR(https://community.atlassian.com/forums/Bitbucket-questions/Re-Builds-not-appearing-in-pull-requests/qaq-p/1805991/comment-id/65864#M65864).\n\nI suggest that we change the code from above to:\n```go\nRef: fmt.Sprintf(\"refs/heads/%s\", ev.PullRequest.Source.DisplayID),\n```\nI believe this would fix the issue, and I would like to work on it if possible.\n\nAdding: @Levy-Tal as he worked on PR mentioned above and @langecode because he is the main contributor behind the BitBucket Datacenter forge integration.\n\n\n### Steps to reproduce\n\n1. Open a PR with woodpecker pipelines on BitBucket Datacenter\n2. Trigger a build on the last commit of that PR\n3. Wait for the build to finish\n4. Observe that there is no status on the PR itself\n\n### Expected behavior\n\nThere should be a build status on the PR.\n\n### System Info\n\n```shell\nWoodpecker version: v3.5.2\nHelm chart version: 3.1.0\n```\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [x] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [x] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\n- [x] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/versions]",[3198,3199],{"name":3140,"color":3141},{"name":3187,"color":3188},5158,"PR build status does not get updated on BitBucket Datacenter","2025-05-13T15:29:01Z","https://github.com/woodpecker-ci/woodpecker/issues/5158",0.6405972,{"description":3206,"labels":3207,"number":3211,"owner":3143,"repository":3144,"state":3190,"title":3212,"updated_at":3213,"url":3214,"score":3215},"Gitlab seems to have an issue which results in single Woodpecker pipelines being shown as multiple pipelines in Gitlab.\r\n\r\n expected:\r\n\r\n\r\ncurrently (two pipelines with a single job):\r\n\r\n\r\nGitlab issue: https://gitlab.com/gitlab-org/gitlab/-/issues/13134",[3208,3209],{"name":3140,"color":3141},{"name":3210,"color":3188},"forge/gitlab",618,"Gitlab status / pipelines are separated","2022-08-12T15:49:41Z","https://github.com/woodpecker-ci/woodpecker/issues/618",0.66497225,{"description":3217,"labels":3218,"number":3221,"owner":3143,"repository":3144,"state":3190,"title":3222,"updated_at":3223,"url":3224,"score":3225},"### Component\r\n\r\nserver, agent, web-ui\r\n\r\n### Describe the bug\r\n\r\nWhen using \".woodpecker/\" directory with a workflow file (myworkflow.yml) inside, the error message: `[generic]pipeline definition not found in company/my-repo` appears (manual run).\r\n\r\nWhen using the same file (myworkflow.yml) in the root directory of the project with name \".woodpecker.yml\", the workflow is found and executed.\r\n\r\nThe documentation states that BitBucket Cloud supports multiple workflows. See [https://woodpecker-ci.org/docs/next/administration/forges/overview](https://woodpecker-ci.org/docs/next/administration/forges/overview)\r\n\r\n### System Info\r\n\r\n```shell\r\nversion\t\"next-d0e63375fa\"\r\n```\r\n\r\n\r\n### Additional context\r\n\r\n```\r\nwoodpecker-server-1 | {\"level\":\"debug\",\"time\":\"2024-04-09T07:06:55Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/router/middleware/session/repo.go:150\",\"message\":\"myuser granted &{UserID:1 RepoID:1 Repo:\u003Cnil> Pull:true Push:true Admin:true Synced:1712646369 Created:1712589724 Updated:1712646369} permission to company/my-repo\"}\r\nwoodpecker-server-1 | {\"level\":\"error\",\"error\":\"Resource not found\",\"repo\":\"company/my-repo\",\"user\":\"myuser\",\"time\":\"2024-04-09T07:06:56Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/services/config/forge.go:152\",\"message\":\"could not get folder from forge\"}\r\nwoodpecker-server-1 | {\"level\":\"error\",\"error\":\"Resource not found\",\"repo\":\"company/my-repo\",\"user\":\"myuser\",\"time\":\"2024-04-09T07:06:57Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/services/config/forge.go:152\",\"message\":\"could not get folder from forge\"}\r\nwoodpecker-server-1 | {\"level\":\"error\",\"error\":\"Resource not found\",\"repo\":\"company/my-repo\",\"user\":\"myuser\",\"time\":\"2024-04-09T07:06:57Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/services/config/forge.go:152\",\"message\":\"could not get folder from forge\"}\r\nwoodpecker-server-1 | {\"level\":\"debug\",\"repo\":\"company/my-repo\",\"error\":\"configFetcher: fallback did not find config: Resource not found\\nNo such file or directory: .woodpecker.yaml\\nNo such file or directory: .woodpecker.yml\",\"time\":\"2024-04-09T07:06:58Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/pipeline/create.go:82\",\"message\":\"error while fetching config '' in 'ci/woodpecker' with user: 'myuser'\"}\r\n```\r\n\r\nWoodpecker-UI: Pipeline Path -> empty (default)\r\n\r\n### Validations\r\n\r\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\r\n- [X] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\r\n- [X] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]",[3219,3220],{"name":3140,"color":3141},{"name":3187,"color":3188},3600,"BitBucket Cloud - Pipeline definition not found (when using multiple workflows, manual run)","2024-05-06T07:08:30Z","https://github.com/woodpecker-ci/woodpecker/issues/3600",0.6707594,{"description":3227,"labels":3228,"number":3230,"owner":3143,"repository":3144,"state":3190,"title":3231,"updated_at":3232,"url":3233,"score":3234},"### Component\n\nweb-ui\n\n### Describe the bug\n\nThe pipeline status image (on Woodpecker - returned by API: /api/badges/25/status.svg ) shows ERROR, even that last build is OK:\r\n\r\n\n\n### System Info\n\n```shell\nversion 2.4.1 running on Docker\n```\n\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [X] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\n- [X] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]",[3229],{"name":3140,"color":3141},3561,"Pipeline status is error, but last job is OK","2024-04-15T10:15:05Z","https://github.com/woodpecker-ci/woodpecker/issues/3561",0.6724564,{"description":3236,"labels":3237,"number":3240,"owner":3143,"repository":3144,"state":3190,"title":3241,"updated_at":3242,"url":3243,"score":3244},"### Component\n\nserver\n\n### Describe the bug\n\n**Issue:** \nWhen running a manual pipeline, the link to the commit is broken in Bitbucket DC.\n\n \n\n\n**Cause:** \nThe `forge_url` is set to:\n\n{bitbucket-url}/projects/{project}/repos/{repo-name}/browse\n\nAnd in this [line](https://github.com/woodpecker-ci/woodpecker/blob/main/server/forge/bitbucketdatacenter/bitbucketdatacenter.go#L380), we append `/commit/\u003Ccommit-id>` to it, resulting in the URL:\n\n{bitbucket-url}/projects/{project}/repos/{repo-name}/browse/commit/{commit-id}\n\nThis is a broken link in Bitbucket. The correct URL should be:\n\n{bitbucket-url}/projects/{project}/repos/{repo-name}/commits/{commit-id}\n\n**Note:** \nThis bug only affects manual pipelines. For push and pull request events, the correct URL is injected in the hook function: \n- [Line 100] (https://github.com/woodpecker-ci/woodpecker/blob/main/server/forge/bitbucketdatacenter/convert.go#L100) \n- [Line 123] (https://github.com/woodpecker-ci/woodpecker/blob/main/server/forge/bitbucketdatacenter/convert.go#L123\n\n### Steps to reproduce\n\n1. install server with bitbucket datacenter configured\n2. run pipeline with manual event -\n3. press on the commit in the pipeline - will result in a broken link.\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\nwoodpecker version 3.5.0\n```\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [x] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [x] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\n- [x] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/versions]",[3238,3239],{"name":3140,"color":3141},{"name":3187,"color":3188},5159,"Bitbucket Datacenter commit url is broken","2025-05-20T10:13:15Z","https://github.com/woodpecker-ci/woodpecker/issues/5159",0.68884736,["Reactive",3246],{},["Set"],["ShallowReactive",3249],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fqPpp2Lj6BzTKkQUfqxvRW93R7bWBV0DDIEuC5sSth6A":-1},"/woodpecker-ci/woodpecker/5177"]