1
0
mirror of https://github.com/woodpecker-ci/woodpecker.git synced 2025-01-23 17:53:23 +02:00
Jens Heinrich 79ea9eee35
Update server-setup.md
Add a shared socket directory instead of using an unencrypted TCP connection
2020-08-03 16:40:57 +02:00
2019-10-24 11:17:07 +02:00
2019-09-14 14:21:16 +02:00
2020-05-18 16:41:15 +01:00
2020-08-03 16:40:57 +02:00
2019-08-27 13:07:19 +02:00
2020-05-19 15:05:45 +01:00
2020-05-22 13:15:33 +02:00
2020-05-18 16:41:15 +01:00
2019-08-27 13:07:19 +02:00
2019-04-05 10:17:27 +02:00
2019-11-15 10:42:57 +01:00
2019-11-13 12:23:16 +01:00
2017-09-11 16:03:11 -07:00
2017-09-27 19:01:52 -07:00
2019-11-14 11:45:43 +01:00
2019-11-14 11:45:43 +01:00
2019-08-27 13:07:19 +02:00
2019-11-15 11:36:29 +01:00

Woodpecker

An opinionated fork of the Drone CI system.

  • Based on the v0.8 code tree
  • Focused on team usage
  • Fully Apache 2.0, no tiers

Go Report Card License

woodpecker

.woodpecker.yml

  • Place your pipeline in a file named .woodpecker.yml in your repository
  • Pipeline steps can be named as you like
  • Run any command in the commands section
# .woodpecker.yml
pipeline:
  build:
    image: debian
    commands:
      - echo "This is the build step"
  a-test-step:
    image: debian
    commands:
      - echo "Testing.."

Build steps are containers

  • Define any Docker image as context
  • Install the needed tools in custom Docker images, use them as context
pipeline:
  build:
-    image: debian
+   image: mycompany/image-with-awscli
    commands:
      - aws help

File changes are incremental

  • Woodpecker clones the source code in the beginning pipeline
  • Changes to files are persisted through steps as the same volume is mounted to all steps
# .woodpecker.yml
pipeline:
  build:
    image: debian
    commands:
      - touch myfile
  a-test-step:
    image: debian
    commands:
      - cat myfile

Plugins are straighforward

  • If you copy the same shell script from project to project
  • Pack it into a plugin instead
  • And make the yaml declarative
  • Plugins are Docker images with your script as an entrypoint
# Dockerfile
FROM laszlocloud/kubectl
COPY deploy /usr/local/deploy
ENTRYPOINT ["/usr/local/deploy"]
# deploy
kubectl apply -f $PLUGIN_TEMPLATE
# .woodpecker.yml
pipeline:
  deploy-to-k8s:
    image: laszlocloud/my-k8s-plugin
    template: config/k8s/service.yml

Documentation

https://woodpecker.laszlo.cloud

Who uses Woodpecker

Currently I know of one organization using this fork. With 50+ users, 130+ repos and more than 1100 builds a week.

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 is licensed under Creative Commons Attribution-ShareAlike 4.0 International Public License. It is a derivative work of the https://github.com/drone/docs git repository.

Description
Woodpecker is a simple yet powerful CI/CD engine with great extensibility.
Readme Apache-2.0 170 MiB
Languages
Go 86.4%
Vue 9%
TypeScript 3.3%
Makefile 0.7%
CSS 0.4%
Other 0.1%