\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]",[3033],{"name":3034,"color":3035},"bug","d73a4a",5338,"Build status not completing on matrix pipelines with BitBucket","2025-07-17T18:03:12Z","https://github.com/woodpecker-ci/woodpecker/issues/5338",0.73908544,{"description":3042,"labels":3043,"number":3048,"owner":3023,"repository":3024,"state":3025,"title":3049,"updated_at":3050,"url":3051,"score":3052},"### Component\r\n\r\nweb-ui\r\n\r\n### Describe the bug\r\n\r\nWe have a good state build, but the WEB UI shows a bad build result badge:\r\n\r\n\r\nWe have newer seen this problem before!\r\n\r\n### Steps to reproduce\r\n\r\n...don't know...\r\n\r\n### Expected behavior\r\n\r\n_No response_\r\n\r\n### System Info\r\n\r\n```shell\r\n{\r\n\"source\": \"https://github.com/woodpecker-ci/woodpecker\",\r\n\"version\": \"2.7.3\"\r\n}\r\n```\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\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]",[3044,3047],{"name":3045,"color":3046},"server","5D7A92",{"name":3020,"color":3021},4505,"Allow badges to include more than just push events","2025-03-07T18:14:49Z","https://github.com/woodpecker-ci/woodpecker/issues/4505",0.74910843,{"description":3054,"labels":3055,"number":3060,"owner":3023,"repository":3024,"state":3025,"title":3061,"updated_at":3062,"url":3063,"score":3064},"### Component\n\ncli\n\n### Describe the bug\n\nRunning a pipeline directly like this:\r\n\r\n```console\r\n$ woodpecker exec .woodpecker/ubuntu.yml\r\n...\r\n[build:L188:17s] + ./get-deps.sh\r\n[build:L189:17s] /bin/sh: 30: ./get-deps.sh: not found\r\n```\r\n\r\nfails to mount the repo, so fails to run the `get-deps.sh` script that is present in the repo.\r\n\r\nHowever, running it like this:\r\n\r\n```console\r\n$ woodpecker exec .\r\n# ci.yml\r\n\r\n# ci.yml\r\n\r\n# rust.yml\r\n\r\n# ci.yml\r\n\r\n# ci.yml\r\n\r\n# ci.yml\r\n\r\n# ci.yml\r\n\r\n# ci.yml\r\n\r\n# codecov.yml\r\n\r\n# audit.yaml\r\n\r\n# benchmarks.yaml\r\n\r\n# coverage.yaml\r\n\r\n# test.yaml\r\n\r\n# ci.yml\r\n\r\n# FUNDING.yml\r\n...\r\n```\r\n\r\nworryingly enumerates all the various yaml files in my working copy (those shown are from misc .cache and .github directories) as shown above, as if it were trying to run those, but does mount the repo and is able to run the script from inside it.\r\n\r\nMy expectation is that I can specify the pipeline I want to run based on the `--help` output:\r\n\r\n```console\r\n$ woodpecker exec --help\r\n...\r\nUSAGE:\r\n woodpecker-cli exec [command options] [path/to/.woodpecker.yaml]\r\n```\r\n\r\nand have the repo mounted in the pipeline at the same time.\r\n\n\n### System Info\n\n```shell\n$ woodpecker --version\r\nwoodpecker-cli version 1.0.2\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).",[3056,3057],{"name":3034,"color":3035},{"name":3058,"color":3059},"cli","1d76db",2511,"`woodpecker exec .woodpecker/ubuntu.yml` has no repo available","2024-07-03T03:54:28Z","https://github.com/woodpecker-ci/woodpecker/issues/2511",0.749496,{"description":3066,"labels":3067,"number":3069,"owner":3023,"repository":3024,"state":3025,"title":3070,"updated_at":3071,"url":3072,"score":3073},"### 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]",[3068],{"name":3034,"color":3035},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.7583658,{"description":3075,"labels":3076,"number":3086,"owner":3023,"repository":3024,"state":3087,"title":3088,"updated_at":3089,"url":3090,"score":3091},"Summary of UI issues and smaller changes (based on new UI from #245) which can be posted as comments. For complex improvements please open a separate issue.\r\n\r\n# UI improvements\r\n- [x] improve responsive (mobile) usage\r\n- [x] improve darkmode favicon #576 \r\n- [x] favicon to show pipeline status #576 \r\n- [x] use textarea for secret values (to support long texts like ssh keys) #574 \r\n- [x] show PR name / id instead of target branch if `ref: refs/pull/xxx/merge`\r\n- [x] Show matrix options in build view #526 \r\n- [x] add page `/\u003Cuser-or-group-name>` to view all enabled woodpecker repos of a user / group\r\n- [x] use icons for build proc status (currently just colored points)\r\n\r\n# UI bugs\r\n- [x] #469 \r\n- [x] fix overflowing commit messages #528\r\n- [x] fix back button (direct page load) to go back in history or to some default if history is empty #529 \r\n- [x] fix new build updates not being used / send (new builds are not added list)\r\n- [x] fix flickering when adding new log-lines while step is running\r\n\r\nNext Round: #1314",[3077,3080,3083],{"name":3078,"color":3079},"ui","46DEA2",{"name":3081,"color":3082},"summary","C3DC73",{"name":3084,"color":3085},"ux","fef2c0",468,"closed","Feedback: UI :speech_balloon:","2022-10-22T19:39:41Z","https://github.com/woodpecker-ci/woodpecker/issues/468",0.7155145,{"description":3093,"labels":3094,"number":3098,"owner":3023,"repository":3024,"state":3087,"title":3099,"updated_at":3100,"url":3101,"score":3102},"### Clear and concise description of the problem\n\nIf I have a long list of pipelines and steps and one of them fails, GitHub will present me the link to it. But if I click on that link the woodpecker UI does not take me to that particular pipeline/workflow, I have to scroll down till I find the correct one.\n\n### Suggested solution\n\nscroll the pipeline/workflow into view according to the information given in the URL, similar as done for the log-line number if the URL has a `#L` attached to it\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/versions]\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.",[3095,3096,3097],{"name":3078,"color":3079},{"name":3020,"color":3021},{"name":3084,"color":3085},5081,"scroll to pipeline when navigating through an URL/link","2025-04-18T19:58:47Z","https://github.com/woodpecker-ci/woodpecker/issues/5081",0.71902573,{"description":3104,"labels":3105,"number":3109,"owner":3023,"repository":3024,"state":3087,"title":3110,"updated_at":3111,"url":3112,"score":3113},"### Clear and concise description of the problem\n\nI can't seem to find a way to load pipelines from a different repository into my current repository.\r\nI don't want to copy my pipeline-file over and over again into multiple repositories. This is very error prone and when I want to change something I'd have to do it so many times.\n\n### Suggested solution\n\nImplement pipeline templates like drone-ci does.\n\n### Alternative\n\n_No response_\n\n### Additional context\n\nI want to switch from drone-ci to woodpecker, but this missing feature is killing me.\r\nDrone has [Pipeline templates](https://docs.drone.io/template/yaml/).\r\nWould love to see this coming in the next releases.\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.",[3106],{"name":3107,"color":3108},"feature","180DBE",3633,"Pipeline Templates","2024-04-21T07:20:55Z","https://github.com/woodpecker-ci/woodpecker/issues/3633",0.73906696,{"description":3115,"labels":3116,"number":3118,"owner":3023,"repository":3024,"state":3087,"title":3119,"updated_at":3120,"url":3121,"score":3122},"### Clear and concise description of the problem\n\nI'm wishing for an way to grant individual pipeline executions access to external resources based on their identity (repo name, branch, git-commit, pipeline name, trigger by, ...). External resources includes things such as container registries.\nSigning and generating attestations for artifacts with [Sigstore's `cosign`](https://www.sigstore.dev/), which is growing need due to EU legislation such as NIS2, requires a away to identity the build pipeline to issues signing certificates.\n\n### Suggested solution\n\nThe core idea is to take inspiration from [Github Actions where tokens are issues to pipelines on-demand](https://docs.github.com/en/actions/security-for-github-actions/security-guides/automatic-token-authentication), and implement an OAuth2 provider into Woodpecker that issues token to pipelines with specialized fields and claims identifying the specific pipeline execution.\n\n### Alternative\n\nAdding secrets to pipelines via the existing secrets mechanism can give us some of the functionality, but lacks the fine-grained access that can be given by issuing tokens with exact information about a specific pipeline execution. It is also vulnerable to secret leakage since the secret have a life-time far greater that an single execution.\n\n### Additional context\n\nA lot of legislation is arriving that demands greater and greater cyber security and supply-chain security. Figuring out how we can best support `cosign` with Woodpecker can become important for future use of Woodpecker in commercial settings. And personally I'm very interested in being able to produce [SLSA](https://slsa.dev/) level 3 compliant software artifacts.\n\n### Validations\n\n- [x] Checked that the feature isn't part of the `next` version already [https://woodpecker-ci.org/versions]\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.",[3117],{"name":3107,"color":3108},4837,"Workload identities for pipelines","2025-02-25T09:05:13Z","https://github.com/woodpecker-ci/woodpecker/issues/4837",0.7404468,{"description":3124,"labels":3125,"number":3128,"owner":3023,"repository":3024,"state":3087,"title":3129,"updated_at":3130,"url":3131,"score":3132},"### Component\r\n\r\nweb-ui\r\n\r\n### Describe the bug\r\n\r\njust saw this... Open for example https://ci.woodpecker-ci.org/woodpecker-ci/woodpecker/pipeline/6081 and look at the changed files counter\r\n\r\n### System Info\r\n\r\n```shell\r\nour ci\r\n```\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n\r\n",[3126,3127],{"name":3034,"color":3035},{"name":3078,"color":3079},1843,"Changed files counter shows 0 if opening pipeline directly","2023-10-15T07:14:06Z","https://github.com/woodpecker-ci/woodpecker/issues/1843",0.7470119,["Reactive",3134],{},["Set"],["ShallowReactive",3137],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fHiNwsW1hWmv4njduvhorE4Lyl8-rDuJSr3Pv3Q3kE00":-1},"/woodpecker-ci/woodpecker/1299"]