\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]",[3053],{"name":3034,"color":3035},5338,"Build status not completing on matrix pipelines with BitBucket","2025-07-17T18:03:12Z","https://github.com/woodpecker-ci/woodpecker/issues/5338",0.7505574,{"description":3060,"labels":3061,"number":3066,"owner":3023,"repository":3024,"state":3025,"title":3067,"updated_at":3068,"url":3069,"score":3070},"### 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).",[3062,3063],{"name":3034,"color":3035},{"name":3064,"color":3065},"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.7568802,{"description":3072,"labels":3073,"number":3075,"owner":3023,"repository":3024,"state":3076,"title":3077,"updated_at":3078,"url":3079,"score":3080},"### Component\r\n\r\nagent\r\n\r\n### Describe the bug\r\n\r\nThe Woodpecker agent registers itself as running on `linux/aarch64`\r\n\r\n```json\r\n{\r\n\"message\":\"starting Woodpecker agent with version 'next-0b34578923' and backend 'docker' using platform 'linux/aarch64' running up to 1 pipelines in parallel\"\r\n}\r\n```\r\n\r\nand does not work when using the platform `linux/arm64` in workflows.\r\n\r\n### Steps to reproduce\r\n\r\n1. Compile Woodpecker agent from the current main branch on AARCH64\r\n2. Install and configure the agent\r\n3. Setup a workflow which uses `linux/arm64` as `platform`.\r\n4. Observe, that `linux/aarch64` is not regarded the same as `linux/arm64` by Woodpecker.\r\n\r\n### Expected behavior\r\n\r\nWoodpecker recognizes `arm64` and `aarch64` as synonyms for the same CPU ISA or uses one of these consistently - the agent sets `linux/arm64` on AARCH64.\r\n\r\n### System Info\r\n\r\n```shell\r\nLinux debian 6.1.0-23-arm64 #1 SMP Debian 6.1.99-1 (2024-07-15) aarch64 GNU/Linux\r\n```\r\n\r\n```json\r\n{\r\n \"source\": \"https://github.com/woodpecker-ci/woodpecker\",\r\n \"version\": \"next-0b34578923\"\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]",[3074],{"name":3034,"color":3035},4051,"closed","ISA: aarch64 vs arm64","2024-11-25T15:17:59Z","https://github.com/woodpecker-ci/woodpecker/issues/4051",0.72505695,{"description":3082,"labels":3083,"number":3085,"owner":3023,"repository":3024,"state":3076,"title":3086,"updated_at":3087,"url":3088,"score":3089},"### Component\r\n\r\nagent\r\n\r\n### Describe the bug\r\n\r\nWhen providing key-pairs for --filter, these are not being used by the agent.\r\n\r\nTo replicate:\r\n\r\nStart an agent with a filter of key-value pair:\r\n\r\n```sh\r\n./woodpecker-agent --grpc-password secret --backend-engine local --filter type=exec\r\n```\r\n\r\nAdd label to pipeline yaml:\r\n\r\n```yaml\r\nlabels:\r\n type: exec\r\n```\r\n\r\nExpected:\r\n\r\nagent will run the tack\r\n\r\nExperienced:\r\n\r\nagent does not pick up the task.\r\n\r\nIssue seems to be in `cmd/agent/agent.go`: `for _, v := range c.StringSlice(\"filter-labels\") {` as per my PR.\r\n\r\n\r\n\r\n\r\n### System Info\r\n\r\n```shell\r\n7a4827bb\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).\r\n\r\nEdit: fix yaml formatting",[3084],{"name":3034,"color":3035},1102,"woodpecker-agent not accepting --filter arguments","2022-10-11T16:22:50Z","https://github.com/woodpecker-ci/woodpecker/issues/1102",0.7307207,{"description":3091,"labels":3092,"number":3094,"owner":3023,"repository":3024,"state":3076,"title":3095,"updated_at":3096,"url":3097,"score":3098},"### Component\n\nserver\n\n### Describe the bug\n\nOne cannot use a filtered step in the depends_on clause. If you try it, the linter rejects the configuration\r\n\r\n\r\nThis prohibits the combination of parallel steps and optional steps in the same pipeline.\r\n\r\nMinimal reproducer:\r\n```\r\nsteps:\r\n - name: filtered\r\n image: alpine\r\n commands:\r\n - echo \"step 1\"\r\n when:\r\n branch:\r\n - xyz\r\n\r\n - name: unconditional\r\n image: alpine\r\n commands:\r\n - echo \"step 2\"\r\n depends_on:\r\n - filtered\r\n```\n\n### System Info\n\n```shell\nVersion 2.2.2\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":3034,"color":3035},3278,"Filtered steps and depends_on (step)","2024-01-25T17:22:40Z","https://github.com/woodpecker-ci/woodpecker/issues/3278",0.73240376,{"description":3100,"labels":3101,"number":3103,"owner":3023,"repository":3024,"state":3076,"title":3104,"updated_at":3105,"url":3106,"score":3107},"### Component\n\ncli\n\n### Describe the bug\n\nAdding a \"platform\" as suggested in the documentation at https://woodpecker-ci.org/docs/usage/matrix-pipelines#example-matrix-pipeline-using-multiple-platforms throws an\r\n```\r\n❌ Config is invalid\r\nIn (root): Additional property platform is not allowed\r\n```\r\nin `woodpecker lint`.\n\n### System Info\n\n```shell\nwoodpecker-cli version 0.15\r\n\r\nThis is the amd64 Debian package from GitHub releases.\n```\n\n\n### Additional context\n\n```shell\nThe specific section in my file looks like this:\r\n\r\nmatrix:\r\n PLATFORM:\r\n - 'linux/amd64'\r\n - 'linux/arm64'\r\n\r\nplatform: ${PLATFORM}\r\n\r\npipeline:\r\n setup_environment:\r\n(...)\r\n```\n```\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] 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).",[3102],{"name":3034,"color":3035},1056,"\"Additional property platform is not allowed\"","2022-10-11T16:26:56Z","https://github.com/woodpecker-ci/woodpecker/issues/1056",0.73721814,{"description":3109,"labels":3110,"number":3112,"owner":3023,"repository":3024,"state":3076,"title":3113,"updated_at":3114,"url":3115,"score":3116},"### Component\n\nagent\n\n### Describe the bug\n\nWhen running a local pipeline step, `echo $HOME` shows nothing.\r\n\r\nI have a tool (`nix` in this instance) which needs to write to `HOME`, and therefore fails if it is unset as it tries to write to `/`.\r\n\r\nDoing `HOME=$(mktemp -d) my command here...` however, works.\r\n\r\nI think `HOME` should be set to a sensible value: either the `PWD` (i.e: the CI workspace) or a temporary directory (as-if created by `mktemp -d`).\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-e7ca2802\"}\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).",[3111],{"name":3034,"color":3035},1685,"HOME unset in local pipeline step","2023-04-02T14:47:24Z","https://github.com/woodpecker-ci/woodpecker/issues/1685",0.7404779,["Reactive",3118],{},["Set"],["ShallowReactive",3121],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fuYJkc21GNCIScqCqi7Tj1juXn8wrYFov-upAnGqeUi0":-1},"/woodpecker-ci/woodpecker/5368"]