\r\n\n\n### Steps to reproduce\n\n.\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\n\"next-d126cf9e35\"\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]",[2893,2896],{"name":2894,"color":2895},"bug","d73a4a",{"name":2880,"color":2881},4677,"`tag` pipelines are missing avatar and commit title","2025-01-12T06:19:42Z","https://github.com/woodpecker-ci/woodpecker/issues/4677",0.7620158,{"description":2903,"labels":2904,"number":2910,"owner":2869,"repository":2870,"state":2871,"title":2911,"updated_at":2912,"url":2913,"score":2914},"### Clear and concise description of the problem\n\nIt would be great to have a search form available at `/admin`. For instances with more users (e.g. codeberg), the paginated load becomes quite an issue when searching for a particular user/org/repository.\r\n\r\n\n\n### Suggested solution\n\nAdd a search functionality, similar as in https://ci.codeberg.org/repos.\n\n### Alternative\n\n_No response_\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 [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 request the same feature to avoid creating a duplicate.",[2905,2908,2909],{"name":2906,"color":2907},"server","5D7A92",{"name":2880,"color":2881},{"name":2883,"color":2884},3015,"Admin: Search functionality for users/repos/organizations","2023-12-27T07:56:01Z","https://github.com/woodpecker-ci/woodpecker/issues/3015",0.7641103,{"description":2916,"labels":2917,"number":2921,"owner":2869,"repository":2870,"state":2871,"title":2922,"updated_at":2923,"url":2924,"score":2925},"### Clear and concise description of the problem\n\nHi there, that would be awesome if secrets would be pullable from Hashicorp Vault, by integration like [this](https://docs.gitlab.com/ee/ci/examples/authenticating-with-hashicorp-vault/)\r\n\n\n### Suggested solution\n\nby this https://docs.gitlab.com/ee/ci/secrets/index.html#configure-your-vault-server\r\nand that https://docs.gitlab.com/ee/ci/secrets/index.html#use-vault-secrets-in-a-ci-job\n\n### Alternative\n\nwrapping stuff in bash, that's sad and nasty, because woodpecker does not treat it as concealed string, and secrets gets leaked\r\n[import this onto woodpecker plugin system](https://github.com/drone/drone-vault)\n\n### Additional context\n\nhttps://www.hashicorp.com/resources/securing-your-ci-pipeline-with-vault\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 request the same feature to avoid creating a duplicate.",[2918],{"name":2919,"color":2920},"feature","180DBE",929,"Hashicorp vault as secret storage integration","2025-03-06T00:07:49Z","https://github.com/woodpecker-ci/woodpecker/issues/929",0.76465946,{"description":2927,"labels":2928,"number":2931,"owner":2869,"repository":2870,"state":2871,"title":2932,"updated_at":2933,"url":2934,"score":2935},"### Component\n\nserver\n\n### Describe the bug\n\nError when enabling Gitea repository in Woodpecker CI:\n\n`could not create/update repo in store. error=\"pq: duplicate key value violates unique constraint \\\"UQE_repos_name\\\"\"`\n\nThere are no records with forge_id 0 in orgs table where we had similar problems\n\n### Steps to reproduce\n\n1. Press \"Enable\" in repository list\n2. Webhook is created\n3. Record in database can not be updated (possible tries to insert new one instead of updating?)\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"3.3.0\"}\n```\n\n### Additional context\n\nPostgreSQL database, Gitea forge integration\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]",[2929,2930],{"name":2894,"color":2895},{"name":2906,"color":2907},4935,"Activating repository error that failed to activate becauce of UQE_repos_name constraint","2025-03-11T14:11:01Z","https://github.com/woodpecker-ci/woodpecker/issues/4935",0.7674143,{"description":2937,"labels":2938,"number":2942,"owner":2869,"repository":2870,"state":2943,"title":2944,"updated_at":2945,"url":2946,"score":2947},"... move the details from https://woodpecker-ci.org/docs/next/usage/pipeline-syntax#images-from-private-registries to https://woodpecker-ci.org/docs/next/usage/registries and link there instead ...\r\n\r\nand also make it clear in the WebUI that registry tab in repo settings is only for pull images by the agent and not for push via some plugin",[2939],{"name":2940,"color":2941},"documentation","7D625D",1408,"closed","Docs: move private registry infos","2023-10-17T08:31:09Z","https://github.com/woodpecker-ci/woodpecker/issues/1408",0.6772199,{"description":2949,"labels":2950,"number":2952,"owner":2869,"repository":2870,"state":2943,"title":2953,"updated_at":2954,"url":2955,"score":2956},"### Component\r\n\r\nserver, web-ui\r\n\r\n### Describe the bug\r\n\r\nHi, I have problem with my woodpecker instance. I'm using Github to provide OAuth2 Authorization. But the problem I cannot log in to the app. When I clicking \"Log in\" button, it returns to the same screen. Sometimes when I do many clicks in small amount time I need reatuhorize it in Github.\r\n\r\nInstance is hidden with ngnix proxy manager. \r\n\r\nMy docker compose looks like this:\r\n```\r\nservices:\r\n woodpecker-server:\r\n image: woodpeckerci/woodpecker-server:latest\r\n expose:\r\n - 8000\r\n - 9000\r\n volumes:\r\n - ./woodpecker-server-data:/var/lib/woodpecker/\r\n environment:\r\n - WOODPECKER_OPEN=false\r\n - WOODPECKER_HOST=${WOODPECKER_HOST}\r\n - WOODPECKER_GITHUB=true\r\n - WOODPECKER_GITHUB_CLIENT=${WOODPECKER_GITHUB_CLIENT}\r\n - WOODPECKER_GITHUB_SECRET=${WOODPECKER_GITHUB_SECRET}\r\n - WOODPECKER_AGENT_SECRET=${WOODPECKER_AGENT_SECRET}\r\n - WOODPECKER_ADMIN=${WOODPECKER_ADMIN}\r\n - WOODPECKER_REPO_OWNERS=${WOODPECKER_REPO_OWNERS}\r\n networks:\r\n - ngnix-internal\r\n - composehook-internal\r\n woodpecker-agent:\r\n image: woodpeckerci/woodpecker-agent:latest\r\n command: agent\r\n restart: always\r\n depends_on:\r\n - woodpecker-server\r\n volumes:\r\n - ./woodpecker-agent-config:/etc/woodpecker\r\n - /var/run/docker.sock:/var/run/docker.sock\r\n environment:\r\n - WOODPECKER_SERVER=woodpecker-server:9000\r\n - WOODPECKER_AGENT_SECRET=${WOODPECKER_AGENT_SECRET}\r\n - WOODPECKER_BACKEND_DOCKER_NETWORK=composehook-internal\r\n networks:\r\n - ngnix-internal\r\n - composehook-internal\r\nnetworks:\r\n ngnix-internal:\r\n external: true\r\n name: ngnix-internal\r\n composehook-internal:\r\n external: true\r\n name: composehook-internal\r\n```\r\n\r\nIn logs I haven't see something weird or wrong.\r\n\r\n\r\n### System Info\r\n\r\n```shell\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.4.1\"}\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 [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]",[2951],{"name":2894,"color":2895},3689,"Stuck on login screen. ","2024-06-21T08:20:32Z","https://github.com/woodpecker-ci/woodpecker/issues/3689",0.70840836,{"description":2958,"labels":2959,"number":2961,"owner":2869,"repository":2870,"state":2943,"title":2962,"updated_at":2963,"url":2964,"score":2965},"### Component\r\n\r\nagent\r\n\r\n### Describe the bug\r\n\r\nWhen having a backend error in the config, i.e. a malformed env var, the step and build are marked as successful even though they should be marked as \"failed\". \r\n\r\n\r\n\r\n\r\nk8s backend\r\n\r\n\r\n### System Info\r\n\r\n```shell\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-6ab9f802\"}\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).",[2960],{"name":2894,"color":2895},1871,"Build is marked as \"successful\" although a backend error occurred","2025-01-10T21:25:48Z","https://github.com/woodpecker-ci/woodpecker/issues/1871",0.7192377,{"description":2967,"labels":2968,"number":2970,"owner":2869,"repository":2870,"state":2943,"title":2971,"updated_at":2972,"url":2973,"score":2974},"### Component\n\nserver, agent\n\n### Describe the bug\n\nIf you try to set proxy related env vars in a pipeline step, they won't get used. They are present but without the given values:\r\n\r\n```yaml\r\nwhen:\r\n - event: [pull_request, tag, cron]\r\n - event: push\r\n branch:\r\n - ${CI_REPO_DEFAULT_BRANCH}\r\n - renovate/*\r\n\r\nvariables:\r\n - &golang \"golang:1.21\"\r\n - proxy_args: &proxy_args\r\n - \"http_proxy=http://swarmproxy:8888\"\r\n - \"https_proxy=http://swarmproxy:8888\"\r\n - \"no_proxy=.myhost.com\"\r\n - \"TESTENV=DEBUGGING\"\r\nsteps:\r\n test:\r\n image: *golang\r\n environment:\r\n - \u003C\u003C: *proxy_args\r\n commands:\r\n - env | sort\r\n - go test -cover ./...\r\n```\r\n\r\nThe output looks like this:\r\n\r\n```shell\r\n....\r\nGOLANG_VERSION=1.21.4\r\nGOPATH=/go\r\nGOTOOLCHAIN=local\r\nHOME=/root\r\nHOSTNAME=45d463959e69\r\nHTTPS_PROXY=\r\nHTTP_PROXY=\r\nNO_PROXY=\r\nPATH=/go/bin:/usr/local/go/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin\r\nPWD=/woodpecker/src/xxxxxx/Templates/plugin-extend-env\r\nSHELL=/bin/sh\r\nTESTENV=DEBUGGING\r\nhttp_proxy=\r\nhttps_proxy=\r\nno_proxy=\r\n+ go test -cover ./...\r\ngo: downloading github.com/urfave/cli/v2 v2.25.7\r\ngo: downloading github.com/sirupsen/logrus v1.9.3\r\ngo: downloading github.com/Masterminds/semver/v3 v3.2.1\r\ngo: downloading github.com/joho/godotenv v1.5.1\r\nsemver.go:6:2: github.com/Masterminds/semver/v3@v3.2.1: Get \"https://proxy.golang.org/github.com/%21masterminds/semver/v3/@v/v3.2.1.zip\": dial tcp: lookup proxy.golang.org on 127.0.0.11:53: no such host\r\ntools.go:3:8: github.com/joho/godotenv@v1.5.1: Get \"https://proxy.golang.org/github.com/joho/godotenv/@v/v1.5.1.zip\": dial tcp: lookup proxy.golang.org on 127.0.0.11:53: no such host\r\nlogger.go:6:2: github.com/sirupsen/logrus@v1.9.3: Get \"https://proxy.golang.org/github.com/sirupsen/logrus/@v/v1.9.3.zip\": dial tcp: lookup proxy.golang.org on 127.0.0.11:53: no such host\r\nflags.go:4:2: github.com/urfave/cli/v2@v2.25.7: Get \"https://proxy.golang.org/github.com/urfave/cli/v2/@v/v2.25.7.zip\": dial tcp: lookup proxy.golang.org on 127.0.0.11:53: no such host\r\n...\r\n```\n\n### System Info\n\n```shell\n{\r\n \"source\": \"https://github.com/woodpecker-ci/woodpecker\",\r\n \"version\": \"1.0.5\"\r\n}\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).",[2969],{"name":2894,"color":2895},2858,"Proxy environment variables not passed through in pipeline steps","2023-12-03T16:50:09Z","https://github.com/woodpecker-ci/woodpecker/issues/2858",0.72454554,["Reactive",2976],{},["Set"],["ShallowReactive",2979],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fqOmYsJVEceJEpd-zJ1I1KUKswtJs_uHBYoWmD_yl5y8":-1},"/woodpecker-ci/woodpecker/2982"]