-
### Clear and concise description of the problem
The steps to get Woodpecker running for a repo are quite involved:
1. If it's a new repo, click "Reload Repositories", so Woodpecker discover the…
-
### Clear and concise description of the problem
Woodpecker clones the repository for every pipeline, even if no step will run. Woodpecker's own CI is doing this every time on PRs, e.g. https://ci.wo…
-
We currently have plugins at:
- 11: https://github.com/orgs/woodpecker-ci/repositories?language=&q=plugin&sort=&type=all
- 16: https://codeberg.org/woodpecker-plugins
To simplify development so…
-
### Component
agent
### Describe the bug
The agent failed to pick up new jobs, reporting RPC error.
```
2:48AM INF src/shared/logger/logger.go:101 > log level: debug
2:48AM WRN src/pipel…
-
### Component
other
### Describe the bug
I have the following CI-Config:
```yaml
---
clone:
git:
image: woodpeckerci/plugin-git@sha256:7af90de3a9aa5dc93cc0d5cd2e67e28cb237d4b8e891ccacf…
-
### Component
other
### Describe the bug
https://github.com/woodpecker-ci/woodpecker/blob/23f58fc07a874c821b68fe30bb2733800e8d3301/pipeline/frontend/yaml/types/container_test.go#L29-L72 lists a lot…
-
If something goes wrong with a release, it would be good to have a way to properly recreate it.
Just deleting the GH release and tag and recreate the tag manually does not fully work as e.g. the c…
xoxys updated
4 months ago
-
### Description
I am running Gitea and Woodpecker CI. For some releases now there might be a bug in the mail address of the commit author / pusher, that gets sent to Woodpecker via the web hook.
H…
-
### Component
server
### Describe the bug
```
steps:
- name: init
image: debian
commands:
- echo "FOO=hello" >> envvars
- echo "BAR=world" >> envvars
- name: …
-
### Clear and concise description of the problem
Pressing the "Restart" button will restart all workflows. This can quite time-consuming. Often what one wants is just to restart one or two workflows …