\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]",[3035],{"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.71562696,{"description":3042,"labels":3043,"number":3044,"owner":3025,"repository":3026,"state":3045,"title":3046,"updated_at":3047,"url":3048,"score":3049},"### Component\n\ncli\n\n### Describe the bug\n\nI am getting the following error:\r\n\r\n```sh\r\nwoodpecker-cli secret add --organization \u003Corg> \u003Csecret> \u003Csecret value>\r\n10:11PM FTL error running cli error=\"invalid character '\u003C' looking for beginning of value\"\r\n```\r\n\r\nNB: I am running `woodpecker-cli` dev version on a WP 0.15.5 server install. Are they maybe incompatible?\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"0.15.5\"}\r\n\r\nwoodpecker-cli version next-b6399c0a (built from source for macOS arm64)\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).",[],1446,"closed","Error when adding organization wide secret","2022-11-24T09:05:13Z","https://github.com/woodpecker-ci/woodpecker/issues/1446",0.70442754,{"description":3051,"labels":3052,"number":3057,"owner":3025,"repository":3026,"state":3045,"title":3058,"updated_at":3059,"url":3060,"score":3061},"### Component\n\ncli\n\n### Describe the bug\n\nI have encountered a bug related to the version update notification when using the `woodpecker-cli`. \r\nDespite using the latest version `2.8.0` , the CLI incorrectly suggests updating to `2.7.3` : `A new version of woodpecker-cli is available: 2.7.3`\n\n### Steps to reproduce\n\n1. Download and install woodpecker-cli `2.8.0`\r\n2. Run:\r\n```sh\r\n$ woodpecker-cli lint .woodpecker.yml\r\n✅ Config is valid\r\nWRN A new version of woodpecker-cli is available: 2.7.3. Update by running: woodpecker-cli update\r\n\r\n$ woodpecker-cli -v\r\nwoodpecker-cli version 2.8.0\r\n```\n\n### Expected behavior\n\nThe update notification should not appear\n\n### System Info\n\n```shell\nwoodpecker-cli `2.8.0`\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]",[3053,3054],{"name":3019,"color":3020},{"name":3055,"color":3056},"build","6AB8BA",4527,"Bump version in `version.json` for back-ported releases","2025-02-24T12:37:54Z","https://github.com/woodpecker-ci/woodpecker/issues/4527",0.7077759,{"description":3063,"labels":3064,"number":3066,"owner":3025,"repository":3026,"state":3045,"title":3067,"updated_at":3068,"url":3069,"score":3070},"### Component\n\nserver\n\n### Describe the bug\n\nOn one of my projects CI is still triggered on push events but pipelines do not start anymore.\r\n\r\nThere is a runtime error on the server just after the push. Some other warnings complain about secrets not found but they are well defined at the organization level and the other project CIs are working fine.\r\n\r\nAlso, I can't cancel these stalled pipelines. I have already tried to reinstall Woodpecker without success.\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-d35ab57f\"}\r\n\r\nDeployed on Kubernetes\r\nHelmfile: https://github.com/Japan7/nanak8s/blob/main/apps/woodpecker/helmfile.yaml\r\nServer chart: https://github.com/babykart/woodpecker-helm/tree/server-sts/woodpecker-server\r\nAgent chart: https://github.com/woodpecker-ci/helm/tree/main/woodpecker-agent\n```\n\n\n### Additional context\n\n```\r\n[woodpecker-server-0] [xorm] [info] 2023/03/09 01:21:37.732964 PING DATABASE sqlite3\r\n[woodpecker-server-0] [xorm] [info] 2023/03/09 01:21:37.732964 PING DATABASE sqlite3\r\n[woodpecker-server-0] {\"level\":\"error\",\"error\":\"no secret found for \\\"registry_username\\\"\",\"time\":\"2023-03-09T01:21:42Z\",\"message\":\"paramsToEnv\"}\r\n[woodpecker-server-0] {\"level\":\"error\",\"error\":\"no secret found for \\\"registry_username\\\"\",\"time\":\"2023-03-09T01:21:42Z\",\"message\":\"paramsToEnv\"}\r\n[woodpecker-server-0] {\"level\":\"error\",\"error\":\"no secret found for \\\"webhook_id\\\"\",\"time\":\"2023-03-09T01:21:42Z\",\"message\":\"paramsToEnv\"}\r\n[woodpecker-server-0] {\"level\":\"error\",\"error\":\"no secret found for \\\"webhook_token\\\"\",\"time\":\"2023-03-09T01:21:42Z\",\"message\":\"paramsToEnv\"}\r\n[woodpecker-server-0] {\"level\":\"error\",\"error\":\"no secret found for \\\"webhook_id\\\"\",\"time\":\"2023-03-09T01:21:42Z\",\"message\":\"paramsToEnv\"}\r\n[woodpecker-server-0] \r\n[woodpecker-server-0] \r\n[woodpecker-server-0] 2023/03/09 01:21:47 [Recovery] 2023/03/09 - 01:21:47 panic recovered:\r\n[woodpecker-server-0] runtime error: invalid memory address or nil pointer dereference\r\n[woodpecker-server-0] /usr/local/go/src/runtime/panic.go:260 (0x454e95)\r\n[woodpecker-server-0] /usr/local/go/src/runtime/signal_unix.go:835 (0x454e65)\r\n[woodpecker-server-0] /woodpecker/src/github.com/woodpecker-ci/woodpecker/pipeline/frontend/yaml/compiler/settings/params.go:115 (0xc0b519)\r\n[woodpecker-server-0] /woodpecker/src/github.com/woodpecker-ci/woodpecker/pipeline/frontend/yaml/compiler/settings/params.go:37 (0xc0ac16)\r\n[woodpecker-server-0] /woodpecker/src/github.com/woodpecker-ci/woodpecker/pipeline/frontend/yaml/compiler/convert.go:82 (0xc151cd)\r\n[woodpecker-server-0] /woodpecker/src/github.com/woodpecker-ci/woodpecker/pipeline/frontend/yaml/compiler/compiler.go:244 (0xc13de4)\r\n[woodpecker-server-0] /woodpecker/src/github.com/woodpecker-ci/woodpecker/pipeline/stepBuilder.go:290 (0xc19f95)\r\n[woodpecker-server-0] /woodpecker/src/github.com/woodpecker-ci/woodpecker/pipeline/stepBuilder.go:140 (0xc185d2)\r\n[woodpecker-server-0] /woodpecker/src/github.com/woodpecker-ci/woodpecker/server/pipeline/items.go:81 (0xc373a4)\r\n[woodpecker-server-0] /woodpecker/src/github.com/woodpecker-ci/woodpecker/server/pipeline/create.go:133 (0xc359b7)\r\n[woodpecker-server-0] /woodpecker/src/github.com/woodpecker-ci/woodpecker/server/api/hook.go:178 (0xc7d198)\r\n[woodpecker-server-0] /woodpecker/src/github.com/woodpecker-ci/woodpecker/vendor/github.com/gin-gonic/gin/context.go:173 (0xccfe8d)\r\n[woodpecker-server-0] /woodpecker/src/github.com/woodpecker-ci/woodpecker/server/router/middleware/token/token.go:33 (0xccfa18)\r\n[woodpecker-server-0] /woodpecker/src/github.com/woodpecker-ci/woodpecker/vendor/github.com/gin-gonic/gin/context.go:173 (0xc74fbc)\r\n[woodpecker-server-0] /woodpecker/src/github.com/woodpecker-ci/woodpecker/server/router/middleware/session/user.go:72 (0xc74fa3)\r\n[woodpecker-server-0] /woodpecker/src/github.com/woodpecker-ci/woodpecker/vendor/github.com/gin-gonic/gin/context.go:173 (0xcd523e)\r\n[woodpecker-server-0] /woodpecker/src/github.com/woodpecker-ci/woodpecker/server/router/middleware/store.go:29 (0xcd5225)\r\n[woodpecker-server-0] /woodpecker/src/github.com/woodpecker-ci/woodpecker/vendor/github.com/gin-gonic/gin/context.go:173 (0xcd4ae7)\r\n[woodpecker-server-0] /woodpecker/src/github.com/woodpecker-ci/woodpecker/server/router/middleware/logger.go:23 (0xcd4aca)\r\n[woodpecker-server-0] /woodpecker/src/github.com/woodpecker-ci/woodpecker/vendor/github.com/gin-gonic/gin/context.go:173 (0xccf879)\r\n[woodpecker-server-0] /woodpecker/src/github.com/woodpecker-ci/woodpecker/server/router/middleware/header/header.go:38 (0xccf7a4)\r\n[woodpecker-server-0] /woodpecker/src/github.com/woodpecker-ci/woodpecker/vendor/github.com/gin-gonic/gin/context.go:173 (0xccf701)\r\n[woodpecker-server-0] /woodpecker/src/github.com/woodpecker-ci/woodpecker/server/router/middleware/header/header.go:30 (0xccf6e6)\r\n[woodpecker-server-0] /woodpecker/src/github.com/woodpecker-ci/woodpecker/vendor/github.com/gin-gonic/gin/context.go:173 (0xcd3eca)\r\n[woodpecker-server-0] /woodpecker/src/github.com/woodpecker-ci/woodpecker/server/router/router.go:39 (0xcd3eb0)\r\n[woodpecker-server-0] /woodpecker/src/github.com/woodpecker-ci/woodpecker/vendor/github.com/gin-gonic/gin/context.go:173 (0xa289e1)\r\n[woodpecker-server-0] /woodpecker/src/github.com/woodpecker-ci/woodpecker/vendor/github.com/gin-gonic/gin/recovery.go:101 (0xa289cc)\r\n[woodpecker-server-0] /woodpecker/src/github.com/woodpecker-ci/woodpecker/vendor/github.com/gin-gonic/gin/context.go:173 (0xa27850)\r\n[woodpecker-server-0] /woodpecker/src/github.com/woodpecker-ci/woodpecker/vendor/github.com/gin-gonic/gin/gin.go:616 (0xa274b8)\r\n[woodpecker-server-0] /woodpecker/src/github.com/woodpecker-ci/woodpecker/vendor/github.com/gin-gonic/gin/gin.go:572 (0xa26ffc)\r\n[woodpecker-server-0] /usr/local/go/src/net/http/server.go:2947 (0x79510b)\r\n[woodpecker-server-0] /usr/local/go/src/net/http/server.go:1991 (0x790326)\r\n[woodpecker-server-0] /usr/local/go/src/runtime/asm_amd64.s:1594 (0x472920)\r\n[woodpecker-server-0] \r\n[woodpecker-server-0] [xorm] [info] 2023/03/09 01:21:47.732848 PING DATABASE sqlite3\r\n[woodpecker-server-0] [xorm] [info] 2023/03/09 01:21:47.732873 PING DATABASE sqlite3\r\n```\r\n\r\nhttps://woodpecker.japan7.bde.enseeiht.fr/Japan7/nanapi/pipeline/1\r\n\r\n\u003Cimg width=\"1440\" alt=\"Capture d’écran 2023-03-08 à 20 37 59\" src=\"https://user-images.githubusercontent.com/20094890/223893014-d2e3e854-d811-49db-ab18-8161999dd6ee.png\">\r\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] 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).",[3065],{"name":3019,"color":3020},1609,"CI no longer starts","2023-03-17T07:54:55Z","https://github.com/woodpecker-ci/woodpecker/issues/1609",0.7100085,{"description":3072,"labels":3073,"number":3075,"owner":3025,"repository":3026,"state":3045,"title":3076,"updated_at":3077,"url":3078,"score":3079},"### Component\n\ncli\n\n### Describe the bug\n\nWoodpecker CLI logs the error after each step execution.\r\n\r\nSample pipeline:\r\n\r\n```\r\npipeline:\r\n step1:\r\n image: golang\r\n commands:\r\n - echo step1\r\n step2:\r\n image: golang\r\n commands:\r\n - echo step2\r\n```\r\n\r\nResult:\r\n\r\n```\r\nwoodpecker exec .woodpecker.yaml (k3d-akuity/akuity-platform)\r\n[step1:L0:0s] + echo step1\r\n[step1:L1:0s] step1\r\n8:04PM ERR process logging failed error=\"io: read/write on closed pipe\" CLI=exec\r\n[step2:L0:0s] + echo step2\r\n[step2:L1:0s] step2\r\n8:04PM ERR process logging failed error=\"io: read/write on closed pipe\" CLI=exec\r\n```\n\n### System Info\n\n```shell\nwoodpecker-cli version 0.15.6\r\n```\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] 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).",[3074],{"name":3019,"color":3020},1615," woodpecker-cli exec .woodpecker.yaml: \"io: read/write on closed pipe\"","2023-03-12T15:01:11Z","https://github.com/woodpecker-ci/woodpecker/issues/1615",0.7127063,{"description":3081,"labels":3082,"number":3085,"owner":3025,"repository":3026,"state":3045,"title":3086,"updated_at":3087,"url":3088,"score":3089},"* [ ] token for helm is not added to environment: https://ci.woodpecker-ci.org/woodpecker-ci/woodpecker/build/1918/29\r\n* [x] github release plugin do not work: https://ci.woodpecker-ci.org/woodpecker-ci/woodpecker/build/1918/15",[3083,3084],{"name":3019,"color":3020},{"name":3055,"color":3056},739,"Issues from rc2 run","2022-02-24T14:39:54Z","https://github.com/woodpecker-ci/woodpecker/issues/739",0.7134374,{"description":3091,"labels":3092,"number":3094,"owner":3025,"repository":3026,"state":3045,"title":3095,"updated_at":3096,"url":3097,"score":3098},"### Component\n\ncli\n\n### Describe the bug\n\n```sh\r\n$ woodpecker-cli setup\r\n4:44PM WRN Keyring is not supported on this platform\r\n4:44PM FTL error running cli error=\"unsupported platform\"\r\n```\n\n### Steps to reproduce\n\n1. Run `woodpecker-cli setup` on FreeBSD\n\n### Expected behavior\n\nI should be able to add a secret when running the cli from FreeBSD.\n\n### System Info\n\n```shell\nFreeBSD 14\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]",[3093],{"name":3019,"color":3020},4000,"cli: Keyring is not supported on this platform","2024-08-05T08:27:30Z","https://github.com/woodpecker-ci/woodpecker/issues/4000",0.7136223,{"description":3100,"labels":3101,"number":3103,"owner":3025,"repository":3026,"state":3045,"title":3104,"updated_at":3105,"url":3106,"score":3107},"### Component\n\nserver\n\n### Describe the bug\n\nI'm having job running issues with woodpecker v0.15.0. Builds stay stuck into queue ; they display as \"not yet started\" in the web interface. According to logs, the server is up and the agent seems able to connect to it. The only log I was able to get is when I try and jump to a pending job in the right panel in the web interface. Then the server complains : \r\n``` json\r\n{\"level\":\"error\",\"error\":\"Error #01: sql: no rows in result set\\n\",\"ip\":\"192.168.1.1\",\"latency\":15.180251,\"method\":\"GET\",\"path\":\"/api/repos/lafleur/wanderings/logs/19/1\",\"status\":404,\"time\":\"2022-04-01T13:34:57Z\",\"user-agent\":\"Mozilla/5.0 (X11; Linux x86_64; rv:98.0) Gecko/20100101 Firefox/98.0\",\"time\":\"2022-04-01T13:34:57Z\"}\r\n{\"level\":\"error\",\"error\":\"Error #01: sql: no rows in result set\\n\",\"ip\":\"::1\",\"latency\":14.972052,\"method\":\"GET\",\"path\":\"/api/repos/lafleur/wanderings/logs/19/1\",\"status\":404,\"time\":\"2022-04-01T13:34:57Z\",\"user-agent\":\"Mozilla/5.0 (X11; Linux x86_64; rv:98.0) Gecko/20100101 Firefox/98.0\",\"time\":\"2022-04-01T13:34:57Z\"}\r\n```\r\n\r\nI'm running on a barebone ARMv7 Arch system, installing through its [PKGBUILD](https://aur.archlinux.org/packages/woodpecker).\r\n\r\nI tried rolling back to v0.15.0-rc2. The result is the same, although this time the agent seems unable to connect to the server. Logs from the agent :\r\n``` json\r\n{\"level\":\"error\",\"error\":\"rpc error: code = Unavailable desc = closing transport due to: connection error: desc = \\\"error reading from server: EOF\\\", received prior goaway: code: ENHANCE_YOUR_CALM, debug data: \\\"too_many_pings\\\"\",\"time\":\"2022-04-01T13:47:45Z\",\"message\":\"grpc error: done(): code: Unavailable: rpc error: code = Unavailable desc = closing transport due to: connection error: desc = \\\"error reading from server: EOF\\\", received prior goaway: code: ENHANCE_YOUR_CALM, debug data: \\\"too_many_pings\\\"\"}\r\n```\r\nMy RC2 version is `next-c79aa2b1`.\r\n\r\nRolling back to [v0.15.0-rc1](https://github.com/woodpecker-ci/woodpecker/releases/tag/v0.15.0-rc1) (version `next-150c5e1c`) does workaround the issue.\r\n\r\nI compared my issue with #841 , and the logs do not match, hence this new issue.\r\n\r\nAny clue appreciated !\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-28b15120\"}\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).",[3102],{"name":3019,"color":3020},860,"all jobs stall as \"pending\" in queue since v0.15.0_RC2","2022-10-11T16:35:18Z","https://github.com/woodpecker-ci/woodpecker/issues/860",0.7220149,{"description":3109,"labels":3110,"number":3112,"owner":3025,"repository":3026,"state":3045,"title":3113,"updated_at":3114,"url":3115,"score":3116},"### 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]",[3111],{"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.7277205,["Reactive",3118],{},["Set"],["ShallowReactive",3121],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fF5jWZQe6_6gzfiD3hHozIYko27A240HwlV-G5LafG9E":-1},"/woodpecker-ci/woodpecker/1215"]