\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]",[2867,2870],{"name":2868,"color":2869},"bug","d73a4a",{"name":2871,"color":2872},"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.72286075,{"description":2882,"labels":2883,"number":2890,"owner":2874,"repository":2875,"state":2876,"title":2891,"updated_at":2892,"url":2893,"score":2894},"we currently don't have a concept how to translate/interpreter the services into \"local backend\" and just ignore them.\r\n\r\nwe should have it that way so it works very similar to what the user know with docker or kube backend.",[2884,2887],{"name":2885,"color":2886},"enhancement","7E1FE4",{"name":2888,"color":2889},"backend/local","bfdadc",3095,"Implement services for local backend","2025-02-10T13:40:24Z","https://github.com/woodpecker-ci/woodpecker/issues/3095",0.7586198,{"description":2896,"labels":2897,"number":2899,"owner":2874,"repository":2875,"state":2900,"title":2901,"updated_at":2902,"url":2903,"score":2904},"It would be nice to have an env var like `CI_COMMIT_PULL_REQUEST_LABELS` containing a list of all set labels of a PR as a comma separated string. This would allow a user to filter steps and pipelines with https://woodpecker-ci.org/docs/next/usage/pipeline-syntax#evaluate to only be executed if a specific label is set or is not set. \r\n\r\nFor example the quite time consuming task of building docker images for PRs could be skipped by default and only be activated if the corresponding label was set by a maintainer.\r\n\r\nLater with the support of label changes triggering pipelines like suggested in https://github.com/woodpecker-ci/woodpecker/issues/286#issuecomment-1116699790 a pipeline could immediately be executed in case a label got added.",[2898],{"name":2885,"color":2886},1308,"closed","Add env var with labels from PR","2023-03-17T02:43:07Z","https://github.com/woodpecker-ci/woodpecker/issues/1308",0.71881586,{"description":2906,"labels":2907,"number":2909,"owner":2874,"repository":2875,"state":2900,"title":2910,"updated_at":2911,"url":2912,"score":2913},"### Component\n\nserver\n\n### Describe the bug\n\nTrying out woodpecker, my docker-compose file:\n```\nservices:\n woodpecker-server:\n image: woodpeckerci/woodpecker-server:v3\n ports:\n - 8000:8000\n volumes:\n - woodpecker-server-data:/var/lib/woodpecker/\n environment:\n - WOODPECKER_OPEN=true\n - WOODPECKER_HOST=http://192.168.10.162:8000\n\nvolumes:\n woodpecker-server-data:\n```\n\nWhen running with `docker compose up`, I get the following:\n```\n~/projects/foss/woodpecker$ docker compose up\n[+] Running 1/1\n ✔ Container woodpecker-woodpecker-server-1 Created 0.1s \nAttaching to woodpecker-server-1\nwoodpecker-server-1 | {\"level\":\"info\",\"time\":\"2025-03-07T05:42:55Z\",\"message\":\"log level: info\"}\nwoodpecker-server-1 | {\"level\":\"warn\",\"time\":\"2025-03-07T05:42:55Z\",\"message\":\"no sqlite3 file found, will create one at '/var/lib/woodpecker/woodpecker.sqlite'\"}\nwoodpecker-server-1 | {\"level\":\"error\",\"error\":\"can't setup store: could not migrate datastore: unable to open database file: no such file or directory\",\"time\":\"2025-03-07T05:42:55Z\",\"message\":\"error running server\"}\nwoodpecker-server-1 exited with code 0\n~/projects/foss/woodpecker$ \n```\n\nAlso, I doubled checked the volume dir, and there is no files there:\n```\nroot@[REDACTED]:/var/lib/docker/volumes/woodpecker_woodpecker-server-data/_data# ls -la\ntotal 0\ndrwxr-xr-x. 1 root root 0 Mar 5 04:50 .\ndrwx-----x. 1 root root 10 Mar 7 18:37 ..\nroot@[REDACTED]:/var/lib/docker/volumes/woodpecker_woodpecker-server-data/_data# \n```\n\n\n### Steps to reproduce\n\n1. Woodperker with docker (configuration from docs) & agent entry removed. (only service)\n2. `docker compose up`\n3. Observe the error\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\nDocker version 28.0.1, build 068a01e\n```\n\n### Additional context\n\n**However**, when running with `woodpeckerci/woodpecker-server:v3-alpine` image - this issue goes away.\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]",[2908],{"name":2868,"color":2869},4939,"Fresh run with docker results in \"unable to open database file\"","2025-03-18T16:47:23Z","https://github.com/woodpecker-ci/woodpecker/issues/4939",0.7354689,{"description":2915,"labels":2916,"number":2921,"owner":2874,"repository":2875,"state":2900,"title":2922,"updated_at":2923,"url":2924,"score":2925},"on agent start, it trys to connect to the server and if it cant it stops.\r\n\r\nthere should be retry atempts, as the server could be restarting/starting in just the same moment",[2917,2920],{"name":2918,"color":2919},"agent","ECBCDF",{"name":2885,"color":2886},1721,"Agent Start should have connection retrys","2023-05-03T11:31:31Z","https://github.com/woodpecker-ci/woodpecker/issues/1721",0.7414571,{"description":2927,"labels":2928,"number":2929,"owner":2874,"repository":2875,"state":2900,"title":2930,"updated_at":2931,"url":2932,"score":2933},"### Component\n\nserver\n\n### Describe the bug\n\nI am attempting to deduplicate CI/CD code and one obvious option would be to include `.woodpecker` as Git submodule\n\n### Steps to reproduce\n\nI moved YAML files to separate repo https://git.k-space.ee/k-space/container-image-pipeline and included it as submodule https://git.k-space.ee/k-space/wildflock/commit/86d0b37713e19b66ee48187ba2e4f24fb3d4e0d2\r\n\r\nWoodpecker doesn't see any pipeline elements now\n\n### Expected behavior\n\nWoodpecker would look up YAML files in the referenced Git submodule\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.7.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]",[],4050,"Can't include .woodpecker as Git submodule","2024-08-21T05:20:15Z","https://github.com/woodpecker-ci/woodpecker/issues/4050",0.74384415,{"description":2935,"labels":2936,"number":2943,"owner":2874,"repository":2875,"state":2900,"title":2944,"updated_at":2945,"url":2946,"score":2947},"### Clear and concise description of the problem\n\nIn the [setup documentation](https://woodpecker-ci.org/docs/administration/setup#docker-compose) it reads:\r\n\r\n> Woodpecker needs to know its own address. You must therefore provide the public address of it in `\u003Cscheme>://\u003Chostname>` format.\r\n> [...]\r\n> `WOODPECKER_HOST=${WOODPECKER_HOST}`\r\n\r\nIt is not clear if `\u003Cscheme>://\u003Chostname>` must contain the http port, e.g., the default port 8000 from the compose file. The [reference](https://woodpecker-ci.org/docs/administration/server-config#woodpecker_host) is not clear about this either.\n\n### Suggested solution\n\nImprove the wording in order to clarify if the port number has to be part of the environment variable `WOODPECKER_HOST`.\n\n### Alternative\n\n_No response_\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 request the same feature to avoid creating a duplicate.",[2937,2940],{"name":2938,"color":2939},"documentation","7D625D",{"name":2941,"color":2942},"good first issue","76ea72",1437,"Improve documentation about WOODPECKER_HOST wrt. port number","2023-08-20T17:11:57Z","https://github.com/woodpecker-ci/woodpecker/issues/1437",0.7444393,{"description":2949,"labels":2950,"number":2953,"owner":2874,"repository":2875,"state":2900,"title":2954,"updated_at":2955,"url":2956,"score":2957},"### Component\n\nweb-ui\n\n### Describe the bug\n\nThe spaces in task output should be kept.\r\n\r\n\r\n\n\n### System Info\n\n```shell\n\"source\": \"https://github.com/woodpecker-ci/woodpecker\",\r\n\"version\": \"next-9feb6be9\"\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).",[2951,2952],{"name":2868,"color":2869},{"name":2871,"color":2872},718,"The spaces in task output should be kept.","2022-06-16T17:24:27Z","https://github.com/woodpecker-ci/woodpecker/issues/718",0.74660236,{"description":2959,"labels":2960,"number":2963,"owner":2874,"repository":2875,"state":2900,"title":2964,"updated_at":2965,"url":2966,"score":2967},"### Component\r\n\r\nserver, web-ui\r\n\r\n### Describe the bug\r\n\r\nDownloaded or copy-pasted logs do not have line breaks, appear as one line.\r\n\r\n### Steps to reproduce\r\n\r\n1. Install Woodpecker `2.6.0`.\r\n2. Run pipeline\r\n```yaml\r\nskip_clone: true\r\nsteps:\r\n server:\r\n image: alpine\r\n commands:\r\n - echo Hello\r\n - echo world\r\n```\r\n2. See logs in UI\r\n\r\n3. Download logs\r\n[usr-wp-test-324-server.log](https://github.com/user-attachments/files/15841307/usr-wp-test-324-server.log)\r\n4. Copy logs from UI and paste in some text editor\r\n5. Check, that downloaded logs and copy-pasted one are one-line text\r\n```\r\n+ echo HelloHello+ echo worldworld\r\n```\r\n\r\n### Expected behavior\r\n\r\n1. Install Woodpecker `2.5.0`.\r\n2. Run pipeline\r\n```yaml\r\nskip_clone: true\r\nsteps:\r\n server:\r\n image: alpine\r\n commands:\r\n - echo Hello\r\n - echo world\r\n```\r\n2. See logs in UI\r\n\r\n3. Download logs\r\n[usr-wp-test-323-server.log](https://github.com/user-attachments/files/15841256/usr-wp-test-323-server.log)\r\n4. Copy logs from UI and paste in some text editor\r\n5. Check, that downloaded logs and copy-pasted one are multiple lines\r\n```\r\n+ echo Hello\r\nHello\r\n+ echo world\r\nworld\r\n```\r\n\r\n### System Info\r\n\r\n```shell\r\nWoodpecker 2.6.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 [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]",[2961,2962],{"name":2868,"color":2869},{"name":2871,"color":2872},3790,"There is no line breaks in the Step logs","2024-06-21T08:14:01Z","https://github.com/woodpecker-ci/woodpecker/issues/3790",0.74768084,{"description":2969,"labels":2970,"number":2971,"owner":2874,"repository":2875,"state":2900,"title":2972,"updated_at":2973,"url":2974,"score":2975},"this is just a basic idea of an tool - should be maintained in an independent place (sec repo?) - that is able to convert lets say ... gitlab ci config into woodpecker and visa versa.\r\n\r\nthat way migration can be easier & we could eventaul add a plugin doing translation for woodpecker so we can run ... for example github actions.",[],377,"[Idea] CI config converter","2024-02-11T08:41:52Z","https://github.com/woodpecker-ci/woodpecker/issues/377",0.7499866,["Reactive",2977],{},["Set"],["ShallowReactive",2980],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$ftQRirIy6-wEAdeGa9yPClC6Wa7Qt0IqcivCeXcjd4XE":-1},"/woodpecker-ci/woodpecker/4935"]