Skip to main content
Version: Next ๐Ÿšง

Addon forges

If the forge you're using does not comply with Woodpecker's requirements or your setup is too specific to be added to Woodpecker's core, you can write your own forge using an addon forge.


Addon forges are still experimental. Their implementation can change and break at any time.


You need to trust the author of the addon forge you use. It can access authentication codes and other possibly sensitive information.


To use an addon forge, download the correct addon version. Then, you can add the following to your configuration:


In case you run Woodpecker as container, you probably want to mount the addon binary to /opt/addons/.

Bug reportsโ€‹

If you experience bugs, please check which component has the issue. If it's the addon, do not raise an issue in the main repository, but rather use the separate addon repositories. To check which component is responsible for the bug, look at the logs. Logs from addons are marked with a special field addon containing their addon file name.

List of addon forgesโ€‹

If you wrote or found an addon forge, please add it here so others can find it!

Be the first one to add your addon forge!

Creating addon forgesโ€‹

Addons use RPC to communicate to the server and are implemented using the go-plugin library.

Writing your codeโ€‹

This example will use the Go language.

Directly import Woodpecker's Go packages ( and use the interfaces and types defined there.

In the main function, just call "".Serve with a "".Forge as argument. This will take care of connecting the addon forge to the server.

Example structureโ€‹

package main

import (

forgeTypes ""

func main() {

type config struct {

// `config` must implement `"".Forge`. You must directly use Woodpecker's packages - see imports above.