\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]",[3184,3185],{"name":3140,"color":3141},{"name":3186,"color":3187},"forge/bitbucket","E96280",5338,"Build status not completing on matrix pipelines with BitBucket","2025-08-10T17:51:17Z","https://github.com/woodpecker-ci/woodpecker/issues/5338",0.65753984,{"description":3194,"labels":3195,"number":3198,"owner":3143,"repository":3144,"state":3176,"title":3199,"updated_at":3200,"url":3201,"score":3202},"### 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]",[3196,3197],{"name":3140,"color":3141},{"name":3186,"color":3187},5159,"Bitbucket Datacenter commit url is broken","2025-05-20T10:13:15Z","https://github.com/woodpecker-ci/woodpecker/issues/5159",0.6683747,{"description":3204,"labels":3205,"number":3207,"owner":3143,"repository":3144,"state":3176,"title":3208,"updated_at":3209,"url":3210,"score":3211},"### Component\n\nserver\n\n### Describe the bug\n\n\r\n\r\nI'll try to downgrade my woodpecker version to fix this, because all PRs are now broken on `next`.\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-5bd12aa646\"}\n```\n\n\n### Additional context\n\nNA\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).",[3206],{"name":3140,"color":3141},2350,"All github PRs are reported as *Waiting for status to be reported*","2023-10-02T06:45:33Z","https://github.com/woodpecker-ci/woodpecker/issues/2350",0.69343257,{"description":3213,"labels":3214,"number":3217,"owner":3143,"repository":3144,"state":3176,"title":3218,"updated_at":3219,"url":3220,"score":3221},"### 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).",[3215,3216],{"name":3140,"color":3141},{"name":3186,"color":3187},1695,"Bitbucket Server / Data Center: List branches endpoint 404","2023-04-07T16:09:19Z","https://github.com/woodpecker-ci/woodpecker/issues/1695",0.6994599,{"description":3223,"labels":3224,"number":3226,"owner":3143,"repository":3144,"state":3176,"title":3227,"updated_at":3228,"url":3229,"score":3230},"### 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]",[3225],{"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.70601755,{"description":3232,"labels":3233,"number":3236,"owner":3143,"repository":3144,"state":3176,"title":3237,"updated_at":3238,"url":3239,"score":3240},"### Component\n\nweb-ui\n\n### Describe the bug\n\nI am attempting to use Woodpecker to build an image using the [Cypress Factory](https://hub.docker.com/r/cypress/factory/) docker image that can be used with docker args to generate a container with specific package versions. I am using the woodpecker docker buildx plugin to build the image.\r\n\r\nWhen I run my build job and view the progress in the UI it appears the job is stuck installing GPG keys. However, when I look at the log output on the agent I can see that the GPG key installations are successful and the rest of the job steps are executed and the final image is published.\r\n\r\nAdditionally, the UI never marks the job as completed and the kubernetes builds pods stayed in a 'Completed' state until the job times out or is manually cancelled. When this happens the agents no longer pull new work from the server.\n\n### Steps to reproduce\n\n1. Create a Dockerfile using the Cypress factory image\r\n```\r\nARG NODE_VERSION='18.16.0'\r\nARG YARN_VERSION='1.22.19'\r\nARG CYPRESS_VERSION='13.7.1'\r\nARG CHROME_VERSION='120.0.6099.71-1'\r\nARG EDGE_VERSION='120.0.2210.61-1'\r\nARG FIREFOX_VERSION='120.0.1'\r\n\r\nFROM cypress/factory\r\n```\r\n2. Create a woodpecker job to build the image\r\n```\r\nsteps:\r\n - name: docker-cypress\r\n image: woodpeckerci/plugin-docker-buildx\r\n secrets: [docker_username, docker_password]\r\n settings:\r\n platforms: linux/amd64\r\n registry: \u003Cmy_docker_registry>\r\n repo: \u003Cmy_docker_repo>\r\n dockerfile: Dockerfile.cypress.test\r\n tags: buildx.test-build\r\n username:\r\n from_secret: docker_username\r\n password:\r\n from_secret: docker_password\r\n build_args_from_env:\r\n - CI_REPO\r\n - CI_COMMIT_BRANCH\r\n - CI_COMMIT_SHA\r\n - CI_PIPELINE_NUMBER\r\n debug: true\r\n```\r\n3. Run the job\r\n\n\n### Expected behavior\n\n* The job should successfully build the container and be marked Successful\r\n* The UI log output should stay in sync with the worker agent log output\r\n* The UI should not hang indefinitely during the build\n\n### System Info\n\n```shell\n{\r\n\"source\": \"https://github.com/woodpecker-ci/woodpecker\",\r\n\"version\": \"2.4.1\"\r\n}\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]",[3234,3235],{"name":3140,"color":3141},{"name":3164,"color":3165},3716,"Woodpecker UI output not updating/out of sync","2024-06-13T15:18:35Z","https://github.com/woodpecker-ci/woodpecker/issues/3716",0.70887446,["Reactive",3242],{},["Set"],["ShallowReactive",3245],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fA-VAqjAvUkHleeyQ_vI0zY7Bp9p2Fwvqq9e3sN61RXY":-1},"/woodpecker-ci/woodpecker/5158"]