\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]",[3041],{"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.7159624,{"description":3048,"labels":3049,"number":3051,"owner":3022,"repository":3023,"state":3024,"title":3052,"updated_at":3053,"url":3054,"score":3055},"### Component\r\n\r\nother\r\n\r\n### Describe the bug\r\n\r\nTrying to use steps with the same name, pipeline fails or works wrong.\r\n\r\nhttps://github.com/woodpecker-ci/woodpecker/pull/3411#issuecomment-2194567897:\r\n> be aware that steps now can have the same name\r\n\r\n\r\n### Steps to reproduce 1\r\n\r\n1. Make pipeline\r\n```yaml\r\nskip_clone: true\r\nsteps:\r\n notification:\r\n depends_on:\r\n - build\r\n image: alpine\r\n commands:\r\n - echo 'Alright'\r\n build:\r\n image: alpine\r\n commands:\r\n - echo 'Build'\r\n build:\r\n image: alpine\r\n commands:\r\n - echo 'Test'\r\n package:\r\n image: alpine\r\n commands:\r\n - echo 'Package'\r\n```\r\n2. Get error in editor\r\n\r\n3. Run pipeline\r\n4. Get error in UI\r\n\r\n\r\n⬆️ pipeline with one `build` step works well.\r\n\r\n[server-same-name-map.log](https://github.com/user-attachments/files/17784403/server-same-name-map.log.txt)\r\n[agent-same-name-map.log](https://github.com/user-attachments/files/17784389/agent-same-name-map.log.txt)\r\n\r\n\r\n### Steps to reproduce 2\r\n\r\n1. Make pipeline\r\n```yaml\r\nskip_clone: true\r\nsteps:\r\n - name: notification\r\n depends_on:\r\n - build\r\n image: alpine\r\n commands:\r\n - echo 'Alright'\r\n - name: build\r\n image: alpine\r\n commands:\r\n - echo 'Build'\r\n - name: build\r\n image: alpine\r\n commands:\r\n - echo 'Test'\r\n - name: package\r\n image: alpine\r\n commands:\r\n - echo 'Package'\r\n```\r\n2. Run pipeline\r\n3. See that the only one `build` step was run (second one with echo Test) \r\n\r\n\r\n[server-same-name-array.log](https://github.com/user-attachments/files/17784400/server-same-name-array.log.txt)\r\n[agent-same-name-array.log](https://github.com/user-attachments/files/17784390/agent-same-name-array.log.txt)\r\n\r\n\r\n### Expected behavior\r\n\r\n- pipeline fails with error like `step names must be unique`\r\n- or pipeline runs _both_ steps with the same name (`build`)\r\n\r\n### System Info\r\n\r\n```shell\r\nWoodpecker `next-75017ac7ca`, Gitea `1.22.3`, Postgres `16`, Kubernetes `v1.30.6+k3s1`\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nhttps://github.com/woodpecker-ci/woodpecker/pull/3411#issuecomment-2194567897\r\nhttps://github.com/woodpecker-ci/woodpecker/pull/3411#discussion_r1844941371\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]",[3050],{"name":3019,"color":3020},4385,"Steps with the same name","2024-11-17T14:44:50Z","https://github.com/woodpecker-ci/woodpecker/issues/4385",0.72259223,{"description":3057,"labels":3058,"number":3059,"owner":3022,"repository":3023,"state":3060,"title":3061,"updated_at":3062,"url":3063,"score":3064},"### Component\n\nserver\n\n### Describe the bug\n\nWhen a started pipeline is canceled, the pipeline status is always `Failed`\r\n\r\nIt seems that the pipeline status is always based on the the step state\r\n\r\nWhen a step is canceled, the step state reported back by the killed is always failed.\r\n\r\nThis is caused by \r\n\r\nhttps://github.com/woodpecker-ci/woodpecker/blob/1786c0554a3f347924a0a1d36c8b2684eb45ac86/agent/runner.go#L365\r\n\r\nthat is called even if cancel is set\r\n\r\nI think `Done` should just be called if cancel is not set\r\n\r\n```go\r\nif canceled.IsNotSet() {\r\n err = r.client.Done(ctxmeta, work.ID, state)\r\n}\r\n```\r\n\r\nAlso the step state has to be overwritten\r\n\r\n```go\r\nstepState := rpc.State{\r\n Step: state.Pipeline.Step.Alias,\r\n Exited: state.Process.Exited,\r\n ExitCode: state.Process.ExitCode,\r\n Started: time.Now().Unix(), // TODO do not do this\r\n Finished: time.Now().Unix(),\r\n}\r\nif canceled.IsSet() {\r\n stepState.ExitCode = 137\r\n stepState.Error = \"Step canceled\"\r\n} else if state.Process.Error != nil {\r\n stepState.Error = state.Process.Error.Error()\r\n}\r\n\r\n```\r\n\r\nsince the error reported seems to be always caused by the step getting killed\r\n\r\n\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-05d2f493\"}\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] 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).",[],1430,"closed","Wrong pipeline status on cancel","2022-11-22T08:49:51Z","https://github.com/woodpecker-ci/woodpecker/issues/1430",0.69131845,{"description":3066,"labels":3067,"number":3069,"owner":3022,"repository":3023,"state":3060,"title":3070,"updated_at":3071,"url":3072,"score":3073},"### 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]",[3068],{"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.69320077,{"description":3075,"labels":3076,"number":3081,"owner":3022,"repository":3023,"state":3060,"title":3082,"updated_at":3083,"url":3084,"score":3085},"### Component\n\nserver\n\n### Describe the bug\n\nWhen pipeline/step is canceled automatically it will result in failed state with error:\r\n```\r\nGet \"http://%2Fvar%2Frun%2Fdocker.sock/v1.41/containers/wp_0_8440940097353797125_clone_1/json\": context canceled\r\n```\r\n\r\nInstead on this error step should be set to state canceled and so is pipeline\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-ee9269d6\"}\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] 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).",[3077,3078],{"name":3019,"color":3020},{"name":3079,"color":3080},"duplicate","9D1C99",1391,"Canceled pipelines/steps should have correct status","2022-11-06T02:54:38Z","https://github.com/woodpecker-ci/woodpecker/issues/1391",0.69473433,{"description":3087,"labels":3088,"number":3093,"owner":3022,"repository":3023,"state":3060,"title":3094,"updated_at":3095,"url":3096,"score":3097},"### Component\r\n\r\nserver, agent\r\n\r\n### Describe the bug\r\n\r\nUser-1 have pipeline in repository `wp-test`, he [runs](https://woodpecker.test.smthd.com/repos/1/pipeline/139) `gitea-integration-test` branch:\r\n```yaml\r\nskip_clone: true\r\nservices:\r\n postgres:\r\n image: digitalocean/doks-debug\r\n commands:\r\n - echo 'This is Gitea Postgres test server' | nc -l -6 5432\r\n ports:\r\n - 5432\r\nsteps:\r\n gitea:\r\n image: digitalocean/doks-debug\r\n commands:\r\n - nc -v -6 -w 10 postgres 5432\r\n```\r\n\r\nUser-2 have pipeline below in his `wp-test-2` repository and `woodpecker-integration-test` branch:\r\n```yaml\r\nskip_clone: true\r\nservices:\r\n postgres:\r\n image: digitalocean/doks-debug\r\n commands:\r\n - echo 'This is Woodpecker Postgres test server' | nc -l -6 5432\r\n ports:\r\n - 5432\r\nsteps:\r\n wp:\r\n image: digitalocean/doks-debug\r\n commands:\r\n - nc -v -6 -w 10 postgres 5432\r\n```\r\nWhen User-1's pipeline Service and service Pod were launched, User-2 [ran his own](https://woodpecker.test.smthd.com/repos/2/pipeline/13).\r\n\r\nBugs:\r\n1. User-2's pipeline was cancelled with `error\":\"services \"postgres\" already exists`.\r\n2. User-1's Service and service Pod were deleted because User-2's pipeline cleaned up resources and the names were the same - `postgres`.\r\n\r\n### System Info\r\n\r\n```shell\r\n`next-0b5eef7d1e`, 1 Server, 1 Agent, max workflows 2.\r\n```\r\n\r\n\r\n### Additional context\r\n\r\n[woodpecker-agent.log](https://github.com/woodpecker-ci/woodpecker/files/14075623/woodpecker-agent.log)\r\n\r\nhttps://github.com/woodpecker-ci/woodpecker/pull/3236#issuecomment-1902404296\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]",[3089,3090],{"name":3019,"color":3020},{"name":3091,"color":3092},"backend/kubernetes","bfdadc",3288,"Multiple flaws when running pipelines with the same service (K8s)","2024-02-17T18:45:23Z","https://github.com/woodpecker-ci/woodpecker/issues/3288",0.6961614,{"description":3099,"labels":3100,"number":3105,"owner":3022,"repository":3023,"state":3060,"title":3106,"updated_at":3107,"url":3108,"score":3109},"### Component\r\n\r\nweb-ui\r\n\r\n### Describe the bug\r\n\r\njust saw this... Open for example https://ci.woodpecker-ci.org/woodpecker-ci/woodpecker/pipeline/6081 and look at the changed files counter\r\n\r\n### System Info\r\n\r\n```shell\r\nour ci\r\n```\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n\r\n",[3101,3102],{"name":3019,"color":3020},{"name":3103,"color":3104},"ui","46DEA2",1843,"Changed files counter shows 0 if opening pipeline directly","2023-10-15T07:14:06Z","https://github.com/woodpecker-ci/woodpecker/issues/1843",0.7070725,{"description":3111,"labels":3112,"number":3114,"owner":3022,"repository":3023,"state":3060,"title":3115,"updated_at":3116,"url":3117,"score":3118},"### 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]",[3113],{"name":3019,"color":3020},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.7150109,["Reactive",3120],{},["Set"],["ShallowReactive",3123],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f1G5BFHpJtwL7jwvCniVJzNOyFX7bdV51Tw5gTJ_Y69U":-1},"/woodpecker-ci/woodpecker/2831"]