\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]",[3032],{"name":3019,"color":3020},5338,"Build status not completing on matrix pipelines with BitBucket","2025-07-17T18:03:12Z","https://github.com/woodpecker-ci/woodpecker/issues/5338",0.688478,{"description":3039,"labels":3040,"number":3044,"owner":3022,"repository":3023,"state":3024,"title":3045,"updated_at":3046,"url":3047,"score":3048},"### Clear and concise description of the problem\n\nAs a user of Woodpecker, I want to be able to monitor and create alerts based on the error rate and execution frequency of specific steps within my pipelines, so that I can ensure reliability in key stages such as deploy or test.\n\nCurrently, the available Prometheus metrics (e.g., woodpecker_pipeline_count, woodpecker_pending_steps, etc.) do not expose enough granularity to identify the performance or failures of individual steps. I’m particularly looking for the ability to filter by step name or label, which is essential to trigger alerts using Prometheus Alertmanager based on issues in critical steps.\n\nWe are running Woodpecker version 2.7 and facing limitations when trying to build such alerting due to this lack of visibility.\nThis feature would unlock more precise observability and alerting for teams operating at scale.\n\n### Suggested solution\n\nIn the web-ui or in the metrics endpoint (used by Prometheus), expose new metrics (or expand existing ones) that include a label for the step name.\n\nExample metric proposal:\n\n```\nwoodpecker_step_duration_seconds{pipeline=\"xyz\", repo=\"myrepo\", step=\"deploy\"} 12.3\nwoodpecker_step_failures_total{pipeline=\"xyz\", step=\"test\"} 1\n```\n\n### Alternative\n\n_No response_\n\n### Additional context\n\nI understand this could raise cardinality concerns, especially in larger installations, so maybe the feature could be optional and configurable via environment variable or config file to enable step-level metrics selectively.\n\n### Validations\n\n- [x] Checked that the feature isn't part of the `next` version already [https://woodpecker-ci.org/versions]\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.",[3041],{"name":3042,"color":3043},"feature","180DBE",5182,"Support metrics with step-level labels to enable fine-grained Prometheus alerting","2025-05-15T16:17:37Z","https://github.com/woodpecker-ci/woodpecker/issues/5182",0.71232325,{"description":3050,"labels":3051,"number":3055,"owner":3022,"repository":3023,"state":3024,"title":3056,"updated_at":3057,"url":3058,"score":3059},"### 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]",[3052],{"name":3053,"color":3054},"enhancement","7E1FE4",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.72630656,{"description":3061,"labels":3062,"number":3063,"owner":3022,"repository":3023,"state":3064,"title":3065,"updated_at":3066,"url":3067,"score":3068},"### Component\r\n\r\nagent\r\n\r\n### Describe the bug\r\n\r\nAfter some time/conditions steps start to fail with error: `Error response from daemon: Duplicate mount point: /etc/ssl/certs` and can be resolved only by restarting docker service woodpecker is running on.\r\n\r\n\r\n### System Info\r\n\r\nVersion:\r\n\r\n```json\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-fc4af44b\"}\r\n```\r\n\r\nAgent deployment:\r\n\r\n```yaml\r\n woodpecker-runner:\r\n image: woodpeckerci/woodpecker-agent:next-alpine\r\n volumes:\r\n - /var/run/docker.sock:/var/run/docker.sock\r\n - /etc/ssl/certs:/etc/ssl/certs:ro\r\n networks:\r\n - woodpecker_internal\r\n environment: \r\n - WOODPECKER_SERVER=woodpecker-server:9000\r\n - WOODPECKER_AGENT_SECRET=\u003Credacted>\r\n - WOODPECKER_MAX_PROCS=4\r\n - WOODPECKER_HOSTNAME=${HOSTNAME}\r\n - WOODPECKER_BACKEND_DOCKER_VOLUMES=/etc/ssl/certs:/etc/ssl/certs:ro,/etc/docker/certs.d:/etc/docker/certs.d:ro\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).",[],1495,"closed","Duplicate mount point step error","2023-01-31T20:33:42Z","https://github.com/woodpecker-ci/woodpecker/issues/1495",0.69846183,{"description":3070,"labels":3071,"number":3076,"owner":3022,"repository":3023,"state":3064,"title":3077,"updated_at":3078,"url":3079,"score":3080},"### Component\n\nserver\n\n### Describe the bug\n\nSometimes pipeline cancellations still result in errors that will flag the pipeline as failed instead of cancelled:\r\n\r\n\r\n\n\n### Steps to reproduce\n\nHave not found a reliable way to reproduce this specific case.\n\n### Expected behavior\n\nPipeline should be marked as cancelled instead of failed.\n\n### System Info\n\n```shell\nnext-bf5405b6cc\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]",[3072,3073],{"name":3019,"color":3020},{"name":3074,"color":3075},"ui","46DEA2",4349,"Cancelled pipelines marked as failed","2024-11-12T06:48:56Z","https://github.com/woodpecker-ci/woodpecker/issues/4349",0.7013009,{"description":3082,"labels":3083,"number":3085,"owner":3022,"repository":3023,"state":3064,"title":3086,"updated_at":3087,"url":3088,"score":3089},"### Component\n\nweb-ui\n\n### Describe the bug\n\nThe pipeline status image (on Woodpecker - returned by API: /api/badges/25/status.svg ) shows ERROR, even that last build is OK:\r\n\r\n\n\n### System Info\n\n```shell\nversion 2.4.1 running on Docker\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]",[3084],{"name":3019,"color":3020},3561,"Pipeline status is error, but last job is OK","2024-04-15T10:15:05Z","https://github.com/woodpecker-ci/woodpecker/issues/3561",0.7017587,{"description":3091,"labels":3092,"number":3094,"owner":3022,"repository":3023,"state":3064,"title":3095,"updated_at":3096,"url":3097,"score":3098},"### Component\n\nweb-ui\n\n### Describe the bug\n\nHello everyone !\r\n\r\nFirst of all, thank you for the great work you do here!\r\n\r\nWe have a problem on our Woodpecker test instance; when running steps, the logs only appear after the step is completed. During execution, the log window remains black, which can be a problem when some tasks are very long.\r\n\r\nAs a quick diagnostic:\r\n* https://host/stream/logs/org/repo/34/6 returns event=error, data=eof during the step execution\r\n\r\n```\r\n: ping\r\n\r\nevent: error\r\ndata: eof\r\n```\r\n\r\nThe woodpecker server logs:\r\n```\r\n{\"level\":\"error\",\"error\":\"stream: not found\",\"time\":\"2021-12-08T14:45:36Z\",\"message\":\"tail of logs failed\"}\r\n```\r\n\r\nit is always the case. As soon as the step is finished (failed or successful), the logs are displayed as if by magic.\r\nAny idea ?\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-03a43567\"}\n```\n\n\n### Additional context\n\n```shell\nThe woodpecker-server is on the same machine as the woodpecker-agent, both running with docker-compose.\r\n\r\nA Caddy reverse-proxy is setup in front of the woodpecker-server (reverse of localhost:8000) and the WOODPECKER_HOST variable is setup.\r\n\r\nThe build works fine, just the logs don't appear.\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).",[3093],{"name":3019,"color":3020},580,"Tail of logs failed - logs only appear after the step","2023-06-12T23:53:33Z","https://github.com/woodpecker-ci/woodpecker/issues/580",0.70617306,{"description":3100,"labels":3101,"number":3103,"owner":3022,"repository":3023,"state":3064,"title":3104,"updated_at":3105,"url":3106,"score":3107},"### 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]",[3102],{"name":3019,"color":3020},3536,"Linter errors on repos dependent on external configuration API ","2024-03-22T14:16:02Z","https://github.com/woodpecker-ci/woodpecker/issues/3536",0.7103052,{"description":3109,"labels":3110,"number":3115,"owner":3022,"repository":3023,"state":3064,"title":3116,"updated_at":3117,"url":3118,"score":3119},"### Component\r\n\r\nserver\r\n\r\n### Describe the bug\r\n\r\nconditional step event failure always triggered even when there is no error\r\n\r\n```yml\r\n when:\r\n status:\r\n - failure\r\n```\r\nis triggered even when no jobs fails\r\n\r\n### System Info\r\n\r\n```shell\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-6433dfea\"}\r\n```\r\n\r\n\r\n### Additional context\r\n\r\n\r\n\r\n\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).",[3111,3112],{"name":3019,"color":3020},{"name":3113,"color":3114},"server","5D7A92",1181,"conditional step event failure aways triggered ","2023-01-02T05:36:59Z","https://github.com/woodpecker-ci/woodpecker/issues/1181",0.71326625,["Reactive",3121],{},["Set"],["ShallowReactive",3124],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fCsZqACMYkmRIxkXkJ99Vsvu25B-Pq-SdpSb9SS5Jx1s":-1},"/woodpecker-ci/woodpecker/2512"]