\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]",[3044],{"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.69551253,{"description":3051,"labels":3052,"number":3053,"owner":3022,"repository":3023,"state":3054,"title":3055,"updated_at":3056,"url":3057,"score":3058},"### Component\n\nserver\n\n### Describe the bug\n\nWhen a started pipeline is canceled, the pipeline status is always `Failed`\r\n\r\nIt seems that the pipeline status is always based on the the step state\r\n\r\nWhen a step is canceled, the step state reported back by the killed is always failed.\r\n\r\nThis is caused by \r\n\r\nhttps://github.com/woodpecker-ci/woodpecker/blob/1786c0554a3f347924a0a1d36c8b2684eb45ac86/agent/runner.go#L365\r\n\r\nthat is called even if cancel is set\r\n\r\nI think `Done` should just be called if cancel is not set\r\n\r\n```go\r\nif canceled.IsNotSet() {\r\n err = r.client.Done(ctxmeta, work.ID, state)\r\n}\r\n```\r\n\r\nAlso the step state has to be overwritten\r\n\r\n```go\r\nstepState := rpc.State{\r\n Step: state.Pipeline.Step.Alias,\r\n Exited: state.Process.Exited,\r\n ExitCode: state.Process.ExitCode,\r\n Started: time.Now().Unix(), // TODO do not do this\r\n Finished: time.Now().Unix(),\r\n}\r\nif canceled.IsSet() {\r\n stepState.ExitCode = 137\r\n stepState.Error = \"Step canceled\"\r\n} else if state.Process.Error != nil {\r\n stepState.Error = state.Process.Error.Error()\r\n}\r\n\r\n```\r\n\r\nsince the error reported seems to be always caused by the step getting killed\r\n\r\n\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-05d2f493\"}\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).",[],1430,"closed","Wrong pipeline status on cancel","2022-11-22T08:49:51Z","https://github.com/woodpecker-ci/woodpecker/issues/1430",0.5713847,{"description":3060,"labels":3061,"number":3064,"owner":3022,"repository":3023,"state":3054,"title":3065,"updated_at":3066,"url":3067,"score":3068},"### 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]",[3062,3063],{"name":3019,"color":3020},{"name":3034,"color":3035},4349,"Cancelled pipelines marked as failed","2024-11-12T06:48:56Z","https://github.com/woodpecker-ci/woodpecker/issues/4349",0.6176751,{"description":3070,"labels":3071,"number":3076,"owner":3022,"repository":3023,"state":3054,"title":3077,"updated_at":3078,"url":3079,"score":3080},"### Component\r\n\r\nserver\r\n\r\n### Describe the bug\r\n\r\nconditional step event failure always triggered even when there is no error\r\n\r\n```yml\r\n when:\r\n status:\r\n - failure\r\n```\r\nis triggered even when no jobs fails\r\n\r\n### System Info\r\n\r\n```shell\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-6433dfea\"}\r\n```\r\n\r\n\r\n### Additional context\r\n\r\n\r\n\r\n\r\n\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).",[3072,3073],{"name":3019,"color":3020},{"name":3074,"color":3075},"server","5D7A92",1181,"conditional step event failure aways triggered ","2023-01-02T05:36:59Z","https://github.com/woodpecker-ci/woodpecker/issues/1181",0.66009086,{"description":3082,"labels":3083,"number":3085,"owner":3022,"repository":3023,"state":3054,"title":3086,"updated_at":3087,"url":3088,"score":3089},"### 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]",[3084],{"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.67066705,{"description":3091,"labels":3092,"number":3097,"owner":3022,"repository":3023,"state":3054,"title":3098,"updated_at":3099,"url":3100,"score":3101},"### Component\r\n\r\nserver\r\n\r\n### Describe the bug\r\n\r\nIf a workflow contains multiple steps or services with the same name (one service and one step with the same name is affected as well) it will result in a race condition during the container creation.\r\n\r\n\r\n\r\n\r\n\r\n\r\n \r\n\r\n### System Info\r\n\r\n```shell\r\nnext-5d98a717ac\r\n```\r\n\r\n\r\n### Additional context\r\n\r\ncaused by https://github.com/woodpecker-ci/woodpecker/pull/2757/files#diff-6f809c0a6ea3b1924d8664a9f0dba9e308c15a5915d6444a18f0cb913809e26aR90\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]",[3093,3094],{"name":3019,"color":3020},{"name":3095,"color":3096},"regression","7E192B",3494,"Duplicate step/service names results in conflicting container names","2024-03-18T19:07:47Z","https://github.com/woodpecker-ci/woodpecker/issues/3494",0.6834903,{"description":3103,"labels":3104,"number":3107,"owner":3022,"repository":3023,"state":3054,"title":3108,"updated_at":3109,"url":3110,"score":3111},"### Component\n\nserver\n\n### Describe the bug\n\nWhen I tried to trigger a pipeline via api with an incorrect ID, I got an error 500 instead of 404, because it doesn't check if there is a repo with the given ID\r\n\r\nThe following route:\r\nhttps://my-woodpecker/api/repos/{repo_id}/pipelines\r\n\r\n*Sorry in advance if this is a duplication of issues, in searching I found no issues with my keywords*\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.4.1\"}\n```\n\n\n### Additional context\n\n\r\n\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]",[3105,3106],{"name":3019,"color":3020},{"name":3074,"color":3075},3686,"Nil pointer with invalid id on trigger pipeline api","2024-05-11T08:38:36Z","https://github.com/woodpecker-ci/woodpecker/issues/3686",0.6883674,{"description":3113,"labels":3114,"number":3118,"owner":3022,"repository":3023,"state":3054,"title":3119,"updated_at":3120,"url":3121,"score":3122},"### Component\n\nserver, web-ui\n\n### Describe the bug\n\nIn a repo where builds are only desired for a specific branch (excluding the default branch), the following happens:\r\n\r\n- On a push to a custom branch which has a valid pipeline definition, everything works\r\n- On a push to any other of the repo the webhook is also triggered but the build will immediately fail due to a missing pipeline config\r\n\r\n\r\n\r\nThe use case I have here is that I maintain a fork. I build some stuff in a custom branch but always keep `main/master` in sync with upstream.\r\nHence, only the custom branch has a pipeline definition and whenever the `main` branch is synced with upstream, the above error occurs.\r\n\r\nI think it would be good if WP first checks for any existence of a valid WP YAML file and if none is found, just does nothing - instead of throwing an error?\n\n### System Info\n\n```shell\nnext-8629a418f8\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).",[3115],{"name":3116,"color":3117},"duplicate","9D1C99",2579,"Don't fail if branch has no pipeline definition","2023-10-14T09:08:14Z","https://github.com/woodpecker-ci/woodpecker/issues/2579",0.6889827,["Reactive",3124],{},["Set"],["ShallowReactive",3127],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fY_giT2TZtXQFzGwYCMAuNCT0vFTDI5c_Ph4Dth_ymV8":-1},"/woodpecker-ci/woodpecker/1391"]