\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]",[3018],{"name":3019,"color":3020},"bug","d73a4a",5338,"woodpecker-ci","woodpecker","open","Build status not completing on matrix pipelines with BitBucket","2025-07-17T18:03:12Z","https://github.com/woodpecker-ci/woodpecker/issues/5338",0.6965447,{"description":3030,"labels":3031,"number":3033,"owner":3022,"repository":3023,"state":3024,"title":3034,"updated_at":3035,"url":3036,"score":3037},"### Component\n\nagent, web-ui\n\n### Describe the bug\n\nOn all my pipelines only the first few log lines appear in the webui. Then everything else is cut out. I can certainly see the log output when I kubectl logs wp-1234.... the step/pipeline, bit it doesn't seem to get sent to the server from the agent.\r\n\r\nI also see a lot of \r\n`{\"level\":\"error\",\"repo\":\"renovatebot/renovate\",\"pipeline\":\"2064\",\"workflow_id\":\"6848\",\"image\":\"docker.io/woodpeckerci/plugin-git:2.5.1\",\"workflow_id\":\"6848\",\"error\":\"io: read/write on closed pipe\",\"time\":\"2024-11-17T13:04:52Z\",\"message\":\"copy limited logStream part\"}`\r\n\r\non the agent and \r\n\r\n`{\"level\":\"error\",\"repo_id\":\"29\",\"pipeline_id\":\"4660\",\"workflow_id\":\"6871\",\"error\":\"stream: not found\",\"time\":\"2024-11-18T12:55:30Z\",\"message\":\"done: cannot close log stream for step 21827\"}` and `{\"level\":\"error\",\"repo_id\":\"29\",\"pipeline_id\":\"4660\",\"workflow_id\":\"6871\",\"error\":\"sql: no rows in result set\",\"time\":\"2024-11-18T12:55:30Z\",\"message\":\"queue.Done: cannot ack workflow\"}`\r\n\r\non the server.\r\n\r\nIt has to be mentioned, that before a month ago (I upgrade woodpecker almost immediately after release) the logs worked almost flawlessly for more than a year, since I switched from drone to woodpecker.\r\n\r\nCurrently I don't know where to start debugging, to get to the bottom of this. Do you have any pointers?\n\n### Steps to reproduce\n\ninstall woodpecker using the helm chart version 1.6.2 on a kubernetes cluster v1.31 only setting WOODPECKER_BACKEND_K8S_STORAGE_RWX: false beside the setup with a forge using https://woodpecker-ci.org/docs/next/administration/forges/forgejo\n\n### Expected behavior\n\nI expect to always get all the logs, when I click on a step/workflow. \n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.7.3\"}\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]",[3032],{"name":3019,"color":3020},4409,"Logs only showing the first few lines of each step","2024-11-19T10:25:07Z","https://github.com/woodpecker-ci/woodpecker/issues/4409",0.7187619,{"description":3039,"labels":3040,"number":3044,"owner":3022,"repository":3023,"state":3045,"title":3046,"updated_at":3047,"url":3048,"score":3049},"# Required open issues / PRs\r\n- [x] #4314 fixed\r\n- [x] v2.8.0 with https://github.com/woodpecker-ci/woodpecker/issues/4306 released\r\n- [x] service settings (https://github.com/woodpecker-ci/woodpecker/pull/4336)\r\n- [ ] ...\r\n\r\n# Breaking changes (sorted by impact for users)\r\n\r\n- change of webhook => requires repair all #4013 \r\n- removed deprecated keywords: \r\n - `pipeline`, `platform`, `branches`, `steps.[name].secrets` #4363 #3916 \r\n - `steps.[name].group`, removed `include` / `exclude` from when filter #4016\r\n- removed privileged plugins: `plugins/docker`, `plugins/gcr`, `plugins/ecr`, `woodpeckerci/plugin-docker-buildx` #3846\r\n- removed alternative names for secrets, use `environment` with `from_secret` #4016\r\n- removed `environment` for `when.evaluate` #4016\r\n- removed slice definition for env vars #4016\r\n- #4005\r\n- #3785\r\n- stopped secrets from being uppercased #4053\r\n- replaced cli `registry` command with `repo registry` #4017\r\n- some changes / removals of api routes / json properties #3968\r\n- cron not using seconds anymore #3785\r\n- (Left out less relevant changes, Please add other impact-full changes)\r\n\r\n# Tasks before releasing\r\n- Update go imports to `\"go.woodpecker-ci.org/woodpecker/v3/...\"`\r\n- Check and adjust migration docs, so users can simply follow and get to the new version. testing\r\n- Create new docs version 3.0\r\n- Create blog post\r\n- Test version \r\n- Post on social media",[3041],{"name":3042,"color":3043},"governance","A46EFE",4320,"closed","Release plan for v3.0.0","2025-01-18T23:31:56Z","https://github.com/woodpecker-ci/woodpecker/issues/4320",0.6600497,{"description":3051,"labels":3052,"number":3056,"owner":3022,"repository":3023,"state":3045,"title":3057,"updated_at":3058,"url":3059,"score":3060},"To have less breaking changes in the future to not annoy users again and again, breaking changes should be part of the next version.\r\n\r\n# Some ideas\r\n- [x] replace `DRONE_` env vars with `WOODPECKER_` prefix #218\r\n- [x] drop Gitea basic auth support #365\r\n- [x] change config path resolution (`.woodpecker/*.ymll` -> `.woodpecker.yml` -> `.drone.yml`) #299 \r\n- [x] replace repository hooks setting with only allow PRs #281\r\n- [ ] ~~migrate to cert-magic #360~~\r\n- [x] remove `DRONE_` env vars passed to pipeline steps (only use `CI_`) #427 \r\n- [x] rename default paths `/var/lib/drone` => `/var/lib/woodpecker` and `/drone` => `/woodpecker` #431 \r\n- [x] rename default datasource: `/var/lib/drone/drone.sqlite` => `/var/lib/woodpecker/woodpecker.sqlite` #438 \r\n- [x] rename prometheus namespace `drone` => `woodpecker` #439 \r\n- pipeline config changes\r\n - [x] move plugin-settings in pipeline steps to some sub-setting like: `pipeline.[step].settings` and pass all KV options as `PLUGIN_` #464 \r\n - [ ] remove support for `root.pipeline.[step].commands` string values in favor of array lists\r\n - [x] ~~move `root.skip_clone` under `root.clone.skip`~~\r\n - [ ] ~~move `root.platform`, `root.branches`, `root.labels`, `root.runs_on`, `root.depends_on` to `root.when.xxx` to match step filters~~ #283 -> next release\r\n - [ ] ~~make `root.when` and `root.pipeline.[step].when` an array of the current with items using the current settings to allow ORs~~ non breaking & can move into next release\r\n - [ ] ~~remove `root.Cache` and functionality in favor of plugins?~~ - need more discussion\r\n",[3053],{"name":3054,"color":3055},"summary","C3DC73",393,"Breaking changes before releasing 0.15.0","2022-01-09T07:14:00Z","https://github.com/woodpecker-ci/woodpecker/issues/393",0.6658497,{"description":3062,"labels":3063,"number":3065,"owner":3022,"repository":3023,"state":3045,"title":3066,"updated_at":3067,"url":3068,"score":3069},"### Prerequisites\n\n- [ ] MAJOR: Check `docs/src/pages/migrations.md`\n - [ ] Check whether it contains all the necessary migration steps and recommended actions for users and administrators\n - [ ] Check whether the steps refer to the associated pull requests or issues\n - [ ] Ensure that the steps are clear and describe the actions required for the migration\n - Good: \"Rename your `branch` configuration option to `when.branch` (PR#123)\"\n - Bad: \"Remove the `branch` configuration option in favor of `when.branch`\"\n - If possible, provide background information so users can understand the change\n- [ ] MAJOR: Create a blog entry in `docs/blog/` that highlights the most important changes and includes a link to the release notes.\n- [x] Prepare docs PR for new version and delete old versions (keep only the last three minor versions for the current major version) https://github.com/woodpecker-ci/woodpecker/pull/5154\n - [x] Copy `docs/docs` to `docs/versioned_docs/version-\u003Cversion>` and delete old versions\n - [x] Create `docs/versioned_sidebars/version-\u003Cversion>-sidebars.json` and delete old ones\n - [x] Add new version to `docs/versions.json` and delete old versions\n - [x] Add new version to the version list in `docs/src/pages/versions.md`\n- [x] Announce the release in the maintainer chat and ask for pending blockers\n\n### Release\n\n- [x] Test the latest container images to make sure they work as expected\n- [x] Update `https://ci.woodpecker.org` to the latest version of `next` and verify that it works as expected\n- [x] Merge the release PR to start the release pipeline\n\n### Post-release\n\n- [x] Merge the docs PR\n- [x] Release the Helm Chart. If renovate has not created the upgrade PR already, manually trigger it from the Dependency Dashboard.\n- [ ] Announce release in relevant chats and on social media platforms\n - [ ] Mastodon (check if already posted from the release pipeline)\n - [ ] Matrix\n - [ ] Twitter",[3064],{"name":3042,"color":3043},5153,"☂️ Release Woodpecker v3.6","2025-05-07T13:00:31Z","https://github.com/woodpecker-ci/woodpecker/issues/5153",0.67354697,{"description":3071,"labels":3072,"number":3079,"owner":3022,"repository":3023,"state":3045,"title":3080,"updated_at":3081,"url":3082,"score":3083},"Add a own section called `compile` into pipeline config.\r\n\r\nwitch use normal workflow logic (default or custom clone) ... but it's output is no log but an pipeline config.\r\n\r\ntldr: with way we could support **starlark**, jsonnet (#1396), drone >= 1.0, ... without needing to add it to woodpecker core\r\n\r\n## details\r\nwe either could make a special compile pipeline, and show it as own entry, witch trigger the actual pipeline with its config\r\n(if we do so, we need to somehow link them UI/UX wise ...)\r\nor we just use our multi workflow approach ... where one workflow (eventually with a different icon) is the compile and all generated workflows from it are also i it ... (as a compile could create one or more workflows)\r\n\r\nwe need to make sure we dont have a recursion in it -> see permutate example\r\n\r\n## example:\r\n```yaml\r\ncompile:\r\n image: wp/jsonnet\r\n settings:\r\n file: woodpecker.jsonnet\r\n```\r\n```yaml\r\ncompile:\r\n image: wp/replace-image # permutate normal wp pipeline config\r\n\r\npipeline:\r\n normal-steps:\r\n...\r\n```\r\n\r\n## workaround:\r\nuse a [ Configuration Service](https://woodpecker-ci.org/docs/next/administration/external-configuration-api)",[3073,3076],{"name":3074,"color":3075},"feature","180DBE",{"name":3077,"color":3078},"pipeline-config","1BE540",1400,"RFC: pipeline compile step","2023-08-20T15:57:51Z","https://github.com/woodpecker-ci/woodpecker/issues/1400",0.6891392,{"description":3085,"labels":3086,"number":3087,"owner":3022,"repository":3023,"state":3045,"title":3088,"updated_at":3089,"url":3090,"score":3091},"Thank you so much for this project!\r\n\r\nThe project description says Woodpecker is \"a highly opinionated fork\" of Drone CI, but neither docs nor the repos mention what those opinions are, what the difference to Drone is and why one would choose one over the other.\r\n\r\nThe original motivation is laid out in now archived https://github.com/laszlocph/drone-oss, but I think it could be very helpful for those new to either with a brief FAQ in the readme and/or docs",[],165,"[Docs] Motivation and goals","2021-09-11T15:10:32Z","https://github.com/woodpecker-ci/woodpecker/issues/165",0.697557,{"description":3093,"labels":3094,"number":3101,"owner":3022,"repository":3023,"state":3045,"title":3102,"updated_at":3103,"url":3104,"score":3105},"\u003C!-- PLEASE READ BEFORE DELETING\r\n\r\nBugs or Issues? Please do not open a GitHub issue until you have\r\ndiscussed and verified with community support:\r\n\r\n https://discourse.drone.io/\r\n\r\nFailing Builds? Please do not use GitHub issues for generic support\r\nquestions. Instead please use Stack Overflow:\r\n\r\n http://stackoverflow.com/questions/tagged/drone.io\r\n\r\n-->\r\n\r\nAs the current .drone.yml files are not supported by woodpecker, it seems to useful to switch to supporting .woodpecker.yml as a default configuration source",[3095,3098],{"name":3096,"color":3097},"enhancement","7E1FE4",{"name":3099,"color":3100},"breaking","A1B83C",133,"Use .woodpecker.yml as default pipeline config file","2021-09-17T19:40:44Z","https://github.com/woodpecker-ci/woodpecker/issues/133",0.6980193,{"description":3107,"labels":3108,"number":3115,"owner":3022,"repository":3023,"state":3045,"title":3116,"updated_at":3117,"url":3118,"score":3119},"### Component\n\nserver\n\n### Describe the bug\n\nIf you have a repository on forgejo with more than 1000 files that are sorted before the 'pipeline path' directory, woodpecker will be unable to find the configuration file(s).\n\nThis most likely happens because woodpecker relies on the `api/v1/repos/$OWNER/$REPOSITORY/git/trees/$sha?recursive=1` api call which is paginated on every 1000 items and might not include the actual pipeline config file(s) if enough other files are sorted in front.\n\nThis can be observed by looking at the forgejo router logs which i have attached below.\n\nThis might be something similar to what happened in #1514 but i don't get the explicit 'config not found' error, neither in the UI nor in the woodpecker logs.\n\n\n### Steps to reproduce\n\n1. Have a generally working Woodpecker Server properly configured for a forgejo instance\n2. Create a new repository with a woodpecker workflow configured in `.woodpecker/stuff.yml` and >1000 files in `.ansible/`\n3. Try to trigger any kind of pipeline.\n4. The woodpecker UI will show \"No pipelines have been started yet.\" for the configured repository no matter how hard you try to start a pipeline.\n\n### Expected behavior\n\nI would expect pipelines configured in the **default** location to just work no matter what.\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"3.0.1\"}\n\nForgejo version: 10.0.0\n```\n\n### Additional context\n\n\u003Cdetails>\n\u003Csummary>Forgejo router logs for one webhook trigger\u003C/summary>\n\n```\n2025-01-27 21:06:20.715\t\u003C5>router: completed GET /api/v1/repos/histalek/infrastructure/git/trees/4788b8cb23b10ba4e6c8317b91e739a504c15fac?recursive=1 for 10.89.0.3:38568, 200 OK in 193.0ms @ repo/tree.go:14(repo.GetTree)\n\n2025-01-27 21:06:20.725\t\u003C5>router: completed GET /api/v1/version for 10.89.0.3:38568, 200 OK in 1.1ms @ misc/version.go:15(misc.Version)\n\n2025-01-27 21:06:20.760\t\u003C5>router: completed GET /api/v1/repos/histalek/infrastructure/raw/.woodpecker/?ref=4788b8cb23b10ba4e6c8317b91e739a504c15fac for 10.89.0.3:38568, 404 Not Found in 33.0ms @ repo/file.go:43(repo.GetRawFile)\n\n2025-01-27 21:06:20.765\t\u003C5>router: completed GET /api/v1/version for 10.89.0.3:38568, 200 OK in 1.5ms @ misc/version.go:15(misc.Version)\n\n2025-01-27 21:06:20.787\t\u003C5>router: completed GET /api/v1/repos/histalek/infrastructure/raw/.woodpecker.yaml?ref=4788b8cb23b10ba4e6c8317b91e739a504c15fac for 10.89.0.3:38568, 404 Not Found in 19.3ms @ repo/file.go:43(repo.GetRawFile)\n\n2025-01-27 21:06:20.791\t\u003C5>router: completed GET /api/v1/version for 10.89.0.3:38568, 200 OK in 1.2ms @ misc/version.go:15(misc.Version)\n\n2025-01-27 21:06:20.811\t\u003C5>router: completed GET /api/v1/repos/histalek/infrastructure/raw/.woodpecker.yml?ref=4788b8cb23b10ba4e6c8317b91e739a504c15fac for 10.89.0.3:38568, 404 Not Found in 18.0ms @ repo/file.go:43(repo.GetRawFile)\n\n2025-01-27 21:06:20.855\t\u003C5>router: polling GET /user/events for 10.89.0.3:38566, elapsed 3226.2ms @ events/events.go:18(events.Events)\n```\n\n\u003C/details>\n\nIf you would call `/api/v1/repos/histalek/infrastructure/git/trees/4788b8cb23b10ba4e6c8317b91e739a504c15fac?recursive=1 ` manually and inspect the output you would not find any files in '.woodpecker/'. (In my case that is because i have ~15.000 files in `.ansible/`; ansible collections ...).\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]",[3109,3110,3113],{"name":3019,"color":3020},{"name":3111,"color":3112},"forge/gitea","E96280",{"name":3114,"color":3112},"forge/forgejo",4789,"Woodpecker fails to find contents of 'pipeline path' directory on forgejo","2025-02-15T19:40:36Z","https://github.com/woodpecker-ci/woodpecker/issues/4789",0.69990355,{"description":3121,"labels":3122,"number":3123,"owner":3022,"repository":3023,"state":3045,"title":3124,"updated_at":3125,"url":3126,"score":3127},"When we enable a repo, deployment and push events gets automatically enabled. We have automation of onboarding new microservices, where a part includes creating repo and integrate woodpecker. We drone cli to enable repos at the same time we want to enable tag based events. Is there any other way I can do this, like an API call? ",[],243,"woodpecker cli to support enabling tag based builds","2021-09-18T14:28:35Z","https://github.com/woodpecker-ci/woodpecker/issues/243",0.70085937,["Reactive",3129],{},["Set"],["ShallowReactive",3132],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f8xJMTQ5K1j8EJWD8UMEnKkM0KnxTWO2Gx4QyPPN4P0M":-1},"/woodpecker-ci/woodpecker/869"]