\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]",[2892,2895],{"name":2893,"color":2894},"bug","d73a4a",{"name":2896,"color":2897},"ui","46DEA2",4677,"`tag` pipelines are missing avatar and commit title","2025-01-12T06:19:42Z","https://github.com/woodpecker-ci/woodpecker/issues/4677",0.7874994,{"description":2904,"labels":2905,"number":2913,"owner":2871,"repository":2872,"state":2873,"title":2914,"updated_at":2915,"url":2916,"score":2917},"host a list (json) at `https://api.woodpecker-ci.org/vuln/plugins.json` or so ... so we could also count the api access counts to get some estimations of server installations.\r\n\r\nalso the list should be compiled into the binary for offline/air-gapped systems and updated by the server once a day.\r\n\r\nthe list should contain:\r\n- image name and tag\r\n- if it's criticall or not (linter throw a warning or error (fail))\r\n- the reason (text to be displayed) like links to an CVE etc ...\r\n\r\nthat file should be managed within the git repo like we do with our plugin list for the website ...",[2906,2909,2910],{"name":2907,"color":2908},"server","5D7A92",{"name":2868,"color":2869},{"name":2911,"color":2912},"security","B60205",4080,"Let linter check against vulnerable plugin list","2024-11-24T23:13:46Z","https://github.com/woodpecker-ci/woodpecker/issues/4080",0.7878465,{"description":2919,"labels":2920,"number":2923,"owner":2871,"repository":2872,"state":2873,"title":2924,"updated_at":2925,"url":2926,"score":2927},"### Component\n\nweb-ui\n\n### Describe the bug\n\nText parsing of an http link printed in color on the output console adds a span tag to the HTML\n\n\n\n### Steps to reproduce\n\n- Example pipeline\n\n```yaml\n - name: test\n image: alpine:3.21\n commands:\n - NOCOLOR='\\\\033[0m'\n - BLUE='\\\\033[0;34m'\n - echo -e \"$${BLUE}https://docs.astral.sh/ruff/rules/pytest-fixture-positional-args/$${NOCOLOR}\"\n - echo \"https://docs.astral.sh/ruff/rules/pytest-fixture-positional-args\"\n```\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\n{\nsource: \"https://github.com/woodpecker-ci/woodpecker\",\nversion: \"3.0.1\"\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/versions]",[2921,2922],{"name":2893,"color":2894},{"name":2896,"color":2897},4907,"Console parsing input text for colored html link","2025-03-14T13:19:12Z","https://github.com/woodpecker-ci/woodpecker/issues/4907",0.79106224,{"description":2929,"labels":2930,"number":2932,"owner":2871,"repository":2872,"state":2933,"title":2934,"updated_at":2935,"url":2936,"score":2937},"### Component\n\nserver, agent\n\n### Describe the bug\n\nWhile trying to port some pipelines from drone to woodpecker-ci I found out, that the [drillster/drone-email](https://github.com/Drillster/drone-email) plugin is not working with woodpecker-ci.\r\n\r\nEven if the build is successful, the plugin will always send failure notifications. The reason is, that the plugin checks for `DRONE_BUILD_STATUS=='success'` (`DRONE_BUILD_STATUS` is put into the context of a template as `build.status`, the templates uses this to create the message / subject).\r\n\r\n The reason seems is that `DRONE_BUILD_STATUS` has the value `pending`. In the [docs](https://woodpecker-ci.org/docs/usage/environment) it says:\r\n\r\n| NAME | Description |\r\n|----|----|\r\n| CI_BUILD_STATUS | build status (success, failure) |\r\n\r\n`DRONE_*` environment variables are not mentioned.\r\n\r\nA simple `env | sort` reveals:\r\n```text\r\nCI_BUILD_STATUS=success\r\nCI_JOB_STATUS=success\r\nCI_PIPELINE_STATUS=success\r\nCI_STEP_STATUS=success\r\nDRONE_BUILD_STATUS=pending\r\n```\r\n\r\nIs it intended behavior that `CI_BUILD_STATUS` differs from `DRONE_BUILD_STATUS` or a bug?\r\n\r\nIf the DRONE_* environment variables are just a deprecated legacy, i can offer to fork the plugin and use the correct environment variable. For this it would be helpful, if someone explained to me the difference between `BUILD_STATUS`, `JOB_STATUS`, `PIPELINE_STATUS` and `STEP_STATUS` and when they are set.\r\n\r\n\n\n### System Info\n\n```shell\nI am using a simple docker-compose config with\r\n\r\n-compose.yml\r\nservices:\r\n woodpecker-server:\r\n image: woodpeckerci/woodpecker-server:next\r\n\r\n...\r\n\r\n woodpecker-agent1:\r\n image: woodpeckerci/woodpecker-agent:next\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).",[2931],{"name":2893,"color":2894},1416,"closed","DRONE_BUILD_STATUS environment variable not set to CI_BUILD_STATUS (makes plugin drillster/drone-email fail)","2022-11-22T22:57:14Z","https://github.com/woodpecker-ci/woodpecker/issues/1416",0.74156654,{"description":2939,"labels":2940,"number":2943,"owner":2871,"repository":2872,"state":2933,"title":2944,"updated_at":2945,"url":2946,"score":2947},"### Component\n\nserver\n\n### Describe the bug\n\nCurrently, it seems that missed cronjobs are getting executed when the instance starts up the next time. \r\n\r\nIn the environment I'm currently using Woodpecker, it is utilized to run Ansible playbooks at given times. This also includes scheduled server updates & reboots. \r\n\r\nIn the case of having the Woodpecker instance down & started up afterward, all those jobs are getting executed at once, causing servers to reboot when they absolutely should not. \r\n\r\nI'm not sure whether this is an actual bug or just how the cron feature works, though this is kind of a dangerous behavior depending on what kind of tasks are dedicated to Woodpecker. \r\n\r\nThe proposal is to either change the behavior to not run missed crons at startup or to provide a way to turn it off. \n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"1.0.0\"}\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).",[2941,2942],{"name":2907,"color":2908},{"name":2882,"color":2883},2188,"Skip missed cronjobs and add delay for cronjobs on server start","2023-08-12T08:11:27Z","https://github.com/woodpecker-ci/woodpecker/issues/2188",0.76111203,{"description":2949,"labels":2950,"number":2952,"owner":2871,"repository":2872,"state":2933,"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":2893,"color":2894},3689,"Stuck on login screen. ","2024-06-21T08:20:32Z","https://github.com/woodpecker-ci/woodpecker/issues/3689",0.77048856,{"description":2958,"labels":2959,"number":2961,"owner":2871,"repository":2872,"state":2933,"title":2962,"updated_at":2963,"url":2964,"score":2965},"### Component\n\nserver\n\n### Describe the bug\n\nGot this error :\n\n```\nwoodpecker-server | {\"level\":\"info\",\"time\":\"2025-02-13T09:36:51Z\",\"message\":\"log level: info\"}\nwoodpecker-server | {\"level\":\"error\",\"error\":\"can't setup store: could not migrate datastore: migration cron-without-sec failed: attempt to write a readonly database\",\"time\":\"2025-02-13T09:36:51Z\",\"message\":\"error running server\"}\n```\n\n### Steps to reproduce\n\nHave a 2.8.3 with docker compose up\nEdit docker compose to 3.0.0\nUp docker compose\nGot this error\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\nClient: Docker Engine - Community\n Version: 27.3.1\n\nDocker Compose version v2.32.4\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]",[2960],{"name":2893,"color":2894},4836,"Migration 2.8.3 to 3.0.0 failed - migration cron-without-sec failed","2025-02-13T14:04:04Z","https://github.com/woodpecker-ci/woodpecker/issues/4836",0.7738464,{"description":2967,"labels":2968,"number":2976,"owner":2871,"repository":2872,"state":2933,"title":2977,"updated_at":2978,"url":2979,"score":2980},"### Component\r\n\r\nserver\r\n\r\n### Describe the bug\r\n\r\nFrom 2.7.0 if I add a service container that had `WORKDIR` set in Dockerfile the service won't be able to find files via relative paths (or it expects to find files in it's current folder).\r\n\r\nWorkaround: Set `directory` manually on the service\r\n\r\n### Steps to reproduce\r\n\r\n1. Create a container that has `WORKDIR` set to something you know the contents of and set `CMD` and `ENTRYPOINT` to `ls`\r\n2. Add said container to a pipeline as a service (with no commands ofc)\r\n3. Observe the output, it should be different from `WORKDIR`'s contents.\r\n\r\n### Expected behavior\r\n\r\nWorking directory inside the container should be left alone and be the same set in the container.\r\n\r\n### System Info\r\n\r\n```shell\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.7.0\"}\r\n```\r\n\r\ndocker-compose config:\r\n\r\n```\r\nversion: '3'\r\n\r\nservices:\r\n woodpecker-server:\r\n image: woodpeckerci/woodpecker-server:v2.7.0\r\n ports:\r\n - 5000:8000\r\n - 10000:9000\r\n volumes:\r\n - ./data:/var/lib/woodpecker/\r\n - /etc/ssl/certs:/etc/ssl/certs:ro\r\n - /etc/timezone:/etc/timezone\r\n - /etc/docker/certs.d:/etc/docker/certs.d:ro\r\n environment:\r\n - WOODPECKER_OPEN=true\r\n - WOODPECKER_HOST=REDACTED\r\n - WOODPECKER_GITEA=true\r\n - WOODPECKER_GITEA_URL=REDACTED\r\n - WOODPECKER_GITEA_CLIENT=a3439c88-9061-4ce7-b3dc-64500fd5257f\r\n - WOODPECKER_GITEA_SECRET=REDACTED\r\n - WOODPECKER_GITEA_SKIP_VERIFY=true\r\n - WOODPECKER_AGENT_SECRET=REDACTED\r\n - WOODPECKER_ADMIN=Gr3qi\r\n # - WOODPECKER_LOG_LEVEL=debug\r\n - WOODPECKER_AUTHENTICATE_PUBLIC_REPOS=true\r\n #- WOODPECKER_MIGRATIONS_ALLOW_LONG=true\r\n - WOODPECKER_BACKEND_DOCKER_VOLUMES=/etc/ssl/certs:/etc/ssl/certs:ro,/etc/timezone:/etc/timezone,/etc/docker/certs.d:/etc/docker/certs.d:ro\r\n # woodpecker-agent:\r\n # image: woodpeckerci/woodpecker-agent:v2.6.0\r\n # command: agent\r\n # restart: always\r\n # depends_on:\r\n # - woodpecker-server\r\n # volumes:\r\n # - /var/run/docker.sock:/var/run/docker.sock\r\n # - /etc/ssl/certs:/etc/ssl/certs:ro\r\n # - /etc/timezone:/etc/timezone\r\n # - /etc/docker/certs.d:/etc/docker/certs.d:ro\r\n # environment:\r\n # - WOODPECKER_SERVER=woodpecker-server:9000\r\n # - WOODPECKER_AGENT_SECRET=REDACTED\r\n # - WOODPECKER_BACKEND_DOCKER_VOLUMES=/etc/ssl/certs:/etc/ssl/certs:ro,/etc/timezone:/etc/timezone,/etc/docker/certs.d:/etc/docker/certs.d:ro\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]",[2969,2972,2973],{"name":2970,"color":2971},"documentation","7D625D",{"name":2882,"color":2883},{"name":2974,"color":2975},"engine","5319e7",3993,"Service containers have their working directory changed when launched","2024-11-25T19:13:33Z","https://github.com/woodpecker-ci/woodpecker/issues/3993",0.7778127,["Reactive",2982],{},["Set"],["ShallowReactive",2985],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f3-KuOBtMAFbi-GXL9eda6rbpO2XK_l0AplmBNImx1mI":-1},"/woodpecker-ci/woodpecker/1068"]