-
### Component
agent
### Describe the bug
i am using woodpecker:next docker image and configured for my gitea instance:
```yml
# docker-compose.yml
version: '3'
networks:
put_net:
drive…
-
### Component
agent, web-ui
### Describe the bug
I was configuring `woodpecker-ci` to work with Gitea locally.
- Both are deployed on two different servers.
- Gitea has SSL
- Woodpeck…
-
The docs reference the chart being published as an OCI artifact: `oci://registry-1.docker.io/woodpeckerci/helm` but there's nothing there at the moment: https://hub.docker.com/r/woodpeckerci/helm/tags…
milas updated
6 months ago
-
### Component
server, agent
### Describe the bug
The server seems to refuse connections on port 9000, even though it says it is listening.
### System Info
```shell
2.1.1
This is running in kub…
-
After switching to the v2.1.0 docker image for woodpecker, the admin interface says to update to the current version.
![image](https://github.com/woodpecker-ci/woodpecker/assets/1147749/e976a089-ac…
-
helm pull on oci artifact fails with 401 unauthorized error with 3.13.0. The chart is hosted on azure container registry and anonymous pull is enabled on this repository. The same command worked with …
-
### Component
server, other
### Describe the bug
Using this `docker-compose.yml` snippet
```yaml
server:
image: *woodpecker-server-image
restart: unless-stopped
expose:
…
-
### Clear and concise description of the problem
Currently woodpecker clones the repositories via HTTP, but some git ssh config must use custom config.
- support custom `git config` as [ssh_config…
-
**Describe the bug**
Say you have two pipelines defined where the first clones fine but takes about an hour to finish. The default clone operation fails on the second pipeline with the message:
``…
-
Just tested it with:
```yaml
steps:
woodpecker-env:
image: ubuntu:22.04
pull: true
commands:
- env | sort
extend-env:
image: woodpeckerci/plugin-extend-env:next
…