\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]",[3043],{"name":3033,"color":3034},5338,"Build status not completing on matrix pipelines with BitBucket","2025-07-17T18:03:12Z","https://github.com/woodpecker-ci/woodpecker/issues/5338",0.6985354,{"description":3050,"labels":3051,"number":3053,"owner":3022,"repository":3023,"state":3054,"title":3055,"updated_at":3056,"url":3057,"score":3058},"### 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).",[3052],{"name":3033,"color":3034},1615,"closed"," 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.63505363,{"description":3060,"labels":3061,"number":3068,"owner":3022,"repository":3023,"state":3054,"title":3069,"updated_at":3070,"url":3071,"score":3072},"### Clear and concise description of the problem\r\n\r\nThere currently is no support for `woodpecker-cli` to run multiple pipeline files as the agent is able to do.\r\n\r\n### Suggested solution\r\n\r\nRunning `woodpecker-cli exec ./.woodpecker/` should detect that the path is a folder and run all pipelines as the agent would do.\r\nSomehow similar to how `woodpecker-cli lint` works.\r\n\r\n### Alternative\r\n\r\n_No response_\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Validations\r\n\r\n- [X] Read the [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/master/CONTRIBUTING.md).\r\n- [X] Read the [docs](https://woodpecker-ci.github.io/docs/intro).\r\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.",[3062,3065],{"name":3063,"color":3064},"feature","180DBE",{"name":3066,"color":3067},"cli","1d76db",443,"support multi-pipeline with cli exec","2021-12-13T18:51:54Z","https://github.com/woodpecker-ci/woodpecker/issues/443",0.6586787,{"description":3074,"labels":3075,"number":3081,"owner":3022,"repository":3023,"state":3054,"title":3082,"updated_at":3083,"url":3084,"score":3085},"### Component\n\ncli\n\n### Describe the bug\n\n`woodpecker-cli pipeline logs` is hardly usable and does not comply to the docs.\r\n\r\nThe help text is:\r\n```txt\r\n$ woodpecker-cli pipeline logs help\r\nNAME:\r\n woodpecker-cli pipeline logs - show pipeline logs\r\n\r\nUSAGE:\r\n woodpecker-cli pipeline logs [command options]\u003Crepo-id|repo-full-name> [pipeline] [stepID]\r\n\r\nOPTIONS:\r\n --help, -h show help\r\n```\r\n\r\nstating that `pipeline` and `stedID` are optional, but they are not and there is no hint of how to get the `stepId`\r\n\r\n\r\nI do not know, if this classifies as a bug or feature request\n\n### Steps to reproduce\n\n`165` is the id of one of our repos, 21945 is a pipeline. To reproduce change against the ids of one of your repos / pipelines.\r\n\r\n\r\nOnly with repo:\r\n```bash\r\n$ woodpecker-cli pipeline logs 165\r\n12:01PM FTL error running cli error=\"strconv.ParseInt: parsing \\\"\\\": invalid syntax\"\r\n```\r\n\r\nWith repo and pipeline:\r\n```bash\r\n$ woodpecker-cli pipeline logs 165 21945\r\n12:02PM FTL error running cli error=\"strconv.ParseInt: parsing \\\"\\\": invalid syntax\"\r\n```\r\n\r\nSo let's try it with a step:\r\n\r\n```txt\r\n$ woodpecker-cli pipeline logs 165 21945 1\r\n12:41PM FTL error running cli error=\"client error 404: \"\r\n$ woodpecker-cli pipeline logs 165 21945 2\r\n12:41PM FTL error running cli error=\"client error 400: \"\r\n```\r\n\r\nNote: Two different error codes (404 i can understand, 400 not)\r\n\r\nThe cli doesn't give a clue too:\r\n\r\n```txt\r\n$ woodpecker-cli pipeline ps 165 21945\r\nStep #2\r\nStep: clone\r\nState: success\r\n\r\nStep #3\r\nStep: wartung-weekly\r\nState: failure\r\n\r\nStep #4\r\nStep: Send E-Mail\r\nState: success\r\n``` \r\n\r\nWhat actually works is:\r\n\r\n```bash\r\n$ woodpecker-cli pipeline logs 165 21945 158434\r\n```\r\n\r\nThe `stepID` I got from the browser network window.\r\n\n\n### Expected behavior\n\nI would expect that:\r\n\r\n- parse errors indicate, what went wrong\r\n- `pipeline` is not optional as there is no god default behavior and you can find out about them using `pipeline ls`\r\n- `stepID` is not mandatory. If omitted, you get the complete log of the pipeline\r\n- Error codes are equal for invalid stepID.\r\n- There is a human friendly way of getting the `stepID` maybe added to `pipeline ps` or\r\n or a human friendly way of specifying the `stepID`\r\n\r\nBonus:\r\n- Have a way to get the logs of a single workflow\n\n### System Info\n\n```shell\ncli-version 2.6.0\n```\n\n\n### Additional context\n\nMay be related to #1824\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]",[3076,3077,3078],{"name":3033,"color":3034},{"name":3066,"color":3067},{"name":3079,"color":3080},"ux","fef2c0",3911,"woodpecker-cli pipeline logs hardly usabe","2024-07-18T18:39:20Z","https://github.com/woodpecker-ci/woodpecker/issues/3911",0.67163795,{"description":3087,"labels":3088,"number":3089,"owner":3022,"repository":3023,"state":3054,"title":3090,"updated_at":3091,"url":3092,"score":3093},"### Component\n\ncli\n\n### Describe the bug\n\ndocumentation is a bit spares so it's hard to tell what the expected behavior here is but I'm in a situation where one repo has never had a job run against it, and the `woodpecker-cli build start` won't run without providing a `build #`\r\n\r\n```\r\n$ woodpecker-cli build start --help\r\n10:52AM ??? github.com/woodpecker-ci/woodpecker/cli/common/zerologger.go:20 > LogLevel = trace\r\nNAME:\r\n woodpecker-cli build start - start a build\r\n\r\nUSAGE:\r\n woodpecker-cli build start [command options] \u003Crepo/name> [build]\r\n```\r\n\r\nHere `[build]` implies the build number is optional but when ran without an error is thrown.\r\n\r\n```\r\n$ woodpecker-cli build start morgan/thatrepo\r\n10:53AM FTL github.com/woodpecker-ci/woodpecker/cmd/cli/main.go:69 > error running cli error=\"missing job number\"\r\n```\r\n\r\nBut then, if a job number is included, it 404s because no job actually exists yet.\r\n\r\n```\r\n$ woodpecker-cli build start morgan/thatrepo 0\r\n10:54AM FTL github.com/woodpecker-ci/woodpecker/cmd/cli/main.go:69 > error running cli error=\"client error 404: \"\r\n```\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"0.15.4\"}\r\n```\n```\n\n\n### Additional context\n\nnote: I did not actually complete the last validation step, discord and matrix as are both VC backed non-public forums that do not hold user interest in their operational priorities.\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).",[],1215,"cannot launch first job with CLI / woodpecker-cli build start requires job build #","2022-10-11T16:20:13Z","https://github.com/woodpecker-ci/woodpecker/issues/1215",0.67419785,{"description":3095,"labels":3096,"number":3098,"owner":3022,"repository":3023,"state":3054,"title":3099,"updated_at":3100,"url":3101,"score":3102},"The documentation front page mentions `.woodpecker.yml` as the YAML file name for configuring a pipeline.\r\n\r\n(In other places in the docs, and in this repo's README, the file name `.drone.yml` is used. That's confusing.)\r\n\r\nAssuming that `.woodpecker.yml` would be future proof, I renamed a file in one repository which was connected with a woodpecker server. But no builds were happening. Is that actually supposed to work?\r\n\r\nIn the source code I cannot find any occurrence of `.woodpecker.yml` except for `docs/docs/incex.md`.\r\n",[3097],{"name":3033,"color":3034},212,"Docs mention `.woodpecker.yml`, but does it work?","2021-05-31T11:45:56Z","https://github.com/woodpecker-ci/woodpecker/issues/212",0.67711836,{"description":3104,"labels":3105,"number":3107,"owner":3022,"repository":3023,"state":3054,"title":3108,"updated_at":3109,"url":3110,"score":3111},"### 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]",[3106],{"name":3033,"color":3034},3536,"Linter errors on repos dependent on external configuration API ","2024-03-22T14:16:02Z","https://github.com/woodpecker-ci/woodpecker/issues/3536",0.6773985,{"description":3113,"labels":3114,"number":3116,"owner":3022,"repository":3023,"state":3054,"title":3117,"updated_at":3118,"url":3119,"score":3120},"### Component\r\n\r\ncli\r\n\r\n### Describe the bug\r\n\r\nI'm just starting out with Woodpecker, having used Drone 1.x for awhile now. I wanted to test out the multi-pipeline feature and am using the go examples from woodpecker/.woodpecker. If I try to lint the files using the 0.15.3 Mac binaries I get the following error:\r\n\r\n```bash\r\n$ woodpecker-cli lint .woodpecker/test.yml\r\n10:23AM ??? ../../../../woodpecker/src/github.com/woodpecker-ci/woodpecker/cli/common/zerologger.go:20 > LogLevel = trace\r\n❌ Config is invalid\r\n10:23AM FTL ../../../../woodpecker/src/github.com/woodpecker-ci/woodpecker/cmd/cli/main.go:69 > error running cli error=\"Failed to load yml file do not support yaml node kind '16'\"\r\n```\r\n\r\nIf I remove the variables (eg. `&golang_image golang:latest`) and change the image locations from *golang_image to golang:latest it will work. \r\n\r\nDoes it work correctly from the server/agent and this is just a lint error?\r\n\r\n### System Info\r\n\r\n```json\r\n{\r\n\"source\": \"https://github.com/woodpecker-ci/woodpecker\",\r\n\"version\": \"0.15.3\"\r\n}\r\n```\r\n\r\n```bash\r\n$ uname -v\r\nDarwin Kernel Version 21.4.0: Fri Mar 18 00:45:05 PDT 2022; root:xnu-8020.101.4~15/RELEASE_X86_64\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 [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/master/CONTRIBUTING.md).\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] 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).",[3115],{"name":3033,"color":3034},1048,"lint issues with advanced YAML","2022-10-11T16:25:36Z","https://github.com/woodpecker-ci/woodpecker/issues/1048",0.6835158,["Reactive",3122],{},["Set"],["ShallowReactive",3125],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fy7Jq4ul4ZAC69NY1pU-S-FBolgOnJNOjzixn-Ej7xH8":-1},"/woodpecker-ci/woodpecker/2511"]