\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]",[3036],{"name":3037,"color":3038},"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.69580555,{"description":3045,"labels":3046,"number":3051,"owner":3026,"repository":3027,"state":3028,"title":3052,"updated_at":3053,"url":3054,"score":3055},"### 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).",[3047,3048],{"name":3037,"color":3038},{"name":3049,"color":3050},"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.7046295,{"description":3057,"labels":3058,"number":3060,"owner":3026,"repository":3027,"state":3028,"title":3061,"updated_at":3062,"url":3063,"score":3064},"### Component\n\nweb-ui\n\n### Describe the bug\n\nWhen there is an error in one of the workflows , the UI does not show which file is causing the error:\r\n\r\nIn this project I have `build.yml` and `release.yml` and the UI gives me that:\r\n\r\n\r\n\r\nThe error was in workflow `release.yml` (which was not triggerd), but not in build.yml.\r\n\r\n\n\n### Steps to reproduce\n\nSchould be obvious\n\n### Expected behavior\n\nIch would like to see, which file / workflow is causing the error.\n\n### System Info\n\n```shell\nWoodpecker 2.7.3 (docker image)\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]",[3059],{"name":3020,"color":3021},4376,"error message in UI does not point to workflow / yaml file","2024-11-14T14:27:25Z","https://github.com/woodpecker-ci/woodpecker/issues/4376",0.7258396,{"description":3066,"labels":3067,"number":3069,"owner":3026,"repository":3027,"state":3070,"title":3071,"updated_at":3072,"url":3073,"score":3074},"### Component\n\nserver\n\n### Describe the bug\n\nIn woodpecker v2.3.0, custom yaml files defined in repositories are configured in woodpecker and passed to the external configuration API. This API responds with valid woodpecker workflows based on the custom yaml, allowing this workflow to execute successfully. However, woodpecker 2.4.1 introduces linting on these configured custom yaml files, resulting in failed executions due to linting errors. This change effectively inhibits our ability to upgrade our instance to v2.4.1.\n\n### System Info\n\n```shell\nVersion which works for us\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.3.0\"}\r\n---\r\nVersion with issue\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.4.1\"}\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":3037,"color":3038},3536,"closed","Linter errors on repos dependent on external configuration API ","2024-03-22T14:16:02Z","https://github.com/woodpecker-ci/woodpecker/issues/3536",0.6902552,{"description":3076,"labels":3077,"number":3078,"owner":3026,"repository":3027,"state":3070,"title":3079,"updated_at":3080,"url":3081,"score":3082},"### Clear and concise description of the problem\n\nWhen I implemented #1073 in #1388 `*.yaml` became an accepted config format in addition to `*.yml`. But vscode, codium,... (for a non-exhaustive list see https://www.schemastore.org/json/#editors) don't yet recognize those files as woodpecker pipelines, which leads to missing schema validation in the IDE.\n\n### Suggested solution\n\nI'll do it, this FR is just here as a reference / to document it was done\r\n\r\nOpening a PR to update the pattern for woodpecker withing the catalog of schemastore (https://github.com/SchemaStore/schemastore/blob/6004a529b2b19ce0756198891ada5a79cd6b334c/src/api/json/catalog.json#L4010)\n\n### Alternative\n\n_No response_\n\n### Additional context\n\nI'm going to open the PR there, this is just to a) keep you informed and b) have a reference for the future\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 request the same feature to avoid creating a duplicate.",[],1529,"Updating schema validation in `https://www.schemastore.org/api/json/` to allow `*.yaml`","2023-01-04T19:56:33Z","https://github.com/woodpecker-ci/woodpecker/issues/1529",0.69620216,{"description":3084,"labels":3085,"number":3087,"owner":3026,"repository":3027,"state":3070,"title":3088,"updated_at":3089,"url":3090,"score":3091},"### Component\n\nserver\n\n### Describe the bug\n\n\r\n\r\nI'll try to downgrade my woodpecker version to fix this, because all PRs are now broken on `next`.\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-5bd12aa646\"}\n```\n\n\n### Additional context\n\nNA\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).",[3086],{"name":3037,"color":3038},2350,"All github PRs are reported as *Waiting for status to be reported*","2023-10-02T06:45:33Z","https://github.com/woodpecker-ci/woodpecker/issues/2350",0.7003277,{"description":3093,"labels":3094,"number":3098,"owner":3026,"repository":3027,"state":3070,"title":3099,"updated_at":3100,"url":3101,"score":3102},"This is a general roadmap for the project covering the most requested epics. They are sorted in some kind of priority (considered by maintainers), but this is not forced.\r\n\r\n> Keep in mind Woodpecker has no scheduled releases as it is a OSS project done by volunteers. \r\n\r\n# For first stable release 1.0\r\n- [x] Refactoring of drone 0.8 code\r\n - [x] Improve pipeline config format (possible breaking changes) #567\r\n - [x] Move Server Pipeline Build code into own package #949\r\n - [x] #1288\r\n - [x] #1287\r\n- [x] Support when filters on root level #283 #770 \r\n- [x] #1295 \r\n\r\n# General roadmap\r\n- [x] #1451\r\n- [ ] Add more pipeline events \r\n - [x] Cron #8 #934 \r\n - [x] Support manually triggering a pipeline #83 #240 \r\n - [ ] PR close #286\r\n - [ ] Release (type: draft, pre, stable; action: created, updated, deleted) #764 \r\n - [ ] comments (create, delete, update) / #814 \r\n - [ ] label (added, removed, issue, PR)\r\n - [ ] issues (created, updated, closed, reopened)\r\n- [ ] well known #1385 \r\n- [x] Autoscaler #999\r\n- [ ] BringYourOwnAgent #267\r\n- [ ] non root images #1077\r\n- [ ] pipeline compile step #1400 #53\r\n- [ ] enhance plugins so they can **easily** be used for caching #767\r\n- [ ] multiple forges #138\r\n- [ ] UI configured forges #425\r\n- [ ] Admin panel #345\r\n- [ ] UI plugins which can be used by plugins #1006\r\n- [ ] Add support for HA setup #742 \r\n- [x] Decide to use Swagger docs or Graphql #292 #994 \r\n- [ ] #84\r\n- [ ] repo extensions (external secrets, registries, config compilers) #915 \r\n- [ ] deprecation warnings #276 #922",[3095],{"name":3096,"color":3097},"summary","C3DC73",869,"Roadmap","2023-08-08T11:39:30Z","https://github.com/woodpecker-ci/woodpecker/issues/869",0.70601296,{"description":3104,"labels":3105,"number":3109,"owner":3026,"repository":3027,"state":3070,"title":3110,"updated_at":3111,"url":3112,"score":3113},"# 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",[3106],{"name":3107,"color":3108},"governance","A46EFE",4320,"Release plan for v3.0.0","2025-01-18T23:31:56Z","https://github.com/woodpecker-ci/woodpecker/issues/4320",0.7078808,{"description":3115,"labels":3116,"number":3121,"owner":3026,"repository":3027,"state":3070,"title":3122,"updated_at":3123,"url":3124,"score":3125},"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)",[3117,3120],{"name":3118,"color":3119},"feature","180DBE",{"name":3023,"color":3024},1400,"RFC: pipeline compile step","2023-08-20T15:57:51Z","https://github.com/woodpecker-ci/woodpecker/issues/1400",0.7128223,["Reactive",3127],{},["Set"],["ShallowReactive",3130],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fY1e5HbpsRZ_e_s72xo-cGdfXsbTzwf8UoO2lOlJo6gs":-1},"/woodpecker-ci/woodpecker/3873"]