e95aaaa8de
This is a follow up on #1379 and #1381, after fixing those (I noticed them while building a pipeline for one of my projects) I took a deep dive into the schema, and consolidated the functionality as far as possible. As a reference, I matched it against pipeline/frontend/yaml/constraint//constraints.go of the release/v0.15 branch. The .branches while not in the pipeline uses the Type (List) and functions of pipeline/frontend/yaml/constraint//constraints.go Regarding the formatting i went with what was already there, since enabling editorconfig / formatting would have changed most of the file (not that there is too much untouched after this anyways)
Woodpecker
Woodpecker is a community fork of the Drone CI system.
Support
Please consider to donate and become a backer. 🙏 [Become a backer]
Usage
.woodpecker.yml
- Place your pipeline in a file named
.woodpecker.ymlin your repository - Pipeline steps can be named as you like
- Run any command in the commands section
Build steps are containers
- Define any Docker image as context
- Install the needed tools in custom Docker images, use them as context
Plugins
Woodpecker has official plugins, but you can also use your own.
Documentation
Contribution
Who uses Woodpecker?
Codeberg, the woodpecker project itself, and many others.
Leave a comment if you're using it.
Also consider using the topic WoodpeckerCI in your repository, so others can learn
from your config and use the hashtag #WoodpeckerCI when talking about the project on social media!
Here are some places where people mention Woodpecker:
Stars over time
License
Woodpecker is Apache 2.0 licensed with the source files in this repository having a header indicating which license they are under and what copyrights apply.
Files under the docs/ folder are licensed under Creative Commons Attribution-ShareAlike 4.0 International Public License.