-
**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:
``…
-
### 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…
-
### Component
server, other
### Describe the bug
Using this `docker-compose.yml` snippet
```yaml
server:
image: *woodpecker-server-image
restart: unless-stopped
expose:
…
-
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…
-
### 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…
-
### Clear and concise description of the problem
Currently woodpecker clones the repositories via HTTP, but some git solutions like Gitea have the option to disable HTTP and use ssh only. For cases l…
-
looking at [docker hub](https://hub.docker.com/search?q=prettier&sort=updated_at&order=desc) and [Github Packages](https://github.com/orgs/prettier/packages) I can not find an official image.
It's …
-
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
…
-
### Component
cli
### Describe the bug
When installing the CLI for version `2.1.0`, `woodpecker-cli --version` returns `version dev`. I would expect it to return `2.1.0`.
### System Info
```she…
-
With the autoscaler I am creating following docker-compose set for the agent. Somehow the agent does not start and complains about a port being already in use:
```
root-woodpecker-agent-1 | rpc e…