-
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…
-
### Component
agent, other
### Describe the bug
I'm pretty sure that this is a bug in the plugin-git image or in my networking setup on my computer.
My git server is only available in ipv6 on my…
-
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 …
6543 updated
7 months ago
-
we have a lot of wrong links in the jsonschema linking to old v0.15.0 paths
6543 updated
5 months ago
-
This is a follow up from #97. In my testing, it looks like the extra volume mounts are added at the wrong indent level which breaks the YAML and the entire chart. If I run `helm template ...` I get YA…
-
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…
-
### Component
cli
### Describe the bug
* login as `woodpecker` admin user (via gitea) :heavy_check_mark:
* see and use API Access Token via swagger :heavy_check_mark:
* connection of `cli` to s…
-
### Component
web-ui
### Describe the bug
When a pipeline fails, it properly reports to fail to GitHub, but the Woodpecker WebUI still shows the pipeline as running.
### System Info
```shell
{"so…
-
### Component
server, agent
### Describe the bug
Web UI logs:
~~~
+ git config --global http.sslVerify false
+ git init -b main
Initialized empty Git repository in /woodpecker/src/19[2](h…