\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]",[3019],{"name":3020,"color":3021},"bug","d73a4a",5338,"woodpecker-ci","woodpecker","open","Build status not completing on matrix pipelines with BitBucket","2025-07-17T18:03:12Z","https://github.com/woodpecker-ci/woodpecker/issues/5338",0.68344235,{"description":3031,"labels":3032,"number":3039,"owner":3023,"repository":3024,"state":3025,"title":3040,"updated_at":3041,"url":3042,"score":3043},"### Component\r\n\r\nweb-ui\r\n\r\n### Describe the bug\r\n\r\nWe have a good state build, but the WEB UI shows a bad build result badge:\r\n\r\n\r\nWe have newer seen this problem before!\r\n\r\n### Steps to reproduce\r\n\r\n...don't know...\r\n\r\n### Expected behavior\r\n\r\n_No response_\r\n\r\n### System Info\r\n\r\n```shell\r\n{\r\n\"source\": \"https://github.com/woodpecker-ci/woodpecker\",\r\n\"version\": \"2.7.3\"\r\n}\r\n```\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\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]",[3033,3036],{"name":3034,"color":3035},"server","5D7A92",{"name":3037,"color":3038},"enhancement","7E1FE4",4505,"Allow badges to include more than just push events","2025-03-07T18:14:49Z","https://github.com/woodpecker-ci/woodpecker/issues/4505",0.70928824,{"description":3045,"labels":3046,"number":3048,"owner":3023,"repository":3024,"state":3049,"title":3050,"updated_at":3051,"url":3052,"score":3053},"### 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]",[3047],{"name":3020,"color":3021},3561,"closed","Pipeline status is error, but last job is OK","2024-04-15T10:15:05Z","https://github.com/woodpecker-ci/woodpecker/issues/3561",0.66565764,{"description":3055,"labels":3056,"number":3058,"owner":3023,"repository":3024,"state":3049,"title":3059,"updated_at":3060,"url":3061,"score":3062},"### 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).",[3057],{"name":3020,"color":3021},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.6803532,{"description":3064,"labels":3065,"number":3070,"owner":3023,"repository":3024,"state":3049,"title":3071,"updated_at":3072,"url":3073,"score":3074},"### Component\n\nserver\n\n### Describe the bug\n\nWhen pipeline/step is canceled automatically it will result in failed state with error:\r\n```\r\nGet \"http://%2Fvar%2Frun%2Fdocker.sock/v1.41/containers/wp_0_8440940097353797125_clone_1/json\": context canceled\r\n```\r\n\r\nInstead on this error step should be set to state canceled and so is pipeline\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-ee9269d6\"}\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/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] 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).",[3066,3067],{"name":3020,"color":3021},{"name":3068,"color":3069},"duplicate","9D1C99",1391,"Canceled pipelines/steps should have correct status","2022-11-06T02:54:38Z","https://github.com/woodpecker-ci/woodpecker/issues/1391",0.6875854,{"description":3076,"labels":3077,"number":3082,"owner":3023,"repository":3024,"state":3049,"title":3083,"updated_at":3084,"url":3085,"score":3086},"### Component\n\nweb-ui\n\n### Describe the bug\n\nWhen rootPath is not empty the badge image src link is wrong in the page of repo badge settings.\n\n### System Info\n\n```shell\n{\r\n \"source\": \"https://github.com/woodpecker-ci/woodpecker\",\r\n \"version\": \"2.1.0\"\r\n}\n```\n\n\n### Additional context\n\n\r\n\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).",[3078,3079],{"name":3020,"color":3021},{"name":3080,"color":3081},"ui","46DEA2",3032,"Wrong badgeUrl when rootPath is not empty in the page of repo badge settings","2023-12-28T05:15:14Z","https://github.com/woodpecker-ci/woodpecker/issues/3032",0.6998738,{"description":3088,"labels":3089,"number":3092,"owner":3023,"repository":3024,"state":3049,"title":3093,"updated_at":3094,"url":3095,"score":3096},"### Component\n\nserver\n\n### Describe the bug\n\nSometimes pipeline cancellations still result in errors that will flag the pipeline as failed instead of cancelled:\r\n\r\n\r\n\n\n### Steps to reproduce\n\nHave not found a reliable way to reproduce this specific case.\n\n### Expected behavior\n\nPipeline should be marked as cancelled instead of failed.\n\n### System Info\n\n```shell\nnext-bf5405b6cc\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]",[3090,3091],{"name":3020,"color":3021},{"name":3080,"color":3081},4349,"Cancelled pipelines marked as failed","2024-11-12T06:48:56Z","https://github.com/woodpecker-ci/woodpecker/issues/4349",0.700828,{"description":3098,"labels":3099,"number":3102,"owner":3023,"repository":3024,"state":3049,"title":3103,"updated_at":3104,"url":3105,"score":3106},"### Component\r\n\r\nweb-ui\r\n\r\n### Describe the bug\r\n\r\nI noticed some issues with the new terminal:\r\n- log lines for other running jobs shown in selected running jobs? 🤔 or the terminal is not properly reset after switching\r\n- space reserved for `exit code x` for running jobs (Screenshot 1)\r\n- `exit code x` pushed to bottom (only half of it visible) (Screenshot 2)\r\n- sometimes it still seems to flicker\r\n\r\n\r\n\r\n\r\n\r\n\r\n### System Info\r\n\r\n```shell\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-3f73d5bf\"}\r\n```\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Validations\r\n\r\n- [X] Read the [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/master/CONTRIBUTING.md).\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] 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).",[3100,3101],{"name":3020,"color":3021},{"name":3080,"color":3081},1012,"Terminal issues","2022-08-08T13:29:53Z","https://github.com/woodpecker-ci/woodpecker/issues/1012",0.7017237,{"description":3108,"labels":3109,"number":3111,"owner":3023,"repository":3024,"state":3049,"title":3112,"updated_at":3113,"url":3114,"score":3115},"### Clear and concise description of the problem\n\nCurrently, the status sent back to the forge looks like this:\r\n\r\n|state|status|message|\r\n|---|---|---|\r\n|pipeline waits for approval|pending|`Pipeline is pending`|\r\n|pipeline is declined|pending|`Pipeline is pending`|\n\n### Suggested solution\n\nIt should look like:\r\n\r\n|state|status|message|\r\n|---|---|---|\r\n|pipeline waits for approval|pending|`Pipeline waits for approval`|\r\n|pipeline is declined|failed|`Pipeline was declined`|\n\n### Alternative\n\n_No response_\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/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 request the same feature to avoid creating a duplicate.",[3110],{"name":3037,"color":3038},895,"Improve status messages for protected pipelines","2024-02-22T14:48:31Z","https://github.com/woodpecker-ci/woodpecker/issues/895",0.7020842,{"description":3117,"labels":3118,"number":3120,"owner":3023,"repository":3024,"state":3049,"title":3121,"updated_at":3122,"url":3123,"score":3124},"### 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]",[3119],{"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.72069037,["Reactive",3126],{},["Set"],["ShallowReactive",3129],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fDbLlvXBSYv_AlwWBCvZErOiqI7by5YxZ3FbJz7MD-44":-1},"/woodpecker-ci/woodpecker/958"]