\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]",[3198,3199],{"name":3160,"color":3161},{"name":3200,"color":3201},"forge/bitbucket","E96280",5338,"Build status not completing on matrix pipelines with BitBucket","2025-08-10T17:51:17Z","https://github.com/woodpecker-ci/woodpecker/issues/5338",0.7100131,{"description":3208,"labels":3209,"number":3211,"owner":3149,"repository":3150,"state":3190,"title":3212,"updated_at":3213,"url":3214,"score":3215},"### Component\n\nagent\n\n### Describe the bug\n\nHi team\r\nAs I have deployed Woodpecker agent next version in kubernetes wanted to test few builds by scheduling on this agent and restricting all other builds so do we have any feature to restrict particular agent so that no builds get scheduled except the builds matching agent label? If possible do we have any documentation/reference?\n\n### System Info\n\n```shell\nVersion info {\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-f6811a20\"}\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).",[3210],{"name":3160,"color":3161},1684,"Restrict Particular Agent(K8s) ","2023-04-03T13:38:11Z","https://github.com/woodpecker-ci/woodpecker/issues/1684",0.7177601,{"description":3217,"labels":3218,"number":3220,"owner":3149,"repository":3150,"state":3190,"title":3221,"updated_at":3222,"url":3223,"score":3224},"### Component\n\nagent\n\n### Describe the bug\n\nWhen setting `platform: \u003Cany arch>` with the Kubernetes backend, the resulting jobs are not placed on the respective nodes.\r\n\r\nFor this to happen the platform arch must most likely be translated into a `nodeSelector` for the upcoming pod but this field is not set.\r\n\r\nWhen running a mixed-arch cluster, this makes WP practically unusable :(\n\n### System Info\n\n```shell\nk8s 1.26\r\n\r\nVersion: `next-049c2622`\n```\n\n\n### Additional context\n\nrelated to #platform\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).",[3219],{"name":3160,"color":3161},1736,"Kubernetes: `platform` does not guarantee correct scheduling","2023-05-18T09:21:22Z","https://github.com/woodpecker-ci/woodpecker/issues/1736",0.71854216,{"description":3226,"labels":3227,"number":3229,"owner":3149,"repository":3150,"state":3190,"title":3230,"updated_at":3231,"url":3232,"score":3233},"### 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).",[3228],{"name":3160,"color":3161},1056,"\"Additional property platform is not allowed\"","2022-10-11T16:26:56Z","https://github.com/woodpecker-ci/woodpecker/issues/1056",0.72078055,{"description":3235,"labels":3236,"number":3238,"owner":3149,"repository":3150,"state":3190,"title":3239,"updated_at":3240,"url":3241,"score":3242},"### Component\n\nagent\n\n### Describe the bug\n\nRecently, I am seeing builds being assigned to the wrong nodes on our cluster. \r\nInspecting the pods, I can see that the `platform` env, which comes from the matrix definition, is set to `amd64`. However, the nodeSelector is set to `arm64` instead.\r\n\r\n```\r\nEnvironment:\r\n platform: linux/amd64 \r\n\r\n[...]\r\n\r\nNode-Selectors: kubernetes.io/arch=arm64 \r\n```\r\n\r\nThe WF definition is as follows\r\n\r\n```\r\nplatform: ${platform}\r\n\r\nmatrix:\r\n include:\r\n - DISTRIBUTION: ubuntu\r\n RELEASE: focal\r\n OS_RELEASE: 20.04\r\n platform: linux/amd64\r\n - DISTRIBUTION: ubuntu\r\n RELEASE: jammy\r\n OS_RELEASE: 22.04\r\n platform: linux/amd64\r\n - DISTRIBUTION: redhat/ubi8-minimal\r\n RELEASE: latest\r\n platform: linux/amd64\r\n OS_RELEASE: rhel8\r\n - DISTRIBUTION: redhat/ubi9-minimal\r\n RELEASE: latest\r\n platform: linux/amd64\r\n OS_RELEASE: rhel9\r\n```\r\n\r\nCould it be that https://github.com/woodpecker-ci/woodpecker/pull/2048 changed the logic in a way that `nodeSelector` is always set to `CI_SYSTEM_PLATFORM` and does not honor `platform` env anymore?\r\n\r\nhttps://github.com/woodpecker-ci/woodpecker/blob/0eacbe8a33823b75e1ecdd738f6c0cad00bd7d68/pipeline/backend/kubernetes/pod.go#L112\r\n\r\nOr maybe one of the changes within the recent months caused this behavior?\r\nTagging @6543 and @zc-devs as you both did modifications in this area lately.\r\n\r\nI am not having enough experience in GO to make an educated judgement right now - all I can see is that `CI_SYSTEM_PLATFORM` is not honoring `platform` env and therefore the `nodeSelector` is wrong in the end :)\n\n### System Info\n\n```shell\n`next-f8e91f00aa`\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).",[3237],{"name":3160,"color":3161},2505,"Node Selector assigns wrong architecture for builds","2023-10-18T16:08:30Z","https://github.com/woodpecker-ci/woodpecker/issues/2505",0.72355163,["Reactive",3244],{},["Set"],["ShallowReactive",3247],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fdxuy_VvwF2zceKMPG_r0TdctlSfWk7yP-yj9rf712Qs":-1},"/woodpecker-ci/woodpecker/1059"]