\n\nAnd here is the outcome on BitBucket:\n\u003Cimg width=\"479\" height=\"182\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/11c2a65d-cbf2-4162-9805-3d035bdac04e\" />\n\n\n### Steps to reproduce\n\n1. Run Woodpecker with BitBucket Cloud forge\n2. Create a pipeline that uses a matrix\n3. Let the pipeline finish on Woodpecker\n4. Observe the build statuses on the commit in BitBucket\n\n### Expected behavior\n\nBoth pipelines should show completed.\n\n### System Info\n\n```shell\nWoodpecker version: v3.8.0\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]",[3019],{"name":3020,"color":3021},"bug","d73a4a",5338,"woodpecker-ci","woodpecker","open","Build status not completing on matrix pipelines with BitBucket","2025-07-17T18:03:12Z","https://github.com/woodpecker-ci/woodpecker/issues/5338",0.7207858,{"description":3031,"labels":3032,"number":3039,"owner":3023,"repository":3024,"state":3025,"title":3040,"updated_at":3041,"url":3042,"score":3043},"### Component\r\n\r\nserver\r\n\r\n### Describe the bug\r\n\r\nThis is further to the discussion on [discord](https://discord.com/channels/838698813463724034/911685405546524722/1132977506362855424).\r\n\r\nMy publish step (using `woodpeckerci/plugin-docker-buildx`) was correct, yet still yielded this error:\r\n> ERROR: tag is needed when pushing to registry\r\n\r\nI spent hours going over every little thing in my config. No one on the discord channel could figure it out either.\r\n\r\nFinally I discovered the problem:\r\n```yml\r\n publish:\r\n image: woodpeckerci/plugin-docker-buildx\r\n settings:\r\n password:\r\n from_secret: publish-to-registry\r\n tags: [latest, 1.2.3] # \u003C----- I did specify tags\r\n # ...\r\n when:\r\n event: tag\r\n```\r\nThe `publish-to-registry` global secret had the `manual` and `push` scopes, but not `tag`.\r\n\r\nSo the error log was misleading.\r\n\r\nI hope it can be fixed so it doesn't waste other peoples' time, and cause more repo issues (unnecessary work for you :smile:).\r\n\r\n### System Info\r\n\r\n```shell\r\nnext-b3c2bb2e (latest)\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).",[3033,3036],{"name":3034,"color":3035},"server","5D7A92",{"name":3037,"color":3038},"enhancement","7E1FE4",2032,"Incorrect error for buildx plugin and global secret of insufficient scope","2023-07-26T02:44:15Z","https://github.com/woodpecker-ci/woodpecker/issues/2032",0.7242371,{"description":3045,"labels":3046,"number":3051,"owner":3023,"repository":3024,"state":3025,"title":3052,"updated_at":3053,"url":3054,"score":3055},"### Component\n\ncli\n\n### Describe the bug\n\nRunning a pipeline directly like this:\r\n\r\n```console\r\n$ woodpecker exec .woodpecker/ubuntu.yml\r\n...\r\n[build:L188:17s] + ./get-deps.sh\r\n[build:L189:17s] /bin/sh: 30: ./get-deps.sh: not found\r\n```\r\n\r\nfails to mount the repo, so fails to run the `get-deps.sh` script that is present in the repo.\r\n\r\nHowever, running it like this:\r\n\r\n```console\r\n$ woodpecker exec .\r\n# ci.yml\r\n\r\n# ci.yml\r\n\r\n# rust.yml\r\n\r\n# ci.yml\r\n\r\n# ci.yml\r\n\r\n# ci.yml\r\n\r\n# ci.yml\r\n\r\n# ci.yml\r\n\r\n# codecov.yml\r\n\r\n# audit.yaml\r\n\r\n# benchmarks.yaml\r\n\r\n# coverage.yaml\r\n\r\n# test.yaml\r\n\r\n# ci.yml\r\n\r\n# FUNDING.yml\r\n...\r\n```\r\n\r\nworryingly enumerates all the various yaml files in my working copy (those shown are from misc .cache and .github directories) as shown above, as if it were trying to run those, but does mount the repo and is able to run the script from inside it.\r\n\r\nMy expectation is that I can specify the pipeline I want to run based on the `--help` output:\r\n\r\n```console\r\n$ woodpecker exec --help\r\n...\r\nUSAGE:\r\n woodpecker-cli exec [command options] [path/to/.woodpecker.yaml]\r\n```\r\n\r\nand have the repo mounted in the pipeline at the same time.\r\n\n\n### System Info\n\n```shell\n$ woodpecker --version\r\nwoodpecker-cli version 1.0.2\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).",[3047,3048],{"name":3020,"color":3021},{"name":3049,"color":3050},"cli","1d76db",2511,"`woodpecker exec .woodpecker/ubuntu.yml` has no repo available","2024-07-03T03:54:28Z","https://github.com/woodpecker-ci/woodpecker/issues/2511",0.72517353,{"description":3057,"labels":3058,"number":3060,"owner":3023,"repository":3024,"state":3025,"title":3061,"updated_at":3062,"url":3063,"score":3064},"### Component\n\nserver\n\n### Describe the bug\n\nWhen you are not a Woodpecker admin https://ci.woodpecker-ci.org/orgs/2 gives an error.\r\nThe UI shows it as `An unknown error occurred` in a flash message with a red background.\r\nThe network fan shows a call to https://ci.woodpecker-ci.org/api/orgs/2 returning 401 Unauthorized\r\n\r\nAs an admin it returns \r\n```\r\n{\"id\":2,\"name\":\"woodpecker\",\"is_user\":true}\r\n```\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-a28e2e1920\"}\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).",[3059],{"name":3037,"color":3038},2983,"Allow to view (public) repos from other orgs (if not an admin)/users","2024-01-02T09:31:58Z","https://github.com/woodpecker-ci/woodpecker/issues/2983",0.72671854,{"description":3066,"labels":3067,"number":3072,"owner":3023,"repository":3024,"state":3073,"title":3074,"updated_at":3075,"url":3076,"score":3077},"https://ci.woodpecker-ci.org/woodpecker-ci/woodpecker/build/2073/29\r\n\r\n(If step is exec manually it works | that's how 0.15.0 was released)",[3068,3069],{"name":3020,"color":3021},{"name":3070,"color":3071},"build","6AB8BA",792,"closed","github token is not passed to helm chart releaser","2022-04-14T06:58:29Z","https://github.com/woodpecker-ci/woodpecker/issues/792",0.6461466,{"description":3079,"labels":3080,"number":3082,"owner":3023,"repository":3024,"state":3073,"title":3083,"updated_at":3084,"url":3085,"score":3086},"### Component\n\nother\n\n### Describe the bug\n\nWhen trying to add the Helm repo as described in the docs, it doesn't work:\r\n\r\n```\r\n$ helm repo add woodpecker https://woodpecker-ci.org/\r\nError: looks like \"https://woodpecker-ci.org/\" is not a valid chart repository or cannot be reached: failed to fetch https://woodpecker-ci.org/index.yaml : 404 Not Found\r\n```\n\n### System Info\n\n```shell\nHelm: version.BuildInfo{Version:\"v3.5.4\", GitCommit:\"1b5edb69df3d3a08df77c9902dc17af864ff05d1\", GitTreeState:\"clean\", GoVersion:\"go1.15.11\"}\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).",[3081],{"name":3020,"color":3021},507,"Helm Repo: https://woodpecker-ci.org/index.yaml : 404 Not Found","2022-02-06T15:20:22Z","https://github.com/woodpecker-ci/woodpecker/issues/507",0.6987856,{"description":3088,"labels":3089,"number":3094,"owner":3023,"repository":3024,"state":3073,"title":3095,"updated_at":3096,"url":3097,"score":3098},"- [x] Changed file filter shuld be ignored on tag event\r\n see: https://ci.woodpecker-ci.org/woodpecker-ci/woodpecker/build/1707/7\r\n => #698\r\n- [x] Gitea with multible commits have dublicated changed files\r\n- [x] building binaries is missing / broken after #622 , #635 & #634 \r\n- [ ] ~~link docker images to release~~ -> manual / maintainer docu / template ...\r\n- [x] pipeline for latest release branch",[3090,3091],{"name":3020,"color":3021},{"name":3092,"color":3093},"pipeline-config","1BE540",684,"Issues from rc1 run","2022-01-31T14:50:58Z","https://github.com/woodpecker-ci/woodpecker/issues/684",0.7024724,{"description":3100,"labels":3101,"number":3102,"owner":3023,"repository":3024,"state":3073,"title":3103,"updated_at":3104,"url":3105,"score":3106},"### Component\n\ncli\n\n### Describe the bug\n\ndocumentation is a bit spares so it's hard to tell what the expected behavior here is but I'm in a situation where one repo has never had a job run against it, and the `woodpecker-cli build start` won't run without providing a `build #`\r\n\r\n```\r\n$ woodpecker-cli build start --help\r\n10:52AM ??? github.com/woodpecker-ci/woodpecker/cli/common/zerologger.go:20 > LogLevel = trace\r\nNAME:\r\n woodpecker-cli build start - start a build\r\n\r\nUSAGE:\r\n woodpecker-cli build start [command options] \u003Crepo/name> [build]\r\n```\r\n\r\nHere `[build]` implies the build number is optional but when ran without an error is thrown.\r\n\r\n```\r\n$ woodpecker-cli build start morgan/thatrepo\r\n10:53AM FTL github.com/woodpecker-ci/woodpecker/cmd/cli/main.go:69 > error running cli error=\"missing job number\"\r\n```\r\n\r\nBut then, if a job number is included, it 404s because no job actually exists yet.\r\n\r\n```\r\n$ woodpecker-cli build start morgan/thatrepo 0\r\n10:54AM FTL github.com/woodpecker-ci/woodpecker/cmd/cli/main.go:69 > error running cli error=\"client error 404: \"\r\n```\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"0.15.4\"}\r\n```\n```\n\n\n### Additional context\n\nnote: I did not actually complete the last validation step, discord and matrix as are both VC backed non-public forums that do not hold user interest in their operational priorities.\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).",[],1215,"cannot launch first job with CLI / woodpecker-cli build start requires job build #","2022-10-11T16:20:13Z","https://github.com/woodpecker-ci/woodpecker/issues/1215",0.70897585,{"description":3108,"labels":3109,"number":3111,"owner":3023,"repository":3024,"state":3073,"title":3112,"updated_at":3113,"url":3114,"score":3115},"### Component\n\nother\n\n### Describe the bug\n\nAfter 2.6.0 release helm chart archive 1.5.0 got missing.\r\n\r\n\n\n### Steps to reproduce\n\nGet latest helm chart\r\n\r\n helm fetch --repo https://woodpecker-ci.org/ woodpecker\r\n\r\nGot result:\r\n\r\n Error: failed to fetch https://github.com/woodpecker-ci/woodpeckerci.github.io/releases/download/helm-woodpecker-1.5.0/woodpecker-1.5.0.tgz : 404 Not Found\r\n\n\n### Expected behavior\n\nHelm chart should be downloaded. \r\n\r\nI've checked docs on https://github.com/woodpecker-ci/helm/blob/main/charts/woodpecker/README.md to make sure I'm using correct helm repository.\n\n### System Info\n\n```shell\nprobably not important.\r\n\r\nHelm version: is 3.11.1, running on Fedora Linux on x86\r\n\r\nversion.BuildInfo{Version:\"v3.11.1\", GitCommit:\"293b50c65d4d56187cd4e2f390f0ada46b4c4737\", GitTreeState:\"clean\", GoVersion:\"go1.18.10\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]",[3110],{"name":3020,"color":3021},3937,"Helm Chart archive unavailable after 2.6.0 release ","2024-07-19T07:19:47Z","https://github.com/woodpecker-ci/woodpecker/issues/3937",0.71876967,{"description":3117,"labels":3118,"number":3123,"owner":3023,"repository":3024,"state":3073,"title":3124,"updated_at":3125,"url":3126,"score":3127},"### Component\n\nweb-ui\n\n### Describe the bug\n\nI am attempting to use Woodpecker to build an image using the [Cypress Factory](https://hub.docker.com/r/cypress/factory/) docker image that can be used with docker args to generate a container with specific package versions. I am using the woodpecker docker buildx plugin to build the image.\r\n\r\nWhen I run my build job and view the progress in the UI it appears the job is stuck installing GPG keys. However, when I look at the log output on the agent I can see that the GPG key installations are successful and the rest of the job steps are executed and the final image is published.\r\n\r\nAdditionally, the UI never marks the job as completed and the kubernetes builds pods stayed in a 'Completed' state until the job times out or is manually cancelled. When this happens the agents no longer pull new work from the server.\n\n### Steps to reproduce\n\n1. Create a Dockerfile using the Cypress factory image\r\n```\r\nARG NODE_VERSION='18.16.0'\r\nARG YARN_VERSION='1.22.19'\r\nARG CYPRESS_VERSION='13.7.1'\r\nARG CHROME_VERSION='120.0.6099.71-1'\r\nARG EDGE_VERSION='120.0.2210.61-1'\r\nARG FIREFOX_VERSION='120.0.1'\r\n\r\nFROM cypress/factory\r\n```\r\n2. Create a woodpecker job to build the image\r\n```\r\nsteps:\r\n - name: docker-cypress\r\n image: woodpeckerci/plugin-docker-buildx\r\n secrets: [docker_username, docker_password]\r\n settings:\r\n platforms: linux/amd64\r\n registry: \u003Cmy_docker_registry>\r\n repo: \u003Cmy_docker_repo>\r\n dockerfile: Dockerfile.cypress.test\r\n tags: buildx.test-build\r\n username:\r\n from_secret: docker_username\r\n password:\r\n from_secret: docker_password\r\n build_args_from_env:\r\n - CI_REPO\r\n - CI_COMMIT_BRANCH\r\n - CI_COMMIT_SHA\r\n - CI_PIPELINE_NUMBER\r\n debug: true\r\n```\r\n3. Run the job\r\n\n\n### Expected behavior\n\n* The job should successfully build the container and be marked Successful\r\n* The UI log output should stay in sync with the worker agent log output\r\n* The UI should not hang indefinitely during the build\n\n### System Info\n\n```shell\n{\r\n\"source\": \"https://github.com/woodpecker-ci/woodpecker\",\r\n\"version\": \"2.4.1\"\r\n}\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]",[3119,3120],{"name":3020,"color":3021},{"name":3121,"color":3122},"ui","46DEA2",3716,"Woodpecker UI output not updating/out of sync","2024-06-13T15:18:35Z","https://github.com/woodpecker-ci/woodpecker/issues/3716",0.72685415,["Reactive",3129],{},["Set"],["ShallowReactive",3132],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fId-YrFf_ylWcv6jEoeiNxsrNbp-wj5nW2T_-Q1j7VcU":-1},"/woodpecker-ci/woodpecker/739"]