It would be nice if we could have a step type that allowed us to run containers with unchanged entrypoints (not setting it to sh, or other shell) and have the ability to pass environment variables to the containers (like docker -e). That would allow us to use Drone/Woodpecker/Vela plugins, as they are just containers with specific entrypoints configured by environment variables, like:

• CI_* for Woodpecker
• DRONE_* for Drone and
• PARAMETER_* for Vela

You would not need to support those plugins, as they are written for different tools, but allowing users to run container's entrypoint unchanged and passing environment variable would already allow us to use it and write our own plugins for using with Onedev.

Additionally, if you want to, you could write a guide and have your own config style for plugins in Onedev's build spec, like:

Drone uses a settings array, that internally, get converted to environment like:

- name: notify
  image: plugins/slack
  settings:
    channel: developers
    username: drone

Get converted to DRONE_CHANNEL=developers and DRONE_USERNAME=drone

Similarly, Woodpekcer (a Drone fork) convert settings array to CI_* env vars. Vela do the same thing but name the array as parameters instead of settings. So, additionally to environment variables input field, Onedev could have a settings field in the build spec that gets passed to containers as something like ONEDEV_USERNAME=onedev.