\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]",[3055],{"name":3036,"color":3037},5338,"Build status not completing on matrix pipelines with BitBucket","2025-07-17T18:03:12Z","https://github.com/woodpecker-ci/woodpecker/issues/5338",0.7239352,{"description":3062,"labels":3063,"number":3066,"owner":3025,"repository":3026,"state":3027,"title":3067,"updated_at":3068,"url":3069,"score":3070},"### Clear and concise description of the problem\r\n\r\nSince #2695 the build status of matrix pipelines gets correctly reported, what is awesome. However, there is still room for improvement. Currently it gets reported as `{name}/{number}`. It would be better if a name would be used instead of a number.\r\n\r\n### Suggested solution\r\n\r\nAdd a new filed `matrixname` which allows setting the name for a matrix pipeline. With the [example from the documentation](https://woodpecker-ci.org/docs/usage/matrix-workflows) it could look like this:\r\n```yaml\r\nmatrix:\r\n GO_VERSION:\r\n - 1.4\r\n - 1.3\r\n DATABASE:\r\n - mysql:5.5\r\n - mysql:6.5\r\n - mariadb:10.1\r\n\r\nsteps:\r\n build:\r\n image: golang:${GO_VERSION}\r\n commands:\r\n - go get\r\n - go build\r\n - go test\r\n\r\nservices:\r\n database:\r\n image: ${DATABASE}\r\n\r\nmatrixname: ${GO_VERSION}-${DATABASE}\r\n```\r\nThis would be reported as e.g. `{name}/1.4-mysql:5.5`.\r\n\r\n### Alternative\r\n\r\nIf only one variable is used, we can also use the variable instead of the number.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Validations\r\n\r\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]\r\n- [X] Read the [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/main/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 request the same feature to avoid creating a duplicate.",[3064,3065],{"name":3019,"color":3020},{"name":3022,"color":3023},2819,"Allow setting name for matrix pipelines","2023-11-20T19:47:37Z","https://github.com/woodpecker-ci/woodpecker/issues/2819",0.7305636,{"description":3072,"labels":3073,"number":3075,"owner":3025,"repository":3026,"state":3076,"title":3077,"updated_at":3078,"url":3079,"score":3080},"### Component\r\n\r\nserver, agent, web-ui\r\n\r\n### Describe the bug\r\n\r\nI have a very simple pipeline:\r\n\r\n```yaml\r\npipeline:\r\n validate:\r\n commands:\r\n - docker-compose config --quiet\r\n environment:\r\n GROUP_ID: 1000\r\n USER_ID: 1000\r\n group: verify\r\n image: docker.io/docker/compose:alpine-1.29.2\r\n```\r\n\r\nThis configuration prevents `Woodpecker CI` to trigger the pipeline.\r\n\r\nThe fix is to enclose the values from `environment` in double quotes.\r\n\r\n> The pipeline just tests that the `Docker Compose` manifest/definition file is correct, so any valid `docker-compose.yaml` file can be used to test this.\r\n\r\n### System Info\r\n\r\n```shell\r\nCodeberg's Woodpecker CI\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nI usually test all the steps that `Woodpecker CI` will execute locally using a multi-stage `Dockerfile`. I understand that while it's not exactly the same (for all purposes), it does work (for me) for almost 95% of the cases.\r\n\r\nSo I execute this in my local PC using `Docker Compose` and it doesn't fail — either using the integers or double quoted values. That's why I'm inclined to think it could be an issue with `Woodpecker CI` and not the `docker.io/docker/compose:alpine-1.29.2` image itself.\r\n\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).",[3074],{"name":3036,"color":3037},1041,"closed","Certain environment variables (and their values) prevent pipelines to be triggered","2023-06-04T11:57:59Z","https://github.com/woodpecker-ci/woodpecker/issues/1041",0.69500464,{"description":3082,"labels":3083,"number":3087,"owner":3025,"repository":3026,"state":3076,"title":3088,"updated_at":3089,"url":3090,"score":3091},"### Component\n\nserver\n\n### Describe the bug\n\nWhen I use this pipeline script:\n```\nwhen:\n - event: manual\n - branch: main\n - evaluate: 'PIPELINE == \"SANDBOXES\" || PIPELINE == \"ALL\"'\nsteps:\n - name: build\n image: node:22\n commands:\n - npm install\n - npm run build:sandbox-starter\n environment:\n INFISTICAL_CLIENT_ID:\n from_secret: emp_helper_client_id\n INFISTICAL_CLIENT_SECRET:\n from_secret: emp_helper_client_secret\n INFISTICAL_PROJECT_ID:\n from_secret: emp_helper_project_id\n INFISTICAL_URL:\n from_secret: INFISTICAL_URL\n - name: run\n image: mcr.microsoft.com/playwright:v1.52.0-noble\n commands:\n - node dist/apps/sandbox-starter/main.js\n environment:\n NX_TUI: false\n - name: send telegram finished notification\n image: curlimages/curl\n commands:\n - \"curl -X GET https://n8n.example.com/webhook/telegram-emp-helper-success\"\n when:\n status: success\n - name: send telegram failed notification\n image: curlimages/curl\n commands:\n - \"curl -X GET https://n8n.example.com/webhook/telegram-emp-helper-failed\"\n when:\n status: failure\n```\n\nit even succeeds when no PIPELINE variable is set in which case I would think it should stop.\n\n### Steps to reproduce\n\n1. Install Woodpecker Server\n2. Create a Repository and connect to it\n3. Write a pipeline script with a when and evaluate block like the one in the script above.\n4. See that even when the variable is not set the pipeline gets executed\n\n### Expected behavior\n\nPipeline should only succeed when PIPELINE is SANDBOXES for example or ALL. But not when unset.\n\n### System Info\n\n```shell\n\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"3.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]",[3084],{"name":3085,"color":3086},"question","d876e3",5334,"When using evaluate, the sent Variable is not used correctly","2025-07-25T05:31:41Z","https://github.com/woodpecker-ci/woodpecker/issues/5334",0.702421,{"description":3093,"labels":3094,"number":3096,"owner":3025,"repository":3026,"state":3076,"title":3097,"updated_at":3098,"url":3099,"score":3100},"### Clear and concise description of the problem\n\nI'm used (from `GitLab CI`) to be able to provide some some references in filters; for instance:\r\n\r\n```yaml\r\ndefault:\r\n image: docker.io/docker/compose:alpine-1.29.2\r\n\r\nstages:\r\n - verify\r\n\r\nvalidate:\r\n stage: verify\r\n rules:\r\n - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH\r\n - if: $CI_MERGE_REQUEST_ID\r\n script:\r\n - docker-compose config --quiet\r\n```\r\n\r\nWhile the filters in `Woodpecker CI` are slightly different, they achieve (almost) the same results, so it would be great to be able to use environment variables in these as well.\r\n\r\n```yaml\r\npipeline:\r\n validate:\r\n commands:\r\n - docker-compose config --quiet\r\n group: verify\r\n image: docker.io/docker/compose:alpine-1.29.2\r\n when:\r\n branch: ${CI_REPO_DEFAULT_BRANCH}\r\n```\r\n\n\n### Suggested solution\n\nJust to be able to refer to environment variables in filters — expanded by default :wink:\n\n### Alternative\n\nN/A\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 request the same feature to avoid creating a duplicate.",[3095],{"name":3022,"color":3023},963,"Allow the usage of environment variables in filters","2022-10-05T23:49:26Z","https://github.com/woodpecker-ci/woodpecker/issues/963",0.7109811,{"description":3102,"labels":3103,"number":3107,"owner":3025,"repository":3026,"state":3076,"title":3108,"updated_at":3109,"url":3110,"score":3111},"### Clear and concise description of the problem\n\nMany projects use some .env (or .dev.env, .prod.env, etc) files for managing variables.\r\nIt would be nice if woodpecker would support importing these variables directly into steps.\n\n### Suggested solution\n\nProposed syntax (same as docker compose)\r\n```yaml\r\n\r\npipeline:\r\n some_step:\r\n image: some-image\r\n commands:\r\n - do something\r\n env_file: .env\r\n\r\n some_plugin_step:\r\n image: my-build-plugin\r\n settings:\r\n foo: bar\r\n env_file:\r\n - .build.env\r\n - .env\r\n```\n\n### Alternative\n\n_No response_\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 request the same feature to avoid creating a duplicate.",[3104],{"name":3105,"color":3106},"feedback","4B7070",1348,"Add support to import env file in pipeline steps","2022-10-27T13:26:05Z","https://github.com/woodpecker-ci/woodpecker/issues/1348",0.715484,{"description":3113,"labels":3114,"number":3116,"owner":3025,"repository":3026,"state":3076,"title":3117,"updated_at":3118,"url":3119,"score":3120},"### 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).",[3115],{"name":3036,"color":3037},1685,"HOME unset in local pipeline step","2023-04-02T14:47:24Z","https://github.com/woodpecker-ci/woodpecker/issues/1685",0.71693724,["Reactive",3122],{},["Set"],["ShallowReactive",3125],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fz26QgIRD41FYGUekU2X-q5w3kwyGhJIABc2CPBlpW18":-1},"/woodpecker-ci/woodpecker/3436"]