\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]",[2865,2868],{"name":2866,"color":2867},"bug","d73a4a",{"name":2869,"color":2870},"ui","46DEA2",4677,"woodpecker-ci","woodpecker","open","`tag` pipelines are missing avatar and commit title","2025-01-12T06:19:42Z","https://github.com/woodpecker-ci/woodpecker/issues/4677",0.7592842,{"description":2880,"labels":2881,"number":2890,"owner":2872,"repository":2873,"state":2874,"title":2891,"updated_at":2892,"url":2893,"score":2894},"We could have a workspace preparation docker image that would be run as root and do necessary tasks to prepare everything so that the skip clone would work and also clone steps could be run as non-root images?\n\nMaybe even a woodpecker server could act as docker registry to serve container image for this so that it would work in instances that have no internet connection\n\n_Originally posted by @lafriks in https://github.com/woodpecker-ci/woodpecker/pull/5056#issuecomment-2784618118_",[2882,2885,2888],{"name":2883,"color":2884},"server","5D7A92",{"name":2886,"color":2887},"backend/docker","bfdadc",{"name":2889,"color":2887},"backend/kubernetes",5082,"Add workspace preparation hidden step before clone steps","2025-04-07T21:24:54Z","https://github.com/woodpecker-ci/woodpecker/issues/5082",0.7679765,{"description":2896,"labels":2897,"number":2901,"owner":2872,"repository":2873,"state":2874,"title":2902,"updated_at":2903,"url":2904,"score":2905},"### Clear and concise description of the problem\r\n\r\nFor build steps, I might be fine with using a \":latest\" image, but for diagnostics I want to be able to see exactly which image was used for a build. \r\n\r\n### Suggested solution\r\n\r\nPrint the docker image hash as a log line\r\n\r\n### Alternative\r\n\r\n_No response_\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 request the same feature to avoid creating a duplicate.",[2898],{"name":2899,"color":2900},"feature","180DBE",1414,"record build step docker image id","2023-08-20T17:13:01Z","https://github.com/woodpecker-ci/woodpecker/issues/1414",0.7699854,{"description":2907,"labels":2908,"number":2910,"owner":2872,"repository":2873,"state":2874,"title":2911,"updated_at":2912,"url":2913,"score":2914},"### 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.",[2909],{"name":2899,"color":2900},929,"Hashicorp vault as secret storage integration","2025-03-06T00:07:49Z","https://github.com/woodpecker-ci/woodpecker/issues/929",0.77128756,{"description":2916,"labels":2917,"number":2919,"owner":2872,"repository":2873,"state":2874,"title":2920,"updated_at":2921,"url":2922,"score":2923},"### Component\n\nserver\n\n### Describe the bug\n\nRestarting a pipeline that failed due to missing secrets is not enough.\r\nI have seen it in a tag event.\r\n```\r\nsecret \"***\" not found or not allowed to be used\r\n```\r\nThen I added the secret and restarted the pipeline and the error changed to\r\n```\r\n[generic]\r\npipeline definition not found\r\n```\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-5a7e314f5a\"}\n```\n\n\n### Additional context\n\nMight be related to https://github.com/woodpecker-ci/woodpecker/issues/1678\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).",[2918],{"name":2866,"color":2867},2982,"Restarting a pipeline that failed due to missing secrets is not enough","2024-12-08T12:10:58Z","https://github.com/woodpecker-ci/woodpecker/issues/2982",0.7757558,{"description":2925,"labels":2926,"number":2933,"owner":2872,"repository":2873,"state":2874,"title":2934,"updated_at":2935,"url":2936,"score":2937},"and address\r\n- https://github.com/woodpecker-ci/woodpecker/issues/3503 -> #3820\r\n- https://github.com/woodpecker-ci/woodpecker/pull/3733#issuecomment-2180578290\r\n- ...\r\n\r\nTests to run:\r\n- [ ] Run workflow with steps that should only run if the step before [failed,succeded] (could help with questions like: https://github.com/woodpecker-ci/woodpecker/pull/3846#discussion_r1686246455)\r\n- [ ] Services and check if it is started before the steps who need it ...\r\n- [ ] Make sure the Queue respect **labels** and dependencies correctly\r\n- [ ] ...",[2927,2930],{"name":2928,"color":2929},"tests","ACEA1E",{"name":2931,"color":2932},"summary","C3DC73",3819,"Create \"backend integration test\" framework","2024-11-05T23:18:48Z","https://github.com/woodpecker-ci/woodpecker/issues/3819",0.77668905,{"description":2939,"labels":2940,"number":2942,"owner":2872,"repository":2873,"state":2943,"title":2944,"updated_at":2945,"url":2946,"score":2947},"### Component\r\n\r\nother\r\n\r\n### Describe the bug\r\n\r\nI am testing version 2.6 in my development environment, so I updated an application code to use \r\n```- evaluate: CI_PIPELINE_DEPLOY_TASK == \"sre-dummy-rest-app\"```\r\ninstead of the 'task:' filter.\r\nIn my github hooks payload I get: \r\n\r\nBut the CI_PIPELINE_DEPLOY_TASK is empty and woodpecker is not running the steps that it should run.\r\n\r\n### Steps to reproduce\r\n\r\nUsing :\r\n``` \r\nwhen:\r\n - evaluate: CI_PIPELINE_DEPLOY_TASK == \"value\" \r\n```\r\n\r\nInstead of:\r\n`task: \"value\"`\r\n\r\n### Expected behavior\r\n\r\nRun with the variable as it should run with the filter in previous versions.\r\n\r\n### System Info\r\n\r\n```shell\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.6.0\"}\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]",[2941],{"name":2866,"color":2867},3872,"closed","variable CI_PIPELINE_DEPLOY_TASK is empty in woodpecker","2024-07-07T11:43:08Z","https://github.com/woodpecker-ci/woodpecker/issues/3872",0.7177457,{"description":2949,"labels":2950,"number":2953,"owner":2872,"repository":2873,"state":2943,"title":2954,"updated_at":2955,"url":2956,"score":2957},"### Component\n\nserver\n\n### Describe the bug\n\nAfter upgrading to 3.2.0, I am no longer able to enable new repos in the server dashboard. Attempting results in a error notification and the message \"Error 1062 (23000): Duplicate entry 'devin' for key 'UQE_orgs_name'\" being written to the server logs with \"devin\" being admin and only user. Also happens in the current `next` version.\n\nRolling back to 3.1.0, repos can be enabled without issue. \n\n\n\n### Steps to reproduce\n\n1. Navigate to the `/repos` page.\n2. Click the \"Add repository\" button.\n3. Click \"Enable\" on any listed repository not currently enabled. \n4. Receive error message\n\n### Expected behavior\n\nI should be able to enable a repo without error. \n\n### System Info\n\n```shell\n{\n \"source\": \"https://github.com/woodpecker-ci/woodpecker\",\n \"version\": \"next-1232ceb794\"\n}\n```\n\n### Additional context\n\n- Reproducible with `woodpeckerci/woodpecker-server:v3.2.0` and `woodpeckerci/woodpecker-server:next-1232ceb794` container images.\n- Running in a K3S cluster\n- Gitea forge version 1.23.3\n- MariaDB database\n\nServer debug log: [server.debug.log](https://github.com/user-attachments/files/19040797/server.debug.log)\n\nKubernetes Manifest: \n\n```\n---\n\napiVersion: apps/v1\nkind: StatefulSet\nmetadata:\n name: woodpecker-server\n namespace: woodpecker\n labels:\n app.kubernetes.io/name: woodpecker\n app.kubernetes.io/component: server\nspec:\n serviceName: woodpecker-server-headless\n revisionHistoryLimit: 2\n replicas: 1\n minReadySeconds: 20\n selector:\n matchLabels:\n app.kubernetes.io/name: woodpecker\n app.kubernetes.io/component: server\n template:\n metadata:\n labels:\n app.kubernetes.io/name: woodpecker\n app.kubernetes.io/component: server\n spec:\n priorityClassName: please-keep-running\n restartPolicy: Always\n terminationGracePeriodSeconds: 100\n containers:\n - name: server\n image: woodpeckerci/woodpecker-server:v3.2.0\n imagePullPolicy: IfNotPresent\n env:\n - name: WOODPECKER_DATABASE_DRIVER\n value: mysql\n - name: WOODPECKER_DATABASE_DATASOURCE\n valueFrom:\n secretKeyRef:\n key: dsn\n name: woodpecker-server\n - name: WOODPECKER_HOST\n valueFrom:\n secretKeyRef:\n key: host\n name: woodpecker-server\n - name: WOODPECKER_ADMIN\n value: devin\n - name: WOODPECKER_GITEA\n value: \"true\"\n - name: WOODPECKER_GITEA_URL\n valueFrom:\n secretKeyRef:\n key: gitea_url\n name: woodpecker-server\n - name: WOODPECKER_GITEA_CLIENT\n valueFrom:\n secretKeyRef:\n key: gitea_client\n name: woodpecker-server\n - name: WOODPECKER_GITEA_SECRET\n valueFrom:\n secretKeyRef:\n key: gittea_key\n name: woodpecker-server\n - name: WOODPECKER_PLUGINS_PRIVILEGED\n value: woodpeckerci/plugin-docker-buildx\n - name: WOODPECKER_LOG_LEVEL\n value: debug\n resources:\n requests:\n cpu: \"50m\"\n memory: 400Mi\n limits:\n cpu: \"1\"\n memory: 1Gi\n ports:\n - name: http\n containerPort: 8000\n protocol: TCP\n - name: grpc\n containerPort: 9000\n protocol: TCP\n volumeMounts:\n - mountPath: /var/lib/woodpecker/\n name: config\n livenessProbe:\n httpGet:\n path: /healthz\n port: 8000\n initialDelaySeconds: 30\n periodSeconds: 30\n volumes:\n - name: config\n persistentVolumeClaim:\n claimName: woodpecker-config-pvc\n```\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]",[2951,2952],{"name":2866,"color":2867},{"name":2883,"color":2884},4918,"Cannot enable new repos after upgrading from v3.1.0 to v3.2.0. Duplicate entry for key 'UQE_orgs_name'","2025-03-04T23:30:29Z","https://github.com/woodpecker-ci/woodpecker/issues/4918",0.7190932,{"description":2959,"labels":2960,"number":2962,"owner":2872,"repository":2873,"state":2943,"title":2963,"updated_at":2964,"url":2965,"score":2966},"### Component\n\nagent\n\n### Describe the bug\n\nOn an arm64 agent (Raspberry Pi 4b+), the clone step fails when the container is running in podman:\r\n\r\n```\r\n+ git init -b main\r\nInitialized empty Git repository in /woodpecker/src/git.vdx.hu/voidcontext/nix-config/.git/\r\n+ git config --global --replace-all safe.directory /woodpecker/src/git.vdx.hu/voidcontext/nix-config\r\n+ git remote add origin https://git.vdx.hu/voidcontext/nix-config.git\r\n+ git fetch --no-tags --depth=1 --filter=tree:0 origin +a4b83a869d6366bf24921b8f4f3f5836f806f57e:fatal: unable to access 'https://git.vdx.hu/voidcontext/nix-config.git/': Could not resolve host: git.vdx.hu\r\nexit status 128\r\n```\r\n\r\nThe server is on a different server (on amd64).\r\n\r\nExample: https://woodpecker.ci.vdx.hu/repos/109/pipeline/119/5\r\n\r\nThe same pipeline is successful on an amd64 agent (Kubernetes on a 3rd machine).\r\n\r\nThe issue seems to be similar to https://github.com/woodpecker-ci/woodpecker/issues/1407 which has been closed bacause of inactivity.\n\n### Steps to reproduce\n\n1) install server on amd64 machine (A)\r\n2) install agent on arm64 machine (B) using Docker backend that points to a docker compatible podman socket.\r\n3) Run pipeline\n\n### Expected behavior\n\nGit is able to resolve the host as it has a public DNS record.\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.6.0\"}\r\n```\n```\n\n\n### Additional context\n\nUnfortunately I wasn't able to test this on `next`.\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]",[2961],{"name":2866,"color":2867},3892,"Git clone step fails with \"Could not resolve host\" error when running fetch","2024-07-18T22:49:20Z","https://github.com/woodpecker-ci/woodpecker/issues/3892",0.745279,{"description":2968,"labels":2969,"number":2975,"owner":2872,"repository":2873,"state":2943,"title":2976,"updated_at":2977,"url":2978,"score":2979},"like the agent:\r\nhttps://github.com/woodpecker-ci/woodpecker/blob/205f8ecc1649ab48a9d5fb52b0ecd7b8c24abf4f/docker/Dockerfile.agent.multiarch#L21\r\n\r\nref https://docs.docker.com/engine/reference/builder/#healthcheck\r\n\r\nTODO:\r\n- [ ] add subcommand to server that can test against https://github.com/woodpecker-ci/woodpecker/blob/205f8ecc1649ab48a9d5fb52b0ecd7b8c24abf4f/server/router/router.go#L69\r\n- [ ] use subcommand in container",[2970,2971,2972],{"name":2883,"color":2884},{"name":2899,"color":2900},{"name":2973,"color":2974},"good first issue","76ea72",1943,"Add an healthcheck to server container","2023-07-25T13:55:31Z","https://github.com/woodpecker-ci/woodpecker/issues/1943",0.7466308,["Reactive",2981],{},["Set"],["ShallowReactive",2984],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fDl2mPTYOVS5qrLgm6bn8jAdxeRHzxK92arJo_SZluYM":-1},"/woodpecker-ci/woodpecker/4795"]