\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]",[3032],{"name":3019,"color":3020},5338,"Build status not completing on matrix pipelines with BitBucket","2025-07-17T18:03:12Z","https://github.com/woodpecker-ci/woodpecker/issues/5338",0.7248177,{"description":3039,"labels":3040,"number":3044,"owner":3022,"repository":3023,"state":3024,"title":3045,"updated_at":3046,"url":3047,"score":3048},"### Clear and concise description of the problem\r\n\r\ncan we add a flagger example ? https://docs.dagger.io/integrations/ci\r\n\r\n### Suggested solution\r\n\r\nadd a yaml example\r\n\r\n### Alternative\r\n\r\n_No response_\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Validations\r\n\r\n- [X] Checked that the feature isn't part of the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]\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 request the same feature to avoid creating a duplicate.",[3041],{"name":3042,"color":3043},"documentation","7D625D",4518,"dagger example","2024-12-08T12:35:21Z","https://github.com/woodpecker-ci/woodpecker/issues/4518",0.72766554,{"description":3050,"labels":3051,"number":3058,"owner":3022,"repository":3023,"state":3024,"title":3059,"updated_at":3060,"url":3061,"score":3062},"### Clear and concise description of the problem\n\nCurrently all pipelines a user has access to in any org are shown in the activity panel when they run.\r\n\r\nThis becomes an issue if there are some CRON jobs with a high frequency (e.g. running every hour) as they will always appear and dominate the activity panel.\n\n### Suggested solution\n\nAllow to opt-out pipelines from the activity view.\r\n\r\nAnother option would be to opt-out CRON pipelines from the activity panel completely.\n\n### Alternative\n\n_No response_\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Checked that the feature isn't part of the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]\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.",[3052,3055],{"name":3053,"color":3054},"ui","46DEA2",{"name":3056,"color":3057},"enhancement","7E1FE4",3315,"Allow to opt-out pipelines from the activity panel","2024-02-02T16:05:18Z","https://github.com/woodpecker-ci/woodpecker/issues/3315",0.738843,{"description":3064,"labels":3065,"number":3068,"owner":3022,"repository":3023,"state":3069,"title":3070,"updated_at":3071,"url":3072,"score":3073},"### 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]",[3066,3067],{"name":3019,"color":3020},{"name":3053,"color":3054},4349,"closed","Cancelled pipelines marked as failed","2024-11-12T06:48:56Z","https://github.com/woodpecker-ci/woodpecker/issues/4349",0.65219474,{"description":3075,"labels":3076,"number":3081,"owner":3022,"repository":3023,"state":3069,"title":3082,"updated_at":3083,"url":3084,"score":3085},"### 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).",[3077,3078],{"name":3019,"color":3020},{"name":3079,"color":3080},"duplicate","9D1C99",1391,"Canceled pipelines/steps should have correct status","2022-11-06T02:54:38Z","https://github.com/woodpecker-ci/woodpecker/issues/1391",0.70893914,{"description":3087,"labels":3088,"number":3092,"owner":3022,"repository":3023,"state":3069,"title":3093,"updated_at":3094,"url":3095,"score":3096},"### Clear and concise description of the problem\n\nYou can't start a pipeline once it's declined.\n\n### Suggested solution\n\nShow the restart button for declined pipelines to allow to start a declined pipeline later.\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.",[3089],{"name":3090,"color":3091},"feature","180DBE",935,"Allow to restart declined pipeline","2022-05-24T16:32:38Z","https://github.com/woodpecker-ci/woodpecker/issues/935",0.71515024,{"description":3098,"labels":3099,"number":3101,"owner":3022,"repository":3023,"state":3069,"title":3102,"updated_at":3103,"url":3104,"score":3105},"### Clear and concise description of the problem\n\nAs a last step of my pipeline (in case of failure) i would like to report the error message of the failed build without having to wrap every single step command. My reporting pipeline step would look something like this:\r\n\r\n```yaml\r\n ...\r\n on-error:\r\n commands:\r\n - ./report_failure.sh \"CI failed\" CI_JOB_ERROR_MESSAGE\r\n when:\r\n status: failure\r\n```\n\n### Suggested solution\n\nThe `CI_JOB_ERROR_MESSAGE` or the like is what i am asking for.\n\n### Alternative\n\n_No response_\n\n### Additional context\n\nThank you!\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.",[3100],{"name":3090,"color":3091},704,"provide reason/error message for a build failure inside the current pipeline","2023-08-20T20:34:50Z","https://github.com/woodpecker-ci/woodpecker/issues/704",0.71818894,{"description":3107,"labels":3108,"number":3110,"owner":3022,"repository":3023,"state":3069,"title":3111,"updated_at":3112,"url":3113,"score":3114},"### Component\n\nweb-ui\n\n### Describe the bug\n\nIn case you try to trigger a manual pipeline that does not start an actual pipeline as all workflows have been filtered and returns 204 we want the UI to show this as a toast and return to the manual pipeline prompt.\n\n### Steps to reproduce\n\n1. create an empty repo\n2. trigger a manual pipeline\n3. receive 204 and see loading spinner forever\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\ncommit: 6161a7413d831dc98c47aff4f7f4a6d175c2ec2f (3.4.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]",[3109],{"name":3019,"color":3020},4978,"Show pipeline was filtered for manual pipelines","2025-03-18T13:43:52Z","https://github.com/woodpecker-ci/woodpecker/issues/4978",0.71985084,{"description":3116,"labels":3117,"number":3119,"owner":3022,"repository":3023,"state":3069,"title":3120,"updated_at":3121,"url":3122,"score":3123},"### 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]",[3118],{"name":3019,"color":3020},3561,"Pipeline status is error, but last job is OK","2024-04-15T10:15:05Z","https://github.com/woodpecker-ci/woodpecker/issues/3561",0.72228503,["Reactive",3125],{},["Set"],["ShallowReactive",3128],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fPaziHx4q_99gH1bXN44WoKLaIu4m6WkbFOI3MelnxjE":-1},"/woodpecker-ci/woodpecker/1946"]