\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]",[3033],{"name":3020,"color":3021},5338,"Build status not completing on matrix pipelines with BitBucket","2025-07-17T18:03:12Z","https://github.com/woodpecker-ci/woodpecker/issues/5338",0.7171736,{"description":3040,"labels":3041,"number":3043,"owner":3023,"repository":3024,"state":3025,"title":3044,"updated_at":3045,"url":3046,"score":3047},"### Component\n\nweb-ui\n\n### Describe the bug\n\nWhenever I navigate to the settings of a repo (same behavior for all repos) woodpecker reports \"an unknown error occured\". However, as far as I can tell, repo settings are interpreted correctly and I can also still update settings. Pipelines also execute normally. Even the server logs do not show any errors.\r\n\r\nSince I did not experience major issues yet and do not see any errors reported in the server logs (server is running with debug mode on currently), I am not sure how to debug further and thus wanted to report the issue. Probably a low priority issue with (hopefully) no major implications?\r\n\r\n\r\n\u003Cimg width=\"1284\" alt=\"image\" src=\"https://github.com/user-attachments/assets/403e1c1a-f6e7-4800-8a71-e8017cd4e18f\">\r\n\n\n### Steps to reproduce\n\n1. Click on any repository in Woodpecker's WebUI\r\n2. Click on settings icon\r\n3. Error shows up\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\nWoodpecker v2.7.1\r\nBitbucket Datacenter v9.1.1\r\n\r\nWoodpecker is running via docker compose:\r\n\r\n ...\r\n woodpecker-server:\r\n image: woodpeckerci/woodpecker-server:v2.7.1\r\n depends_on:\r\n - traefik\r\n container_name: woodpecker-server\r\n restart: always\r\n environment:\r\n - WOODPECKER_OPEN=true\r\n - WOODPECKER_SERVER_ADDR=:8000\r\n - WOODPECKER_HOST=\u003Cour-woodpecker-url>\r\n # OAuth setup for Bitbucket Datacenter\r\n - WOODPECKER_BITBUCKET_DC=true\r\n - WOODPECKER_BITBUCKET_DC_GIT_USERNAME=\u003Cdedicated-woodpecker-account>\r\n - WOODPECKER_BITBUCKET_DC_GIT_PASSWORD=\u003Cpassword>\r\n - WOODPECKER_BITBUCKET_DC_CLIENT_ID=\u003Cclient-id>\r\n - WOODPECKER_BITBUCKET_DC_CLIENT_SECRET=\u003Cclient-secret>\r\n - WOODPECKER_BITBUCKET_DC_URL=\u003Cbitbucket-dc-url>\r\n - WOODPECKER_BITBUCKET_DC_SKIP_VERIFY=true\r\n # Agent\r\n - WOODPECKER_AGENT_SECRET=\u003Cagent-secret>\r\n # Optional: Additional configurations\r\n - WOODPECKER_LOG_LEVEL=debug\r\n volumes:\r\n - woodpecker_server_data:/var/lib/woodpecker # Persist data across restarts\r\n networks:\r\n - harbor\r\n labels:\r\n - \"traefik.enable=true\"\r\n - \"traefik.http.routers.woodpecker.rule=Host(`\u003Cwoodpecker-url>`)\"\r\n - \"traefik.http.routers.woodpecker.entrypoints=websecure\"\r\n - \"traefik.http.routers.woodpecker.tls.certresolver=le\"\r\n - \"traefik.http.services.woodpecker.loadbalancer.server.port=8000\"\r\n - \"traefik.docker.network=harbor\"\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]",[3042],{"name":3020,"color":3021},4240,"Woodpecker 2.7.1 reporting \"an unknown error occured\" in repo settings","2024-10-21T10:52:58Z","https://github.com/woodpecker-ci/woodpecker/issues/4240",0.717953,{"description":3049,"labels":3050,"number":3052,"owner":3023,"repository":3024,"state":3025,"title":3053,"updated_at":3054,"url":3055,"score":3056},"### Component\n\nserver\n\n### Describe the bug\n\nSee https://codeberg.org/Codeberg-CI/feedback/issues/120\r\n\r\nC/p issue description:\r\n\r\n1. Create repo in Gitea\r\n2. Enable it in WP\r\n3. Delete repo in Gitea\r\n4. Create repo with the same name in Gitea\r\n5. Try to enable it again\r\n\r\n-> error\r\n\r\nWhen enabling a repo, there should be a check for an existing one in the DB and if one exists, it should be deleted. \n\n### System Info\n\n```shell\n`next-dfc2c265b1` (Dec 20th)\n```\n\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Read the [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/main/CONTRIBUTING.md).\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]\n- [X] Check that this is a concrete bug. For Q&A join our [Discord Chat Server](https://discord.gg/fcMQqSMXJy) or the [Matrix room](https://matrix.to/#/#woodpecker:matrix.org).",[3051],{"name":3020,"color":3021},3020,"Re-enabling a WP repo after previous deletion/recreation in forge leads to DB deadlock","2025-01-23T11:41:11Z","https://github.com/woodpecker-ci/woodpecker/issues/3020",0.7284541,{"description":3058,"labels":3059,"number":3064,"owner":3023,"repository":3024,"state":3065,"title":3066,"updated_at":3067,"url":3068,"score":3069},"### Component\n\nserver\n\n### Describe the bug\n\nHi,\r\n\r\nI'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`) to `v0.15.7` and now to `next`.\r\n\r\nApart from the typical to be expected DB migrations and breaking `ENV` configuration changes, the branch list integration introduced with #907 (more exactly the `\u003Cbase>/2.0/repositories/\u003Cowner>/\u003Cname>/refs/branches` template string [here](https://github.com/woodpecker-ci/woodpecker/pull/907/files#diff-ecc104bf0e9c2d9167c43bce82421e93507f8a8660f061ac2171d298dfe214ea)) is actually something still blocking us currently. It `404`s on Bitbucket Server / Data Center and consequently `500` within Woodpecker.\r\n\r\nAFAIK for both Bitbucket Server / Data Center 7.x and 8.x (non-cloud) the proper integration endpoint should be `GET \u003Cbase>/rest/api/latest/projects/\u003Cowner>/repos/\u003Cname>/branches`. Sample Bitbucket Response of this endpoint is:\r\n\r\n```json\r\n{\r\n \"size\": 4,\r\n \"limit\": 25,\r\n \"isLastPage\": true,\r\n \"values\": [\r\n {\r\n \"id\": \"refs/heads/dev\",\r\n \"displayId\": \"dev\",\r\n \"type\": \"BRANCH\",\r\n \"latestCommit\": \"\u003CSHA>\",\r\n \"latestChangeset\": \"\u003CSHA>\",\r\n \"isDefault\": false\r\n },\r\n {\r\n \"id\": \"refs/heads/main\",\r\n \"displayId\": \"main\",\r\n \"type\": \"BRANCH\",\r\n \"latestCommit\": \"\u003CSHA>\",\r\n \"latestChangeset\": \"\u003CSHA>\",\r\n \"isDefault\": true\r\n }\r\n ],\r\n \"start\": 0\r\n}\r\n```\r\n\r\nSources:\r\n* https://developer.atlassian.com/server/bitbucket/rest/v808/api-group-repository/#api-api-latest-projects-projectkey-repos-repositoryslug-branches-get\n\n### System Info\n\n```shell\nwoodpeckerci/woodpecker-server:next-e408c1ba27-alpine\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-e408c1ba\"}\n```\n\n\n### Additional context\n\nWoodpecker Server Log:\r\n```json\r\n{\r\n \"level\": \"error\",\r\n \"error\": \"Error #01: invalid character '\u003C' looking for beginning of value\\n\",\r\n \"ip\": \"xxx.xxx.xxx.xxx\",\r\n \"latency\": 54.356947,\r\n \"method\": \"GET\",\r\n \"path\": \"/api/repos/PROJECT/REPO/branches\",\r\n \"status\": 500,\r\n \"user-agent\": \"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/111.0.0.0 Safari/537.36\",\r\n \"time\": \"2023-04-03T15:57:01Z\",\r\n \"caller\": \"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/router/middleware/logger.go:43\"\r\n}\r\n```\r\n\r\nBrowser Console / UI:\r\n\u003Cimg width=\"997\" alt=\"Bildschirmfoto 2023-04-03 um 17 57 28\" src=\"https://user-images.githubusercontent.com/2149883/229565185-5c2b1a17-735d-43c7-ab2f-31214801da71.png\">\r\n\u003Cimg width=\"120\" alt=\"Bildschirmfoto 2023-04-03 um 18 00 10\" src=\"https://user-images.githubusercontent.com/2149883/229565201-340e64e4-85fb-45be-80a3-af8072dc243e.png\">\r\n\n\n### Validations\n\n- [X] Read the [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/master/CONTRIBUTING.md).\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]\n- [X] Check that this is a concrete bug. For Q&A join our [Discord Chat Server](https://discord.gg/fcMQqSMXJy) or the [Matrix room](https://matrix.to/#/#woodpecker:matrix.org).",[3060,3061],{"name":3020,"color":3021},{"name":3062,"color":3063},"forge/bitbucket","E96280",1695,"closed","Bitbucket Server / Data Center: List branches endpoint 404","2023-04-07T16:09:19Z","https://github.com/woodpecker-ci/woodpecker/issues/1695",0.65876436,{"description":3071,"labels":3072,"number":3075,"owner":3023,"repository":3024,"state":3065,"title":3076,"updated_at":3077,"url":3078,"score":3079},"### 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]",[3073,3074],{"name":3020,"color":3021},{"name":3062,"color":3063},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.6659865,{"description":3081,"labels":3082,"number":3084,"owner":3023,"repository":3024,"state":3065,"title":3085,"updated_at":3086,"url":3087,"score":3088},"### Component\n\nserver\n\n### Describe the bug\n\nWhen a pipeline with multiple workflows starts a correct status is sent at first BitBucket correctly displays that build is in progress. When the build finishes however, only one build is displayed as finished but the other one is still in progress marking the whole commit as in progress(this is internal BitBucket logic). \n\nHere is a pipeline that has two workflows:\n\n\n\nAnd here is the outcome on BitBucket:\n\n\n\nI asked @langecode if he can take a look and we realized that there is a problem in BitBucket forge implementation of `Status` function. It looks like that for each call of `Status` function we send a status of the whole pipeline when we should've sent a status of individual workflows. I.e. change status of https://github.com/woodpecker-ci/woodpecker/blob/main/server/forge/bitbucketdatacenter/bitbucketdatacenter.go#L314\n\nTo:\n```go\nState: convertStatus(workflow.State)\n```\n\n### Steps to reproduce\n\n1. Run woodpecker with BitBucket Datacenter forge\n2. Create a pipeline that has multiple workflows\n3. Let the pipeline finish on woodpecker\n4. Observe the build statuses on the commit in BitBucket\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\nWoodpecker version: v3.5.2\nBitBucket Datacenter version: v8.18.1\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]",[3083],{"name":3020,"color":3021},5177,"Statuses get incorrectly reported for multi workflow pipelines on BitBucket","2025-05-19T11:01:04Z","https://github.com/woodpecker-ci/woodpecker/issues/5177",0.6984233,{"description":3090,"labels":3091,"number":3096,"owner":3023,"repository":3024,"state":3065,"title":3097,"updated_at":3098,"url":3099,"score":3100},"### Component\n\nweb-ui\n\n### Describe the bug\n\nFrom https://codeberg.org/Codeberg-CI/feedback/issues/91\r\n\r\nA commit hash link in CRON runs only links to `user/repo` instead of `user/repo/commit/xxx`\r\n\r\n\r\n\n\n### System Info\n\n```shell\nnext-7b3eeec65c # Oct 17\n```\n\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Read the [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/main/CONTRIBUTING.md).\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]\n- [X] Check that this is a concrete bug. For Q&A join our [Discord Chat Server](https://discord.gg/fcMQqSMXJy) or the [Matrix room](https://matrix.to/#/#woodpecker:matrix.org).",[3092,3093],{"name":3020,"color":3021},{"name":3094,"color":3095},"ui","46DEA2",2657,"Properly link commit hash in run UI","2024-02-11T09:44:51Z","https://github.com/woodpecker-ci/woodpecker/issues/2657",0.7007416,{"description":3102,"labels":3103,"number":3104,"owner":3023,"repository":3024,"state":3065,"title":3105,"updated_at":3106,"url":3107,"score":3108},"I was using the installation instructions from the docs, and the docs link in the UI (top left, under Woodpecker) points to: https://github.com/laszlocph/woodpecker/blob/master/docs/usage/pipeline.md\r\n\r\nAny idea why that happens?\r\n\r\nI've checked the code and it correctly points to: https://woodpecker.laszlo.cloud/ so maybe the docker image is wrong?\r\n\r\n```laszlocloud/woodpecker-server:v0.9.0```",[],155,"Docs link in latest docker image points to broken github page","2021-02-16T16:53:35Z","https://github.com/woodpecker-ci/woodpecker/issues/155",0.70497805,{"description":3110,"labels":3111,"number":3114,"owner":3023,"repository":3024,"state":3065,"title":3115,"updated_at":3116,"url":3117,"score":3118},"### 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]",[3112,3113],{"name":3020,"color":3021},{"name":3062,"color":3063},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.7151152,["Reactive",3120],{},["Set"],["ShallowReactive",3123],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fAF4WIy_Cg1GoBPi3MRbCEg1HLVvN59MNjRypDI91YWg":-1},"/woodpecker-ci/woodpecker/5159"]