\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.6752924,{"description":3031,"labels":3032,"number":3039,"owner":3023,"repository":3024,"state":3025,"title":3040,"updated_at":3041,"url":3042,"score":3043},"### Component\r\n\r\nserver\r\n\r\n### Describe the bug\r\n\r\nThis is further to the discussion on [discord](https://discord.com/channels/838698813463724034/911685405546524722/1132977506362855424).\r\n\r\nMy publish step (using `woodpeckerci/plugin-docker-buildx`) was correct, yet still yielded this error:\r\n> ERROR: tag is needed when pushing to registry\r\n\r\nI spent hours going over every little thing in my config. No one on the discord channel could figure it out either.\r\n\r\nFinally I discovered the problem:\r\n```yml\r\n publish:\r\n image: woodpeckerci/plugin-docker-buildx\r\n settings:\r\n password:\r\n from_secret: publish-to-registry\r\n tags: [latest, 1.2.3] # \u003C----- I did specify tags\r\n # ...\r\n when:\r\n event: tag\r\n```\r\nThe `publish-to-registry` global secret had the `manual` and `push` scopes, but not `tag`.\r\n\r\nSo the error log was misleading.\r\n\r\nI hope it can be fixed so it doesn't waste other peoples' time, and cause more repo issues (unnecessary work for you :smile:).\r\n\r\n### System Info\r\n\r\n```shell\r\nnext-b3c2bb2e (latest)\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] 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).",[3033,3036],{"name":3034,"color":3035},"server","5D7A92",{"name":3037,"color":3038},"enhancement","7E1FE4",2032,"Incorrect error for buildx plugin and global secret of insufficient scope","2023-07-26T02:44:15Z","https://github.com/woodpecker-ci/woodpecker/issues/2032",0.72238714,{"description":3045,"labels":3046,"number":3048,"owner":3023,"repository":3024,"state":3025,"title":3049,"updated_at":3050,"url":3051,"score":3052},"### 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]",[3047],{"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.7336593,{"description":3054,"labels":3055,"number":3057,"owner":3023,"repository":3024,"state":3058,"title":3059,"updated_at":3060,"url":3061,"score":3062},"### Component\n\nserver\n\n### Describe the bug\n\nWe're running woodpecker on k8s and using postgres for backend / metadata store, this is intermittent issue; sometimes the pipeline works and sometimes we see the error in server logs\r\n\r\n`Getting Error #01: failed to save pipeline for repo; error=\"pq: value too long for type character varying(255)\"`\n\n### Steps to reproduce\n\nNot sure how to re-produce this; since this is very intermittent.\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.6.0\"}\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]",[3056],{"name":3020,"color":3021},4596,"closed","support to allow more than 255 chars for avatar column in 2.x ","2024-12-21T11:06:09Z","https://github.com/woodpecker-ci/woodpecker/issues/4596",0.6660853,{"description":3064,"labels":3065,"number":3068,"owner":3023,"repository":3024,"state":3058,"title":3069,"updated_at":3070,"url":3071,"score":3072},"### 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).",[3066,3067],{"name":3020,"color":3021},{"name":3034,"color":3035},1194,"Commit message to long for db column ","2022-10-12T22:47:13Z","https://github.com/woodpecker-ci/woodpecker/issues/1194",0.67436934,{"description":3074,"labels":3075,"number":3080,"owner":3023,"repository":3024,"state":3058,"title":3081,"updated_at":3082,"url":3083,"score":3084},"### Component\n\nother\n\n### Describe the bug\n\n```yaml\nsteps:\n - name: push to ecr dev\n image: woodpeckerci/plugin-docker-buildx:6.0.0\n settings:\n mtu: 1500\n registry: \u003Cregistry>\n dockerfile: ./Dockerfile\n build_args:\n WWWGROUP: \"1000\"\n SUPERVISORD_GO_OS: Linux_ARM64\n repo: \u003Crepo>\n aws_region: \u003Cregion>\n tags:\n - dev\n aws_access_key_id: \u003Ckey>\n aws_secret_access_key: \u003Csecret>\n backend_options:\n kubernetes:\n resources:\n requests:\n memory: 1200Mi\n cpu: 1200m\n limits:\n memory: 1500Mi\n cpu: 1600m\n when:\n branch:\n - develop\n event:\n - push\n```\n\n\n### Steps to reproduce\n\nThis yaml produces docker args `--build-arg 1000 --build-arg Linux_ARM64`.\n\n### Expected behavior\n\nIt should produce docker args `--build-arg WWWGROUP=1000 --build-arg SUPERVISORD_GO_OS=Linux_ARM64`.\n\n### System Info\n\n```shell\nWoodpecker helm chart 3.1.0\n\nwoodpeckerci/plugin-docker-buildx v6.0.0\n```\n\n### Additional context\n\nWorkaround:\n\n```yaml\nsteps:\n - name: push to ecr dev\n image: woodpeckerci/plugin-docker-buildx:6.0.0\n settings:\n mtu: 1500\n registry: \u003Cregistry>\n dockerfile: ./Dockerfile\n build_args:\n WWWGROUP: WWWGROUP=1000\n SUPERVISORD_GO_OS: SUPERVISORD_GO_OS=Linux_ARM64\n repo: \u003Crepo>\n aws_region: \u003Cregion>\n tags:\n - dev\n aws_access_key_id: \u003Ckey>\n aws_secret_access_key: \u003Csecret>\n backend_options:\n kubernetes:\n resources:\n requests:\n memory: 1200Mi\n cpu: 1200m\n limits:\n memory: 1500Mi\n cpu: 1600m\n when:\n branch:\n - develop\n event:\n - push\n```\n\nThis workaround produces `--build-arg WWWGROUP=1000 --build-arg SUPERVISORD_GO_OS=Linux_ARM64`, lol.\n\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]",[3076,3077],{"name":3020,"color":3021},{"name":3078,"color":3079},"plugin","887B27",5145,"Plugin plugin-docker-buildx v6 removes keys from build-arg","2025-05-04T10:42:17Z","https://github.com/woodpecker-ci/woodpecker/issues/5145",0.69744515,{"description":3086,"labels":3087,"number":3092,"owner":3023,"repository":3024,"state":3058,"title":3093,"updated_at":3094,"url":3095,"score":3096},"### 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).",[3088,3089],{"name":3020,"color":3021},{"name":3090,"color":3091},"forge/bitbucket","E96280",1695,"Bitbucket Server / Data Center: List branches endpoint 404","2023-04-07T16:09:19Z","https://github.com/woodpecker-ci/woodpecker/issues/1695",0.7012419,{"description":3098,"labels":3099,"number":3102,"owner":3023,"repository":3024,"state":3058,"title":3103,"updated_at":3104,"url":3105,"score":3106},"### Component\n\nserver\n\n### Describe the bug\n\nWhen build finishes(either successfully or with failure) the status doesn't get updated, even though the commit status of the last commit on the PR is updated just fine.\n\nI was able to trace back this bug to this PR: https://github.com/woodpecker-ci/woodpecker/pull/4724\n\nNow I see the need for the `Ref` to be set when updating the build status but it turns out that `pipeline.Ref` doesn't have a correct value. In my case it would set only the ref as follows: `refs/pull-requests/\u003CpullRequestID>/from`. I was able to find that `Ref` gets set [here](https://github.com/woodpecker-ci/woodpecker/blob/main/server/forge/bitbucketdatacenter/convert.go#L122) and I believe this is wrong, it's not a \"valid\" git ref and if ref is set to an invalid value BitBucket will not set the build status for that PR(https://community.atlassian.com/forums/Bitbucket-questions/Re-Builds-not-appearing-in-pull-requests/qaq-p/1805991/comment-id/65864#M65864).\n\nI suggest that we change the code from above to:\n```go\nRef: fmt.Sprintf(\"refs/heads/%s\", ev.PullRequest.Source.DisplayID),\n```\nI believe this would fix the issue, and I would like to work on it if possible.\n\nAdding: @Levy-Tal as he worked on PR mentioned above and @langecode because he is the main contributor behind the BitBucket Datacenter forge integration.\n\n\n### Steps to reproduce\n\n1. Open a PR with woodpecker pipelines on BitBucket Datacenter\n2. Trigger a build on the last commit of that PR\n3. Wait for the build to finish\n4. Observe that there is no status on the PR itself\n\n### Expected behavior\n\nThere should be a build status on the PR.\n\n### System Info\n\n```shell\nWoodpecker version: v3.5.2\nHelm chart version: 3.1.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]",[3100,3101],{"name":3020,"color":3021},{"name":3090,"color":3091},5158,"PR build status does not get updated on BitBucket Datacenter","2025-05-13T15:29:01Z","https://github.com/woodpecker-ci/woodpecker/issues/5158",0.70672774,{"description":3108,"labels":3109,"number":3111,"owner":3023,"repository":3024,"state":3058,"title":3112,"updated_at":3113,"url":3114,"score":3115},"### 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).",[3110],{"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.7070941,{"description":3117,"labels":3118,"number":3120,"owner":3023,"repository":3024,"state":3058,"title":3121,"updated_at":3122,"url":3123,"score":3124},"### Component\n\nserver, web-ui\n\n### Describe the bug\n\nWe are in the process of migrating from **Drone** to **Woodpecker** and are experiencing an issue when logging into Woodpecker. We are using **Bitbucket Data Center** which contains a large number of repositories. The problem occurs when attempting to log in to Woodpecker: After I log in and approve access via Bitbucket, I am redirected back to Woodpecker. However, it takes about **1:30 minutes** for me to be logged into Woodpecker. During this time, I notice in the Bitbucket logs that Woodpecker is making multiple GET requests to retrieve all of the repositories associated with my Bitbucket account.\r\n\r\nIn drone for example we are logged in instantly. and after that i can sync the repos inside the tool itself.\n\n### Steps to reproduce\n\n1. Set up a Bitbucket Data Center instance with a large number of repositories.\r\n2. Integrate Woodpecker with Bitbucket as the authentication provider.\r\n3. Attempt to log in to Woodpecker using Bitbucket authentication.\r\n4. After approving the permissions in Bitbucket, observe the redirection back to Woodpecker.\r\n5. Monitor the time it takes for the login to complete (approximately 1:30 minutes).\r\n6. Check the Bitbucket logs and see multiple GET requests made by Woodpecker to fetch all repositories.\r\n7. Compare this behavior with Drone, where login happens instantly, and repositories can be synced within the tool itself.\n\n### Expected behavior\n\nLogging into Woodpecker should be quicker, similar to how Drone operates, without unnecessary delays or multiple repository fetches during login.\n\n### System Info\n\n```shell\n2.7.3\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]",[3119],{"name":3020,"color":3021},4580,"[Bitbucket Data Center] Login takes a long time","2024-12-17T19:44:50Z","https://github.com/woodpecker-ci/woodpecker/issues/4580",0.71316576,["Reactive",3126],{},["Set"],["ShallowReactive",3129],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fmJKoExnWBz9VfpZb8QhtEHS09-fcODHMJIHv9HsmpeY":-1},"/woodpecker-ci/woodpecker/5176"]