-
### Component
server
### Describe the bug
- image: woodpeckerci/woodpecker-server:next
- forge: gitea
- step to reproduce: add or remove a tag
### System Info
```shell
{"source":"htt…
-
This project is pain to fabricate through 3rd party thus proposing changes to address it.
### Expected behavior
Throw the repository at PCB manufacturers/fabricators to get quote for fabrication…
-
I have been testing woodpecker ci at codeberg. The S3 plugin did not work like this:
```
pipeline:
upload:
image: woodpeckerci/plugin-s3
secrets: [aws_access_key_id, aws_secret_access_…
-
### Clear and concise description of the problem
On GitHub Actions we use `github.event.number` to get the event number.
We use this event number for sorting and naming build artifacts.
For example…
-
Is there currently a way to share data(e.g. Environment Variables) across steps, if not is this a planned feature?
Or is there an other way to get the latest Git Tag of a Repo and use it in an other …
Tert0 updated
2 years ago
-
### Clear and concise description of the problem
When using Git LFS in a repository, the LFS data is not cloned and I'm left with textual pointers describing the objects in their place.
As a point…
-
Agent: woodpeckerci/woodpecker-agent:next (just pulled)
Error logs:
```
{"level":"error","error":"io: read/write on closed pipe","time":"2022-01-25T08:56:46Z","caller":"/src/agent/runner.go:…
-
### Gitea Version
1.15.7
### Git Version
_No response_
### Operating System
offical docker image gitea/gitea:latest
### How are you running Gitea?
Just request an oauth permission form woodpeck…
-
### Component
server
### Describe the bug
When selecting a log that doesn't exist yet, the woodpecker-server crashes.
![2022-07-31 23 43 16 ci moto9000 moe 81d54b9321b8](https://user-images.github…
-
the first step of a pipeline is the close step, if not set by pipeline config it will be added by default.
this environment should have access to Netrc variables:
https://github.com/woodpecker-ci…