\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]",[3019],{"name":3020,"color":3021},"bug","d73a4a",5338,"woodpecker-ci","woodpecker","open","Build status not completing on matrix pipelines with BitBucket","2025-07-17T18:03:12Z","https://github.com/woodpecker-ci/woodpecker/issues/5338",0.65753984,{"description":3031,"labels":3032,"number":3034,"owner":3023,"repository":3024,"state":3025,"title":3035,"updated_at":3036,"url":3037,"score":3038},"### Component\n\nserver\n\n### Describe the bug\n\nWe changed the Bitbucket build status key to use the same common method as other forges when reporting back the build status to the forge. It works as expected for Woodpecker instances that have not been running for a long time, but it starts failing on those that already have a lot of workflow runs.\n\nThe problem is the template we use to generate the key: \n\nhttps://github.com/woodpecker-ci/woodpecker/blob/1f23da379ef4ca103138c066baafcd65260b4005/cmd/server/flags.go#L279\n\nTemplate: \"{{ .context }}/{{ .event }}/{{ .workflow }}{{if not (eq .axis_id 0)}}/{{.axis_id}}{{end}}\"\n\nBitbucket has a maximum key length of 40 characters. It works as expected if axis_id is not added. The generated key without the axis_id has ~30 characters:\n- ci/woodpecker/branch/woodpecker (31)\n- ci/woodpecker/pr/woodpecker (27)\n\nBefore proposing a fix, I want to understand the purpose of the axis_id. I could not figure it out. What is the axis_id used for?\n\n### Steps to reproduce\n\n1. Woodpecker instance with axis_id > 100000000\n2. Trigger a Woodpecker workflow\n\n### Expected behavior\n\n1. The key should always be less than 40 characters for the Bitbucket forge\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-aac914cfae\"}\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]",[3033],{"name":3020,"color":3021},5176,"BitBucket build status key is too long","2025-05-14T07:35:49Z","https://github.com/woodpecker-ci/woodpecker/issues/5176",0.7101201,{"description":3040,"labels":3041,"number":3043,"owner":3023,"repository":3024,"state":3025,"title":3044,"updated_at":3045,"url":3046,"score":3047},"### Component\n\nserver\n\n### Describe the bug\n\nSee https://codeberg.org/Codeberg-CI/feedback/issues/120\r\n\r\nC/p issue description:\r\n\r\n1. Create repo in Gitea\r\n2. Enable it in WP\r\n3. Delete repo in Gitea\r\n4. Create repo with the same name in Gitea\r\n5. Try to enable it again\r\n\r\n-> error\r\n\r\nWhen enabling a repo, there should be a check for an existing one in the DB and if one exists, it should be deleted. \n\n### System Info\n\n```shell\n`next-dfc2c265b1` (Dec 20th)\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).",[3042],{"name":3020,"color":3021},3020,"Re-enabling a WP repo after previous deletion/recreation in forge leads to DB deadlock","2025-01-23T11:41:11Z","https://github.com/woodpecker-ci/woodpecker/issues/3020",0.73086756,{"description":3049,"labels":3050,"number":3052,"owner":3023,"repository":3024,"state":3025,"title":3053,"updated_at":3054,"url":3055,"score":3056},"### Component\n\nweb-ui\n\n### Describe the bug\n\nWhenever I navigate to the settings of a repo (same behavior for all repos) woodpecker reports \"an unknown error occured\". However, as far as I can tell, repo settings are interpreted correctly and I can also still update settings. Pipelines also execute normally. Even the server logs do not show any errors.\r\n\r\nSince I did not experience major issues yet and do not see any errors reported in the server logs (server is running with debug mode on currently), I am not sure how to debug further and thus wanted to report the issue. Probably a low priority issue with (hopefully) no major implications?\r\n\r\n\r\n\u003Cimg width=\"1284\" alt=\"image\" src=\"https://github.com/user-attachments/assets/403e1c1a-f6e7-4800-8a71-e8017cd4e18f\">\r\n\n\n### Steps to reproduce\n\n1. Click on any repository in Woodpecker's WebUI\r\n2. Click on settings icon\r\n3. Error shows up\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\nWoodpecker v2.7.1\r\nBitbucket Datacenter v9.1.1\r\n\r\nWoodpecker is running via docker compose:\r\n\r\n ...\r\n woodpecker-server:\r\n image: woodpeckerci/woodpecker-server:v2.7.1\r\n depends_on:\r\n - traefik\r\n container_name: woodpecker-server\r\n restart: always\r\n environment:\r\n - WOODPECKER_OPEN=true\r\n - WOODPECKER_SERVER_ADDR=:8000\r\n - WOODPECKER_HOST=\u003Cour-woodpecker-url>\r\n # OAuth setup for Bitbucket Datacenter\r\n - WOODPECKER_BITBUCKET_DC=true\r\n - WOODPECKER_BITBUCKET_DC_GIT_USERNAME=\u003Cdedicated-woodpecker-account>\r\n - WOODPECKER_BITBUCKET_DC_GIT_PASSWORD=\u003Cpassword>\r\n - WOODPECKER_BITBUCKET_DC_CLIENT_ID=\u003Cclient-id>\r\n - WOODPECKER_BITBUCKET_DC_CLIENT_SECRET=\u003Cclient-secret>\r\n - WOODPECKER_BITBUCKET_DC_URL=\u003Cbitbucket-dc-url>\r\n - WOODPECKER_BITBUCKET_DC_SKIP_VERIFY=true\r\n # Agent\r\n - WOODPECKER_AGENT_SECRET=\u003Cagent-secret>\r\n # Optional: Additional configurations\r\n - WOODPECKER_LOG_LEVEL=debug\r\n volumes:\r\n - woodpecker_server_data:/var/lib/woodpecker # Persist data across restarts\r\n networks:\r\n - harbor\r\n labels:\r\n - \"traefik.enable=true\"\r\n - \"traefik.http.routers.woodpecker.rule=Host(`\u003Cwoodpecker-url>`)\"\r\n - \"traefik.http.routers.woodpecker.entrypoints=websecure\"\r\n - \"traefik.http.routers.woodpecker.tls.certresolver=le\"\r\n - \"traefik.http.services.woodpecker.loadbalancer.server.port=8000\"\r\n - \"traefik.docker.network=harbor\"\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]",[3051],{"name":3020,"color":3021},4240,"Woodpecker 2.7.1 reporting \"an unknown error occured\" in repo settings","2024-10-21T10:52:58Z","https://github.com/woodpecker-ci/woodpecker/issues/4240",0.7322722,{"description":3058,"labels":3059,"number":3064,"owner":3023,"repository":3024,"state":3025,"title":3065,"updated_at":3066,"url":3067,"score":3068},"### 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).",[3060,3061],{"name":3020,"color":3021},{"name":3062,"color":3063},"ui","46DEA2",2831,"Service step doesn't change its status","2024-01-09T21:30:54Z","https://github.com/woodpecker-ci/woodpecker/issues/2831",0.7345534,{"description":3070,"labels":3071,"number":3076,"owner":3023,"repository":3024,"state":3025,"title":3077,"updated_at":3078,"url":3079,"score":3080},"### Component\n\ncli\n\n### Describe the bug\n\nRunning a pipeline directly like this:\r\n\r\n```console\r\n$ woodpecker exec .woodpecker/ubuntu.yml\r\n...\r\n[build:L188:17s] + ./get-deps.sh\r\n[build:L189:17s] /bin/sh: 30: ./get-deps.sh: not found\r\n```\r\n\r\nfails to mount the repo, so fails to run the `get-deps.sh` script that is present in the repo.\r\n\r\nHowever, running it like this:\r\n\r\n```console\r\n$ woodpecker exec .\r\n# ci.yml\r\n\r\n# ci.yml\r\n\r\n# rust.yml\r\n\r\n# ci.yml\r\n\r\n# ci.yml\r\n\r\n# ci.yml\r\n\r\n# ci.yml\r\n\r\n# ci.yml\r\n\r\n# codecov.yml\r\n\r\n# audit.yaml\r\n\r\n# benchmarks.yaml\r\n\r\n# coverage.yaml\r\n\r\n# test.yaml\r\n\r\n# ci.yml\r\n\r\n# FUNDING.yml\r\n...\r\n```\r\n\r\nworryingly enumerates all the various yaml files in my working copy (those shown are from misc .cache and .github directories) as shown above, as if it were trying to run those, but does mount the repo and is able to run the script from inside it.\r\n\r\nMy expectation is that I can specify the pipeline I want to run based on the `--help` output:\r\n\r\n```console\r\n$ woodpecker exec --help\r\n...\r\nUSAGE:\r\n woodpecker-cli exec [command options] [path/to/.woodpecker.yaml]\r\n```\r\n\r\nand have the repo mounted in the pipeline at the same time.\r\n\n\n### System Info\n\n```shell\n$ woodpecker --version\r\nwoodpecker-cli version 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).",[3072,3073],{"name":3020,"color":3021},{"name":3074,"color":3075},"cli","1d76db",2511,"`woodpecker exec .woodpecker/ubuntu.yml` has no repo available","2024-07-03T03:54:28Z","https://github.com/woodpecker-ci/woodpecker/issues/2511",0.73457247,{"description":3082,"labels":3083,"number":3085,"owner":3023,"repository":3024,"state":3086,"title":3087,"updated_at":3088,"url":3089,"score":3090},"### 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]",[3084],{"name":3020,"color":3021},5177,"closed","Statuses get incorrectly reported for multi workflow pipelines on BitBucket","2025-05-19T11:01:04Z","https://github.com/woodpecker-ci/woodpecker/issues/5177",0.6502862,{"description":3092,"labels":3093,"number":3098,"owner":3023,"repository":3024,"state":3086,"title":3099,"updated_at":3100,"url":3101,"score":3102},"### Component\n\nserver\n\n### Describe the bug\n\n**Issue:** \nWhen running a manual pipeline, the link to the commit is broken in Bitbucket DC.\n\n \n\n\n**Cause:** \nThe `forge_url` is set to:\n\n{bitbucket-url}/projects/{project}/repos/{repo-name}/browse\n\nAnd in this [line](https://github.com/woodpecker-ci/woodpecker/blob/main/server/forge/bitbucketdatacenter/bitbucketdatacenter.go#L380), we append `/commit/\u003Ccommit-id>` to it, resulting in the URL:\n\n{bitbucket-url}/projects/{project}/repos/{repo-name}/browse/commit/{commit-id}\n\nThis is a broken link in Bitbucket. The correct URL should be:\n\n{bitbucket-url}/projects/{project}/repos/{repo-name}/commits/{commit-id}\n\n**Note:** \nThis bug only affects manual pipelines. For push and pull request events, the correct URL is injected in the hook function: \n- [Line 100] (https://github.com/woodpecker-ci/woodpecker/blob/main/server/forge/bitbucketdatacenter/convert.go#L100) \n- [Line 123] (https://github.com/woodpecker-ci/woodpecker/blob/main/server/forge/bitbucketdatacenter/convert.go#L123\n\n### Steps to reproduce\n\n1. install server with bitbucket datacenter configured\n2. run pipeline with manual event -\n3. press on the commit in the pipeline - will result in a broken link.\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\nwoodpecker version 3.5.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]",[3094,3095],{"name":3020,"color":3021},{"name":3096,"color":3097},"forge/bitbucket","E96280",5159,"Bitbucket Datacenter commit url is broken","2025-05-20T10:13:15Z","https://github.com/woodpecker-ci/woodpecker/issues/5159",0.6683747,{"description":3104,"labels":3105,"number":3107,"owner":3023,"repository":3024,"state":3086,"title":3108,"updated_at":3109,"url":3110,"score":3111},"### Component\n\nserver\n\n### Describe the bug\n\n\r\n\r\nI'll try to downgrade my woodpecker version to fix this, because all PRs are now broken on `next`.\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-5bd12aa646\"}\n```\n\n\n### Additional context\n\nNA\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).",[3106],{"name":3020,"color":3021},2350,"All github PRs are reported as *Waiting for status to be reported*","2023-10-02T06:45:33Z","https://github.com/woodpecker-ci/woodpecker/issues/2350",0.69343257,{"description":3113,"labels":3114,"number":3117,"owner":3023,"repository":3024,"state":3086,"title":3118,"updated_at":3119,"url":3120,"score":3121},"### Component\n\nserver\n\n### Describe the bug\n\nHi,\r\n\r\nI'm currently in the process of migrating a fairly old Bitbucket Server 7.x (non-cloud) instance to Bitbucket Data Center 8.8. As part of this, I'm also investigating migration of a super old woodpecker instance (`v0.8.105`) to `v0.15.7` and now to `next`.\r\n\r\nApart from the typical to be expected DB migrations and breaking `ENV` configuration changes, the branch list integration introduced with #907 (more exactly the `\u003Cbase>/2.0/repositories/\u003Cowner>/\u003Cname>/refs/branches` template string [here](https://github.com/woodpecker-ci/woodpecker/pull/907/files#diff-ecc104bf0e9c2d9167c43bce82421e93507f8a8660f061ac2171d298dfe214ea)) is actually something still blocking us currently. It `404`s on Bitbucket Server / Data Center and consequently `500` within Woodpecker.\r\n\r\nAFAIK for both Bitbucket Server / Data Center 7.x and 8.x (non-cloud) the proper integration endpoint should be `GET \u003Cbase>/rest/api/latest/projects/\u003Cowner>/repos/\u003Cname>/branches`. Sample Bitbucket Response of this endpoint is:\r\n\r\n```json\r\n{\r\n \"size\": 4,\r\n \"limit\": 25,\r\n \"isLastPage\": true,\r\n \"values\": [\r\n {\r\n \"id\": \"refs/heads/dev\",\r\n \"displayId\": \"dev\",\r\n \"type\": \"BRANCH\",\r\n \"latestCommit\": \"\u003CSHA>\",\r\n \"latestChangeset\": \"\u003CSHA>\",\r\n \"isDefault\": false\r\n },\r\n {\r\n \"id\": \"refs/heads/main\",\r\n \"displayId\": \"main\",\r\n \"type\": \"BRANCH\",\r\n \"latestCommit\": \"\u003CSHA>\",\r\n \"latestChangeset\": \"\u003CSHA>\",\r\n \"isDefault\": true\r\n }\r\n ],\r\n \"start\": 0\r\n}\r\n```\r\n\r\nSources:\r\n* https://developer.atlassian.com/server/bitbucket/rest/v808/api-group-repository/#api-api-latest-projects-projectkey-repos-repositoryslug-branches-get\n\n### System Info\n\n```shell\nwoodpeckerci/woodpecker-server:next-e408c1ba27-alpine\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-e408c1ba\"}\n```\n\n\n### Additional context\n\nWoodpecker Server Log:\r\n```json\r\n{\r\n \"level\": \"error\",\r\n \"error\": \"Error #01: invalid character '\u003C' looking for beginning of value\\n\",\r\n \"ip\": \"xxx.xxx.xxx.xxx\",\r\n \"latency\": 54.356947,\r\n \"method\": \"GET\",\r\n \"path\": \"/api/repos/PROJECT/REPO/branches\",\r\n \"status\": 500,\r\n \"user-agent\": \"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/111.0.0.0 Safari/537.36\",\r\n \"time\": \"2023-04-03T15:57:01Z\",\r\n \"caller\": \"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/router/middleware/logger.go:43\"\r\n}\r\n```\r\n\r\nBrowser Console / UI:\r\n\u003Cimg width=\"997\" alt=\"Bildschirmfoto 2023-04-03 um 17 57 28\" src=\"https://user-images.githubusercontent.com/2149883/229565185-5c2b1a17-735d-43c7-ab2f-31214801da71.png\">\r\n\u003Cimg width=\"120\" alt=\"Bildschirmfoto 2023-04-03 um 18 00 10\" src=\"https://user-images.githubusercontent.com/2149883/229565201-340e64e4-85fb-45be-80a3-af8072dc243e.png\">\r\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] 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,3116],{"name":3020,"color":3021},{"name":3096,"color":3097},1695,"Bitbucket Server / Data Center: List branches endpoint 404","2023-04-07T16:09:19Z","https://github.com/woodpecker-ci/woodpecker/issues/1695",0.6994599,["Reactive",3123],{},["Set"],["ShallowReactive",3126],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fA-VAqjAvUkHleeyQ_vI0zY7Bp9p2Fwvqq9e3sN61RXY":-1},"/woodpecker-ci/woodpecker/5158"]