I’m on drone 0.8.4.
Posting here as it’s a general question as to how the params are passed into plugins. I’m brand new to go, and might write a drone plugin, but found something that I can’t seem to link up to the code.
allowed.branch.regex, I can see is brought into the plugins variable BranchRegex
What I don’t understand (unless there’s a plugin bug) is how do I track the allowed.branch.regex into the code. Presumably drone will parse the yaml file, and the git repo being used, and pass that in as a CLI parameter. However, in my yaml config I can’t seem to get a valid branch filter.
This plugin seems to use an old version of the Plugin API, as it doesn’t contain the Config section, so maybe it’s just not compatible with 0.8?
I’ve tried a few config variations including the first one I thought would work:
Most of the plugins I’ve looked at use dashes in these names, so the dots threw me thinking there was a need in the config to have the hierarchy match the dot syntax. Or if that syntax was leveraging the existing drone models.
Also you mentioned being new to Go … note that plugins are language agnostic. A plugin is just some program / script bundled in a Docker container that reads environment variables as input, writes output to stdout/stderr, and uses the exit code to signal whether or not execution was successful.
Here are some examples of plugins written in various languages: