\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]",[3045],{"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.7126827,{"description":3052,"labels":3053,"number":3060,"owner":3023,"repository":3024,"state":3025,"title":3061,"updated_at":3062,"url":3063,"score":3064},"### Clear and concise description of the problem\n\nToday (upon the reporting) the owasp NVD data site was down all day, so all our builds stall... and end up with a pipeline timeout at last.\n\n### Suggested solution\n\nFor a step, it would be useful to be able to configure a timeout option, to avoid the pipeline (and jobs in queue) to be blocked (until the entire pipeline timeout is triggered).\nThe status might need to be updated with a \"stepTimeout\" value, or it should be able to configure if the step timeout should trigger/lead to status success or failure.\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.",[3054,3057],{"name":3055,"color":3056},"enhancement","7E1FE4",{"name":3058,"color":3059},"pipeline-config","1BE540",3557,"Idea: Option for timeout configuration per step","2025-06-02T06:04:23Z","https://github.com/woodpecker-ci/woodpecker/issues/3557",0.7141915,{"description":3066,"labels":3067,"number":3072,"owner":3023,"repository":3024,"state":3073,"title":3074,"updated_at":3075,"url":3076,"score":3077},"### 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).",[3068,3069],{"name":3020,"color":3021},{"name":3070,"color":3071},"duplicate","9D1C99",1391,"closed","Canceled pipelines/steps should have correct status","2022-11-06T02:54:38Z","https://github.com/woodpecker-ci/woodpecker/issues/1391",0.5691597,{"description":3079,"labels":3080,"number":3083,"owner":3023,"repository":3024,"state":3073,"title":3084,"updated_at":3085,"url":3086,"score":3087},"### 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]",[3081,3082],{"name":3020,"color":3021},{"name":3035,"color":3036},4349,"Cancelled pipelines marked as failed","2024-11-12T06:48:56Z","https://github.com/woodpecker-ci/woodpecker/issues/4349",0.63076997,{"description":3089,"labels":3090,"number":3095,"owner":3023,"repository":3024,"state":3073,"title":3096,"updated_at":3097,"url":3098,"score":3099},"### 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).",[3091,3092],{"name":3020,"color":3021},{"name":3093,"color":3094},"server","5D7A92",1181,"conditional step event failure aways triggered ","2023-01-02T05:36:59Z","https://github.com/woodpecker-ci/woodpecker/issues/1181",0.671391,{"description":3101,"labels":3102,"number":3104,"owner":3023,"repository":3024,"state":3073,"title":3105,"updated_at":3106,"url":3107,"score":3108},"### 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]",[3103],{"name":3020,"color":3021},3561,"Pipeline status is error, but last job is OK","2024-04-15T10:15:05Z","https://github.com/woodpecker-ci/woodpecker/issues/3561",0.6733912,{"description":3110,"labels":3111,"number":3116,"owner":3023,"repository":3024,"state":3073,"title":3117,"updated_at":3118,"url":3119,"score":3120},"### Component\r\n\r\nserver\r\n\r\n### Describe the bug\r\n\r\nOn a Kubernetes backend, if any container that is part of a step fails to pull an image and gets stuck in an ImagePullBackOff error, the step will just keep running indefinitely, with no feedback for the user.\r\n\r\nI think the expected behavior here would be something along these lines:\r\n\r\n- Woodpecker to try to pull the image for a while\r\n- If it fails (after a timeout) it displays a error to the user informing that it timed out/failed to pull the specific image\r\n- It fails the step\r\n- It terminates the pod on the cluster\r\n\r\nI'd assume that similar errors can happen if other issues cause a Pod to be in a pending state (for example, there are no nodes available in the cluster). Maybe a similar \"timeout\" strategy could be implemented to deal with all these similar scenarios?\r\n\r\nNote: canceling the pipeline terminates the pipeline and terminates the pod, but _marks the pipeline as successful_, which is another issue.\r\n\r\n### System Info\r\n\r\n```shell\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.3.0\"}\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nHere's a sample I did to showcase the issue (it's running in an internal Woodpecker cluster based on Woodpecker 2.3 so I can't share an open link). \r\n\r\nI have built a pipeline where I have referenced an image that does not exist, `image: broken-image-ref`.\r\n\r\n\r\n\r\nHere's the result. It just stays stuck on the broken step, indefinitely (or at least possibility until the pipeline timeout; didn't get to wait that long) without logging anything.\r\n\r\n\r\n\r\nIf I go look at this pod in my cluster, I can see that it is stuck with the ImagePullBackOff error:\r\n\r\n```\r\n...\r\nEvents:\r\n Type Reason Age From Message\r\n ---- ------ ---- ---- -------\r\n Normal Scheduled 4m55s default-scheduler Successfully assigned woodpecker-pipelines/wp-01hsvnwbdgge7msffe0qn6zz68 to \u003C redacated >\r\n Normal SuccessfulAttachVolume 4m45s attachdetach-controller AttachVolume.Attach succeeded for volume \u003C redacated >\r\n Warning Failed 3m25s (x6 over 4m43s) kubelet Error: ImagePullBackOff\r\n Normal Pulling 3m10s (x4 over 4m44s) kubelet Pulling image \"broken-image-ref\"\r\n Warning Failed 3m10s (x4 over 4m43s) kubelet Failed to pull image \"broken-image-ref\": rpc error: code = Unknown desc = failed to pull and unpack image \"docker.io/library/broken-image-ref:latest\": failed to resolve reference \"docker.io/library/broken-image-ref:latest\": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed\r\n Warning Failed 3m10s (x4 over 4m43s) kubelet Error: ErrImagePull\r\n Normal BackOff 2m58s (x7 over 4m43s) kubelet Back-off pulling image \"broken-image-ref\"\r\n ```\r\n\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":3114,"color":3115},"backend/kubernetes","bfdadc",3555,"Step freezes when container image can't be pulled (ImagePullBackOff)","2024-04-16T06:10:51Z","https://github.com/woodpecker-ci/woodpecker/issues/3555",0.7012227,{"description":3122,"labels":3123,"number":3125,"owner":3023,"repository":3024,"state":3073,"title":3126,"updated_at":3127,"url":3128,"score":3129},"### 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]",[3124],{"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.70175725,["Reactive",3131],{},["Set"],["ShallowReactive",3134],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f60QXryKcsHSh9SIwRPZaKnXwk7uX9PpEv9QxXOn_OSw":-1},"/woodpecker-ci/woodpecker/1430"]