\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]",[3209,3210],{"name":3152,"color":3153},{"name":3211,"color":3212},"forge/bitbucket","E96280",5338,"closed","Build status not completing on matrix pipelines with BitBucket","2025-08-10T17:51:17Z","https://github.com/woodpecker-ci/woodpecker/issues/5338",0.73836285,{"description":3220,"labels":3221,"number":3226,"owner":3155,"repository":3156,"state":3214,"title":3227,"updated_at":3228,"url":3229,"score":3230},"### Component\n\nserver\n\n### Describe the bug\n\nI tried to squash a pull request and after the squashed commit hadn't any pipelines. The Gitea webhook history confirmed the problem on woodpeckers side with and a 500 error code.\r\n\r\n```\r\ngitea-woodpecker-server-1 | {\"time\":\"2022-09-17T16:51:11Z\",\"message\":\"LogLevel = warn\"}\r\ngitea-woodpecker-server-1 | {\"level\":\"error\",\"error\":\"pq: value too long for type character varying(255)\",\"time\":\"2022-09-17T17:45:59Z\",\"message\":\"failure to save build for [domain.tld/ansible-vyos](http://domain.tld/ansible-vyos)\"}\r\ngitea-woodpecker-server-1 | {\"level\":\"error\",\"error\":\"pq: value too long for type character varying(255)\",\"time\":\"2022-09-17T17:47:14Z\",\"message\":\"failure to save build for [domain.tld/ansible-vyos](http://domain.tld/ansible-vyos)\"}\r\ngitea-woodpecker-server-1 | {\"level\":\"error\",\"error\":\"pq: value too long for type character varying(255)\",\"time\":\"2022-09-17T17:50:11Z\",\"message\":\"failure to save build for [domain.tld/ansible-vyos](http://domain.tld/ansible-vyos)\"}\r\n```\n\n### System Info\n\n```shell\n0.15.3\n```\n\n\n### Additional context\n\nI confirmed that the commit message is longer that 255 chars. I also found that some of the commits in this repo still have pending ci runs. It would be imaginable that this is also a reason for them.\r\nhttps://github.com/woodpecker-ci/woodpecker/commit/eaf05dbae84b751ee972daae97f626f7de61487d\r\n\r\nI found that git commit messages count be theoretically unlimited in size: https://stackoverflow.com/a/9733857\r\nMaybe a SQL column type of `TEXT` should be used.\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).",[3222,3223],{"name":3152,"color":3153},{"name":3224,"color":3225},"server","5D7A92",1194,"Commit message to long for db column ","2022-10-12T22:47:13Z","https://github.com/woodpecker-ci/woodpecker/issues/1194",0.75291467,{"description":3232,"labels":3233,"number":3235,"owner":3155,"repository":3156,"state":3214,"title":3236,"updated_at":3237,"url":3238,"score":3239},"### 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]",[3234],{"name":3152,"color":3153},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.7582023,{"description":3241,"labels":3242,"number":3245,"owner":3155,"repository":3156,"state":3214,"title":3246,"updated_at":3247,"url":3248,"score":3249},"if the pipeline fails because of an external issue like:\r\n\r\nhttps://ci.woodpecker-ci.org/repos/3780/pipeline/11472\r\n\r\nthe restarted pipeline do not find the pipeline config:\r\n\r\nhttps://ci.woodpecker-ci.org/repos/3780/pipeline/11475/errors\r\n\r\nI would expect that the pipeline restart with the old config and try to fetch external things like e.g. secrets again",[3243,3244],{"name":3152,"color":3153},{"name":3224,"color":3225},3107,"Can not restart failed pipelines","2024-01-03T11:56:52Z","https://github.com/woodpecker-ci/woodpecker/issues/3107",0.75947595,{"description":3251,"labels":3252,"number":3254,"owner":3155,"repository":3156,"state":3214,"title":3255,"updated_at":3256,"url":3257,"score":3258},"### Component\n\nweb-ui\n\n### Describe the bug\n\nHello everyone !\r\n\r\nFirst of all, thank you for the great work you do here!\r\n\r\nWe have a problem on our Woodpecker test instance; when running steps, the logs only appear after the step is completed. During execution, the log window remains black, which can be a problem when some tasks are very long.\r\n\r\nAs a quick diagnostic:\r\n* https://host/stream/logs/org/repo/34/6 returns event=error, data=eof during the step execution\r\n\r\n```\r\n: ping\r\n\r\nevent: error\r\ndata: eof\r\n```\r\n\r\nThe woodpecker server logs:\r\n```\r\n{\"level\":\"error\",\"error\":\"stream: not found\",\"time\":\"2021-12-08T14:45:36Z\",\"message\":\"tail of logs failed\"}\r\n```\r\n\r\nit is always the case. As soon as the step is finished (failed or successful), the logs are displayed as if by magic.\r\nAny idea ?\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-03a43567\"}\n```\n\n\n### Additional context\n\n```shell\nThe woodpecker-server is on the same machine as the woodpecker-agent, both running with docker-compose.\r\n\r\nA Caddy reverse-proxy is setup in front of the woodpecker-server (reverse of localhost:8000) and the WOODPECKER_HOST variable is setup.\r\n\r\nThe build works fine, just the logs don't appear.\n```\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] Check that this is a concrete bug. For Q&A join our [Discord Chat Server](https://discord.gg/fcMQqSMXJy).",[3253],{"name":3152,"color":3153},580,"Tail of logs failed - logs only appear after the step","2023-06-12T23:53:33Z","https://github.com/woodpecker-ci/woodpecker/issues/580",0.7651902,["Reactive",3260],{},["Set"],["ShallowReactive",3263],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f_CqldTJa9MAL7x3JxB5taxVT3w9midtb7NP2nTrUbac":-1},"/woodpecker-ci/woodpecker/705"]