\n\n### Steps to reproduce\n\nFirst pipeline is `quality.yml` :\n\n```yaml\nwhen:\n - event: push\n branch: master\n - event: pull_request\n\nskip_clone: true\n\nsteps:\n- name: clone\n image: bitnami/git:latest\n pull: true\n environment:\n # hidden\n commands:\n # hidden\n# other steps (install, lint, test)\n```\n\nSecond pipeline is `build.yml` :\n\n```yaml\nwhen:\n - event: tag\n\nskip_clone: true\n\nsteps:\n- name: clone\n image: bitnami/git:latest\n pull: true\n environment:\n # hidden\n commands:\n # hidden\n- name: docker \n image: woodpeckerci/plugin-docker-buildx:latest\n pull: true\n settings:\n # hidden\n```\n\nCommand to trigger on the repository is `git push && git push --tags`\n\n### Expected behavior\n\nBoth pipelines should run at the same time without cancelling each other.\n\n### System Info\n\n```shell\nWoodpecker runs on Docker, latest version (3.10) on a Debian system up to date.\n\nNon-secret server environment variables :\n\n\nWOODPECKER_MAX_WORKFLOWS=2\nWOODPECKER_BACKEND=docker\nWOODPECKER_PLUGINS_PRIVILEGED=woodpeckerci/plugin-docker-buildx\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]",[3198],{"name":3185,"color":3186},5581,"Different event gets cancelled","2025-09-30T14:56:19Z","https://github.com/woodpecker-ci/woodpecker/issues/5581",0.6924597,{"description":3205,"labels":3206,"number":3210,"owner":3188,"repository":3189,"state":3190,"title":3211,"updated_at":3212,"url":3213,"score":3214},"### Component\n\nweb-ui\n\n### Describe the bug\n\nWhen there is an error in one of the workflows , the UI does not show which file is causing the error:\r\n\r\nIn this project I have `build.yml` and `release.yml` and the UI gives me that:\r\n\r\n\r\n\r\nThe error was in workflow `release.yml` (which was not triggerd), but not in build.yml.\r\n\r\n\n\n### Steps to reproduce\n\nSchould be obvious\n\n### Expected behavior\n\nIch would like to see, which file / workflow is causing the error.\n\n### System Info\n\n```shell\nWoodpecker 2.7.3 (docker image)\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]",[3207],{"name":3208,"color":3209},"enhancement","7E1FE4",4376,"error message in UI does not point to workflow / yaml file","2024-11-14T14:27:25Z","https://github.com/woodpecker-ci/woodpecker/issues/4376",0.708313,{"description":3216,"labels":3217,"number":3222,"owner":3188,"repository":3189,"state":3223,"title":3224,"updated_at":3225,"url":3226,"score":3227},"### Component\n\nserver\n\n### Describe the bug\n\nSometimes pipeline cancellations still result in errors that will flag the pipeline as failed instead of cancelled:\r\n\r\n\r\n\n\n### Steps to reproduce\n\nHave not found a reliable way to reproduce this specific case.\n\n### Expected behavior\n\nPipeline should be marked as cancelled instead of failed.\n\n### System Info\n\n```shell\nnext-bf5405b6cc\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]",[3218,3219],{"name":3185,"color":3186},{"name":3220,"color":3221},"ui","46DEA2",4349,"closed","Cancelled pipelines marked as failed","2024-11-12T06:48:56Z","https://github.com/woodpecker-ci/woodpecker/issues/4349",0.6726222,{"description":3229,"labels":3230,"number":3235,"owner":3188,"repository":3189,"state":3223,"title":3236,"updated_at":3237,"url":3238,"score":3239},"### Component\r\n\r\nserver, agent, web-ui\r\n\r\n### Describe the bug\r\n\r\nWhen using \".woodpecker/\" directory with a workflow file (myworkflow.yml) inside, the error message: `[generic]pipeline definition not found in company/my-repo` appears (manual run).\r\n\r\nWhen using the same file (myworkflow.yml) in the root directory of the project with name \".woodpecker.yml\", the workflow is found and executed.\r\n\r\nThe documentation states that BitBucket Cloud supports multiple workflows. See [https://woodpecker-ci.org/docs/next/administration/forges/overview](https://woodpecker-ci.org/docs/next/administration/forges/overview)\r\n\r\n### System Info\r\n\r\n```shell\r\nversion\t\"next-d0e63375fa\"\r\n```\r\n\r\n\r\n### Additional context\r\n\r\n```\r\nwoodpecker-server-1 | {\"level\":\"debug\",\"time\":\"2024-04-09T07:06:55Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/router/middleware/session/repo.go:150\",\"message\":\"myuser granted &{UserID:1 RepoID:1 Repo:\u003Cnil> Pull:true Push:true Admin:true Synced:1712646369 Created:1712589724 Updated:1712646369} permission to company/my-repo\"}\r\nwoodpecker-server-1 | {\"level\":\"error\",\"error\":\"Resource not found\",\"repo\":\"company/my-repo\",\"user\":\"myuser\",\"time\":\"2024-04-09T07:06:56Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/services/config/forge.go:152\",\"message\":\"could not get folder from forge\"}\r\nwoodpecker-server-1 | {\"level\":\"error\",\"error\":\"Resource not found\",\"repo\":\"company/my-repo\",\"user\":\"myuser\",\"time\":\"2024-04-09T07:06:57Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/services/config/forge.go:152\",\"message\":\"could not get folder from forge\"}\r\nwoodpecker-server-1 | {\"level\":\"error\",\"error\":\"Resource not found\",\"repo\":\"company/my-repo\",\"user\":\"myuser\",\"time\":\"2024-04-09T07:06:57Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/services/config/forge.go:152\",\"message\":\"could not get folder from forge\"}\r\nwoodpecker-server-1 | {\"level\":\"debug\",\"repo\":\"company/my-repo\",\"error\":\"configFetcher: fallback did not find config: Resource not found\\nNo such file or directory: .woodpecker.yaml\\nNo such file or directory: .woodpecker.yml\",\"time\":\"2024-04-09T07:06:58Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/pipeline/create.go:82\",\"message\":\"error while fetching config '' in 'ci/woodpecker' with user: 'myuser'\"}\r\n```\r\n\r\nWoodpecker-UI: Pipeline Path -> empty (default)\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]",[3231,3232],{"name":3185,"color":3186},{"name":3233,"color":3234},"forge/bitbucket","E96280",3600,"BitBucket Cloud - Pipeline definition not found (when using multiple workflows, manual run)","2024-05-06T07:08:30Z","https://github.com/woodpecker-ci/woodpecker/issues/3600",0.6857332,{"description":3241,"labels":3242,"number":3243,"owner":3188,"repository":3189,"state":3223,"title":3244,"updated_at":3245,"url":3246,"score":3247},"### Clear and concise description of the problem\n\nAfter my server went offline and I made a new commit, it won't run the pipeline on the latest commit because It didn't receive the webhook. I need a way to manually re-trigger the webhook now and I can't find a feature that can do this...\n\n### Suggested solution\n\n**Trigger Pipeline** button with commit/branch id\n\n### Alternative\n\nPushing a random commit just to get it to trigger (not a good idea)\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.",[],1092,"Manually trigger pipeline on latest commit","2022-08-12T15:36:52Z","https://github.com/woodpecker-ci/woodpecker/issues/1092",0.6934775,{"description":3249,"labels":3250,"number":3251,"owner":3188,"repository":3189,"state":3223,"title":3252,"updated_at":3253,"url":3254,"score":3255},"When I tag/release two builds are executed. One of them does the `when: event: tag` part and the other does not. I think this is because one of the builds is executed because Woodpecker sees a new branch.\r\n\r\n\r\n\r\nWeirdly enough, if I add a `branches: master` the build will time out saying exit code 0 on all steps without any further info from the step execution. [Might be a separate issue]\r\n\r\nMy `.drone.yml`:\r\n```\r\npipeline:\r\n build:\r\n image: debian\r\n pull: true\r\n commands:\r\n - echo \"HALLO WELT, KANNST DU MICH HOEREN\"\r\n when:\r\n event: [push, tag]\r\n\r\n package:\r\n image: debian\r\n pull: true\r\n commands:\r\n - echo \"zap\"\r\n when:\r\n event: tag\r\n\r\n# Not working :/\r\n#branches: master\r\n```\r\n\r\nI am using Gitea as my VCS and have enabled all 4 webhook triggers in the settings.",[],274,"Duplicate pipeline execution on tag event","2021-08-31T01:00:29Z","https://github.com/woodpecker-ci/woodpecker/issues/274",0.6965925,{"description":3257,"labels":3258,"number":3262,"owner":3188,"repository":3189,"state":3223,"title":3263,"updated_at":3264,"url":3265,"score":3266},"### Clear and concise description of the problem\n\nAs a last step of my pipeline (in case of failure) i would like to report the error message of the failed build without having to wrap every single step command. My reporting pipeline step would look something like this:\r\n\r\n```yaml\r\n ...\r\n on-error:\r\n commands:\r\n - ./report_failure.sh \"CI failed\" CI_JOB_ERROR_MESSAGE\r\n when:\r\n status: failure\r\n```\n\n### Suggested solution\n\nThe `CI_JOB_ERROR_MESSAGE` or the like is what i am asking for.\n\n### Alternative\n\n_No response_\n\n### Additional context\n\nThank you!\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.",[3259],{"name":3260,"color":3261},"feature","180DBE",704,"provide reason/error message for a build failure inside the current pipeline","2023-08-20T20:34:50Z","https://github.com/woodpecker-ci/woodpecker/issues/704",0.6996629,{"description":3268,"labels":3269,"number":3271,"owner":3188,"repository":3189,"state":3223,"title":3272,"updated_at":3273,"url":3274,"score":3275},"### Component\n\nserver\n\n### Describe the bug\n\nIn woodpecker v2.3.0, custom yaml files defined in repositories are configured in woodpecker and passed to the external configuration API. This API responds with valid woodpecker workflows based on the custom yaml, allowing this workflow to execute successfully. However, woodpecker 2.4.1 introduces linting on these configured custom yaml files, resulting in failed executions due to linting errors. This change effectively inhibits our ability to upgrade our instance to v2.4.1.\n\n### System Info\n\n```shell\nVersion which works for us\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.3.0\"}\r\n---\r\nVersion with issue\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.4.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/faq#which-version-of-woodpecker-should-i-use]",[3270],{"name":3185,"color":3186},3536,"Linter errors on repos dependent on external configuration API ","2024-03-22T14:16:02Z","https://github.com/woodpecker-ci/woodpecker/issues/3536",0.69979596,{"description":3277,"labels":3278,"number":3283,"owner":3188,"repository":3189,"state":3223,"title":3284,"updated_at":3285,"url":3286,"score":3287},"### Component\n\nserver\n\n### Describe the bug\n\nWhen pipeline/step is canceled automatically it will result in failed state with error:\r\n```\r\nGet \"http://%2Fvar%2Frun%2Fdocker.sock/v1.41/containers/wp_0_8440940097353797125_clone_1/json\": context canceled\r\n```\r\n\r\nInstead on this error step should be set to state canceled and so is pipeline\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-ee9269d6\"}\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).",[3279,3280],{"name":3185,"color":3186},{"name":3281,"color":3282},"duplicate","9D1C99",1391,"Canceled pipelines/steps should have correct status","2022-11-06T02:54:38Z","https://github.com/woodpecker-ci/woodpecker/issues/1391",0.70030516,["Reactive",3289],{},["Set"],["ShallowReactive",3292],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fFKtFCwXbAsJcvh9_uIHFklYbpTA0fP8mnT6yy2Bx1_c":-1},"/woodpecker-ci/woodpecker/2579"]