\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]",[3034],{"name":3021,"color":3022},5338,"Build status not completing on matrix pipelines with BitBucket","2025-07-17T18:03:12Z","https://github.com/woodpecker-ci/woodpecker/issues/5338",0.73836285,{"description":3041,"labels":3042,"number":3049,"owner":3024,"repository":3025,"state":3026,"title":3050,"updated_at":3051,"url":3052,"score":3053},"### Clear and concise description of the problem\n\nRight now, there only seems to be a way to define global env variables for the entire CI, rather than a single pipeline itself.\r\nIn addition is this from what I understand only something an admin can do, meaning users on a shared instance may not have a way to easily define an environment that is accessible across all steps (See \"Alternatives\" for the ones I know of and their (mostly) cons).\n\n### Suggested solution\n\nA global `environment` option should be implemented, which allows you to define the environment variables you want to use across all steps.\r\n\r\nI'm unsure if this global one should be overridable by a step-level environment setting with the same name.\r\n\r\nExample:\r\n```yaml\r\nwhen:\r\n - event: push\r\n\r\nenvironment:\r\n FOO: BAR # Set a global env here.\r\n\r\nsteps:\r\n - name: 'echo'\r\n image: bash\r\n commands:\r\n - echo ${FOO}\r\n - name: 'echo again'\r\n image: bash\r\n environment:\r\n FOO: NOT_BAR # Should this be possible?\r\n commands:\r\n - echo ${FOO}\r\n```\n\n### Alternative\n\nFrom what I understand and gathered are there these possible alternatives, which all have some downsides to them:\r\n\r\n- Set a secret.\r\n - `-` Using a secret for sharing a non-secret value globally seems wrong.\r\n - `-` doesn't allow using other env variables to be processed(? Unsure about this one).\r\n - `+` It's available across all steps and can also be used in plugin settings.\r\n- Create a step that saves a value to an envvars file and then later get it.\r\n - `-` Depending on the image set may require different commands to set and get.\r\n - `-` You can't pull the env in a plugin (unless there is an aproach to run commands before the image execution somehow).\r\n - `-` Requires to pull the envvars file on every step to make it available.\r\n - `+` Above negative allows only exposing the env to specific steps.\n\n### Additional context\n\n_No response_\n\n### Validations\n\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]\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.",[3043,3046],{"name":3044,"color":3045},"enhancement","7E1FE4",{"name":3047,"color":3048},"pipeline-config","1BE540",3661,"Global `environment` option to set env variables across all steps","2024-11-20T15:37:31Z","https://github.com/woodpecker-ci/woodpecker/issues/3661",0.76683587,{"description":3055,"labels":3056,"number":3058,"owner":3024,"repository":3025,"state":3026,"title":3059,"updated_at":3060,"url":3061,"score":3062},"",[3057],{"name":3021,"color":3022},3333,"Pipeline missing a secret should report failed status back","2024-12-08T12:11:00Z","https://github.com/woodpecker-ci/woodpecker/issues/3333",0.7732367,{"description":3064,"labels":3065,"number":3067,"owner":3024,"repository":3025,"state":3026,"title":3068,"updated_at":3069,"url":3070,"score":3071},"### Component\n\nserver\n\n### Describe the bug\n\nI have a .woodpecker directory, with at least 15 workflows to parallelize docker image builds. Any of those pipelines that fail, increment the failed jobs counter, as one would expect. The jobs that pass however, do not, and the success metric is only incremented if *ALL* of the jobs pass. It's kind of a \"everything counts against you, but only total success counts towards you\" sort of thing.\n\n### System Info\n\n```shell\nversion\t\"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).",[3066],{"name":3044,"color":3045},2512,"success / fail metrics are unbalanced","2023-10-23T13:01:03Z","https://github.com/woodpecker-ci/woodpecker/issues/2512",0.7777222,{"description":3073,"labels":3074,"number":3079,"owner":3024,"repository":3025,"state":3026,"title":3080,"updated_at":3081,"url":3082,"score":3083},"### Component\r\n\r\nweb-ui\r\n\r\n### Describe the bug\r\n\r\nRunning pipeline with a service, it doesn't change its status and logs are empty unless page are reloaded.\r\n\r\nPipeline:\r\n```yaml\r\nservices:\r\n database:\r\n image: mysql\r\n environment:\r\n - MYSQL_DATABASE=test\r\n - MYSQL_ROOT_PASSWORD=example\r\n ports:\r\n - 3306\r\nsteps:\r\n get-version:\r\n image: ubuntu\r\n commands:\r\n - ( apt update && apt dist-upgrade -y && apt install -y mysql-client 2>&1 )> /dev/null\r\n - sleep 60s # need to wait for mysql-server init\r\n - echo 'SHOW VARIABLES LIKE \"version\"' | mysql -uroot -hdatabase test -pexample\r\n```\r\n\r\nStart pipeline and click on the service step - logs exist:\r\n\r\n\r\nThen switch to the general step and wait to complete - there are logs, status changes to completed, execution timer stops:\r\n\r\n\r\nSwitch back to the service - now there are no logs, step is executing forever:\r\n\r\n\r\nAfter page reloading, all displays as expected - logs, status and execution timer:\r\n\r\n\r\nThe later should be without refreshing page.\r\n\r\n\r\n### System Info\r\n\r\n```shell\r\n2.0.0-rc.0, Kubernetes\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/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 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]\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).",[3075,3076],{"name":3021,"color":3022},{"name":3077,"color":3078},"ui","46DEA2",2831,"Service step doesn't change its status","2024-01-09T21:30:54Z","https://github.com/woodpecker-ci/woodpecker/issues/2831",0.78076136,{"description":3085,"labels":3086,"number":3091,"owner":3024,"repository":3025,"state":3092,"title":3093,"updated_at":3094,"url":3095,"score":3096},"### Component\n\nserver\n\n### Describe the bug\n\nI tried to squash a pull request and after the squashed commit hadn't any pipelines. The Gitea webhook history confirmed the problem on woodpeckers side with and a 500 error code.\r\n\r\n```\r\ngitea-woodpecker-server-1 | {\"time\":\"2022-09-17T16:51:11Z\",\"message\":\"LogLevel = warn\"}\r\ngitea-woodpecker-server-1 | {\"level\":\"error\",\"error\":\"pq: value too long for type character varying(255)\",\"time\":\"2022-09-17T17:45:59Z\",\"message\":\"failure to save build for [domain.tld/ansible-vyos](http://domain.tld/ansible-vyos)\"}\r\ngitea-woodpecker-server-1 | {\"level\":\"error\",\"error\":\"pq: value too long for type character varying(255)\",\"time\":\"2022-09-17T17:47:14Z\",\"message\":\"failure to save build for [domain.tld/ansible-vyos](http://domain.tld/ansible-vyos)\"}\r\ngitea-woodpecker-server-1 | {\"level\":\"error\",\"error\":\"pq: value too long for type character varying(255)\",\"time\":\"2022-09-17T17:50:11Z\",\"message\":\"failure to save build for [domain.tld/ansible-vyos](http://domain.tld/ansible-vyos)\"}\r\n```\n\n### System Info\n\n```shell\n0.15.3\n```\n\n\n### Additional context\n\nI confirmed that the commit message is longer that 255 chars. I also found that some of the commits in this repo still have pending ci runs. It would be imaginable that this is also a reason for them.\r\nhttps://github.com/woodpecker-ci/woodpecker/commit/eaf05dbae84b751ee972daae97f626f7de61487d\r\n\r\nI found that git commit messages count be theoretically unlimited in size: https://stackoverflow.com/a/9733857\r\nMaybe a SQL column type of `TEXT` should be used.\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).",[3087,3088],{"name":3021,"color":3022},{"name":3089,"color":3090},"server","5D7A92",1194,"closed","Commit message to long for db column ","2022-10-12T22:47:13Z","https://github.com/woodpecker-ci/woodpecker/issues/1194",0.75291467,{"description":3098,"labels":3099,"number":3101,"owner":3024,"repository":3025,"state":3092,"title":3102,"updated_at":3103,"url":3104,"score":3105},"### Component\n\nserver\n\n### Describe the bug\n\nWhen a pipeline with multiple workflows starts a correct status is sent at first BitBucket correctly displays that build is in progress. When the build finishes however, only one build is displayed as finished but the other one is still in progress marking the whole commit as in progress(this is internal BitBucket logic). \n\nHere is a pipeline that has two workflows:\n\n\n\nAnd here is the outcome on BitBucket:\n\n\n\nI asked @langecode if he can take a look and we realized that there is a problem in BitBucket forge implementation of `Status` function. It looks like that for each call of `Status` function we send a status of the whole pipeline when we should've sent a status of individual workflows. I.e. change status of https://github.com/woodpecker-ci/woodpecker/blob/main/server/forge/bitbucketdatacenter/bitbucketdatacenter.go#L314\n\nTo:\n```go\nState: convertStatus(workflow.State)\n```\n\n### Steps to reproduce\n\n1. Run woodpecker with BitBucket Datacenter forge\n2. Create a pipeline that has multiple workflows\n3. Let the pipeline finish on woodpecker\n4. Observe the build statuses on the commit in BitBucket\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\nWoodpecker version: v3.5.2\nBitBucket Datacenter version: v8.18.1\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]",[3100],{"name":3021,"color":3022},5177,"Statuses get incorrectly reported for multi workflow pipelines on BitBucket","2025-05-19T11:01:04Z","https://github.com/woodpecker-ci/woodpecker/issues/5177",0.7582023,{"description":3107,"labels":3108,"number":3111,"owner":3024,"repository":3025,"state":3092,"title":3112,"updated_at":3113,"url":3114,"score":3115},"if the pipeline fails because of an external issue like:\r\n\r\nhttps://ci.woodpecker-ci.org/repos/3780/pipeline/11472\r\n\r\nthe restarted pipeline do not find the pipeline config:\r\n\r\nhttps://ci.woodpecker-ci.org/repos/3780/pipeline/11475/errors\r\n\r\nI would expect that the pipeline restart with the old config and try to fetch external things like e.g. secrets again",[3109,3110],{"name":3021,"color":3022},{"name":3089,"color":3090},3107,"Can not restart failed pipelines","2024-01-03T11:56:52Z","https://github.com/woodpecker-ci/woodpecker/issues/3107",0.75947595,{"description":3117,"labels":3118,"number":3120,"owner":3024,"repository":3025,"state":3092,"title":3121,"updated_at":3122,"url":3123,"score":3124},"### 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).",[3119],{"name":3021,"color":3022},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.7651902,["Reactive",3126],{},["Set"],["ShallowReactive",3129],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f_CqldTJa9MAL7x3JxB5taxVT3w9midtb7NP2nTrUbac":-1},"/woodpecker-ci/woodpecker/705"]