You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Continuous Integration (CI) tools are vital for automating the testing and deployment of modern software. One such open-source tool is Woodpecker CI, a lightweight CI/CD system. Woodpecker CI is an open-source continuous integration and delivery platform that helps developers automate building, testing, and deploying their code. It is a community-driven fork and successor of the popular Drone CI project, sharing many design principles and compatibility with Drone pipelines. Traditionally, Woodpecker pipelines are written in YAML. But with the rise of programmable pipelines, we now have the flexibility to define our CI configuration using Starlark — a Python-like configuration language.
12
+
Continuous Integration tools are essential to build and test modern software automatically and regularly. Woodpecker CI is one such open-source tool, a lightweight CI/CD system. Woodpecker CI is an open-source continuous integration and delivery system that help developers in automating deployment, builds, and testing of code. It's an open-source fork and alternative to the popular Drone CI project with numerous design similarities and Drone pipeline compatibility. Traditionally, Woodpecker pipelines are YAML, but now that programmable pipelines are in vogue, we can finally have the liberty of defining our CI configuration through Starlark — a Python-ish config language.
13
13
14
-
In this blog, I’ll walk you through setting up Woodpecker CI with Traefik as a reverse proxy and integrating it with WCCS (Woodpecker CI Config Service) to convert Starlark configurations into YAML files, enabling us to write pipelines in .woodpecker.star files. Here's a high-level view of what we'll cover:
14
+
In this article, I will walk you through setting up Woodpecker CI with Traefik as a reverse proxy and [WCCS](https://github.com/opencloud-eu/woodpecker-ci-config-service/) (Woodpecker CI Config Service) to convert Starlark configurations into YAML files so that we can write pipelines in `.star` files. Here is a high-level overview of what we are going through:
15
15
16
16
- Spinning up a Woodpecker server with Traefik
17
17
@@ -23,27 +23,57 @@ In this blog, I’ll walk you through setting up Woodpecker CI with Traefik as a
23
23
24
24
By the end, you’ll be able to write CI pipelines in Starlark and dynamically convert them to YAML during runtime.
25
25
26
-
## Prepare Woodpecker secrets via .env
27
-
```console
28
-
#Your woodpecker host
29
-
WOODPECKER_HOST=https://<your-ci-server>
30
-
31
-
32
-
# GitHub OAuth Secrets
33
-
WOODPECKER_GITHUB_CLIENT=XXXXXXXXXXXXXXXX
34
-
WOODPECKER_GITHUB_SECRET=XXXXXXXXXXXXXXXXXXXXXXXX
26
+
## Setting Up Woodpecker Server and Agent
27
+
Let's start by setting up the Woodpecker server and agent services in the `docker-compose.yml` file as show below:
35
28
29
+
```yml
30
+
services:
31
+
woodpecker-server:
32
+
image: woodpeckerci/woodpecker-server:v3
33
+
environment:
34
+
- WOODPECKER_LOG_LEVEL=debug
35
+
- WOODPECKER_OPEN=false
36
+
- WOODPECKER_HOST=http://<your-ci-server>
37
+
- WOODPECKER_GITHUB=true
38
+
- WOODPECKER_GITHUB_CLIENT=xxxxxxx # GitHub OAuth client ID
Woodpecker cannot do anything by itself, it needs a forge (the service where the repositories are hosted). Woodpecker supports [various forges](https://woodpecker-ci.org/docs/administration/configuration/forges/overview), for this blog we will focus on GitHub.
149
+
136
150
To connect GitHub with Woodpecker:
137
151
138
-
1. Register a new OAuth application in your GitHub developer settings.
152
+
1. Register a new OAuth application in your GitHub developer [settings](https://github.com/settings/applications/new).
153
+
154
+
2. In your GitHub OAuth App, set the authorization callback URL to `https://<your-ci-server>/authorize`
139
155
140
-
2. Set the callback URL to `https://<your-ci-server>/authorize`
Before enabling a repo in the Woodpecker CI server, make sure to have a GitHub repository ready. You can use an existing repo of your own or create a new empty one. We will be making a pull request to the repo to trigger CI later.
- Enable it. For this blog, I am using an existing repo called `Drum-KIT` which has already been enabled(as you can see in the last row of the image below).
- Then, add `.woodpecker.star` as pipeline config path and save it:
201
+
Now that you have your `.woodpecker.yaml` file ready, you can commit and push it to your enabled GitHub repository and then, open a Pull Request from your branch <your-branch-name> to `master/main` according to you repo. GitHub's default branch is set to `main`.
202
+
Once the PR is created, Woodpecker will automatically fetch the pipeline configuration, and start your first CI run. You can then head over to the Woodpecker UI to watch the build logs in real time.
Every request sent by Woodpecker is signed using a http-signature by a private key (ed25519) generated on the first start of the Woodpecker server. You can get the public key for the verification of the http-signature from:
176
-
```console
177
-
http(s)://your-ci-server/api/signature/public-key
178
-
```
179
-
Store that public key into `keys/public.pem` in the same directory level as your docker compose, it will be needed for signature verification.
206
+
Now that we have already set up the woodpecker server and triggered pipelines using the traditional `.yaml` configuration, let's now integrate WCCS to unlock flexibility and define our pipelines in Starlark.
180
207
181
208
## Setting Up WCCS-Woodpecker CI Config Service (Starlark Conversion Service)
182
209
The Woodpecker Config Conversion Service (WCCS) is a lightweight web service created and maintained by [Opencloud-eu](https://opencloud.eu/en). It enables Woodpecker CI to convert pipeline definitions written in Starlark into standard YAML on the fly by receiving a signed POST request from Woodpecker.
183
210
You can easily deploy WCCS using their official Docker image available on Docker Hub: [opencloudeu/wccs](https://hub.docker.com/r/opencloudeu/wccs).
211
+
Update your `docker-compose.yml` to include the WCCS service:
184
212
```yml
213
+
...
214
+
185
215
wccs:
186
216
image: opencloudeu/wccs:latest
187
217
container_name: wccs
188
218
command: server
189
219
environment:
190
220
- WCCS_LOG_LEVEL=debug
191
-
- WCCS_SERVER_PUBLIC_KEY=/keys/public.pem
221
+
- WCCS_SERVER_PUBLIC_KEY=/keys/public.pem# path to public key(generated in the section below)
192
222
volumes:
193
223
- /opt/woodpecker/keys:/keys
194
224
- /etc/ssl/certs:/etc/ssl/certs:ro
@@ -201,6 +231,8 @@ You can easily deploy WCCS using their official Docker image available on Docker
201
231
networks:
202
232
- woodpecker-net
203
233
234
+
...
235
+
204
236
volumes:
205
237
woodpecker-server-data:
206
238
woodpecker-agent-config:
@@ -210,15 +242,38 @@ networks:
210
242
driver: bridge
211
243
```
212
244
245
+
## Generating the Public Key
246
+
Before running any pipeline, woodpecker server sends a POST request to an external config service (in our case WCCS) with all current config file and build information of the current repository. The external service takes the information and sends back the pipeline configurations. In our case, this is how a starlark file is being converted into yaml configurations.
247
+
248
+
And before WCCS can accept and process those requests, it needs to verify that the requests are trusted and coming from the woodpecker server.
249
+
250
+
Every request sent by Woodpecker is signed using a http-signature by a private key (ed25519) generated on the first start of the Woodpecker server. You can get the public key for the verification of the http-signature from:
251
+
```console
252
+
https://<your-ci-server>/api/signature/public-key
253
+
```
254
+
Store that public key into `keys/public.pem` in the same directory level as your docker compose. The `public.pem` file is then mounted to the WCCS container as shown in the snippet above and used in env variable `WCCS_SERVER_PUBLIC_KEY`
255
+
213
256
## Connecting WCCS with Woodpecker
214
257
To allow Woodpecker to fetch pipeline configs from WCCS, we added this to the server env:
Woodpecker now sends a signed JSON payload to WCCS whenever a build is triggered. WCCS verifies the signature using the public key and responds with a YAML pipeline based on your .woodpecker.star file.
261
+
Woodpecker now sends a signed JSON payload to WCCS whenever a build is triggered. WCCS verifies the signature using the public key and responds with a YAML pipeline based on your `.woodpecker.star` file.
262
+
263
+
After conneting WCCS with the woodpecker server, there's one more thing that you need to do i.e. to set pipeline config path, because by default Woodpecker will take `.woodpecker.yaml` as it's pipeline configuration.
264
+
265
+
- From the settings of your Woodpecker server, go to `Repositories` and click on the enabled repo's settings icon as shown below:
Here's a simple `.woodpecker.star` example that you can add in your project's root and you're all set:
274
+
Here's a simple starlark pipeline configuration example that you can add in your project.
275
+
Create a new branch by checking out from your `master/main` branch.
276
+
Add the following configration in the `.woodpecker.star` file in your repo's root
222
277
```console
223
278
def main(ctx):
224
279
return [{
@@ -232,16 +287,16 @@ def main(ctx):
232
287
],
233
288
"when": {
234
289
"event": ["push", "pull_request"],
235
-
"branch": ["master"],
290
+
"branch": ["master"], # configure it as your repo's base branch.(in my case, it's `master`)
236
291
},
237
292
}
238
293
]
239
294
}]
240
295
```
241
296
242
-
## Triggering Your First CI Run
243
-
Now that you have your `.woodpecker.star` file ready, commit and push it to your GitHub repository and then, open a Pull Request from your branch <your-branch-name> to master.
244
-
Once the PR is created, Woodpecker will automatically send the build request to WCCS, fetch the pipeline config, and start your first CI run. You can head over to the Woodpecker UI to watch the build logs in real time.
297
+
## Triggering CI with starlark-powered pipeline
298
+
Now that you have your `.woodpecker.star` file ready, commit and push it to your GitHub repository and then, open a new Pull Request from your branch <your-branch-name> to master/main.
299
+
Once the PR is created, Woodpecker will automatically send a build request to WCCS, fetch the pipeline configuration, and start your first CI run. You can then head over to the Woodpecker UI to watch the build logs in real time.
0 commit comments