Support for Jsonnet

[netlander]

Curently using Drone CI and would be interested in switching to Woodpecker. However, all our build and release scripts are in jsonnet format and it would be impossible to migrate without that support.

Are ther any plans on the horizon for jsonnet?

[qwerty287]

Please search open issues and discussions before opening new ones.

#2254 will cover this issue. You can currently use addons to make this working already: #2254 (comment)

[6543]

( https://codeberg.org/qwerty287/woodpecker-jsonnet-addon )

[netlander]

I think I've seen the discussion before posting, the impression I had was: this solution is half baked esp. if it doesn't support private repos. The thing about "need to compile yourself" suggests the same.

We don't have Go development talent on board and hoped that a solution like the above would be implemented in a straightforwad manner.

This is the reason that I've started this conversation, feel free to close if you think this is not a conversation worth having.

[anbraten]

Actually looking at this I think it might help to do this via the config api instead of the plugin approach. That way the admin would just need to add an additional container to the docker-compose and set the config-api-url. The config api also provides the netrc credentials, so we could check for the corresponding config files. @qwerty287 What do you think? Should I give it a try or should we do it using #3268.

[qwerty287]

@anbraten

That way the admin would just need to add an additional container to the docker-compose and set the config-api-url.

I didn't write the addon as a complete, working solution, but as an example you should adapt to your needs.

If something like this is released as "ready to use", it should be possible to download a binary and update the addon env var, this does not require more effort.

The config api also provides the netrc credentials, so we could check for the corresponding config files

The addon gets them as well, but netrc data is different for every forge. E.g. bitbucket sets the login parameteras token, while others use the specifictoken` setting (not sure if this is really how it looks, but it's in this direction).

Should I give it a try or should we do it using #3268.

Feel free to do it, but I'm also fine with doing in #3268. In general, I think we should rather use addons instead of http services. With #3268, they can also be written in any language, go experts are not needed anymore.

To fix the token issue, I plan the following: The addons get the way to perform an RPC call to the server to get the user token of a repo. Maybe also some way to allow using all forge functions.

@netlander

this solution is half baked esp. if it doesn't support private repos

Yes, it is not complete. It was more meant as example you can use to adapt it to your needs.

We don't have Go development talent on board

There is also a comment in the linked discussion about this: You can also use http config services for now. Addons need a big rework - see #3268 - and when I finish this PR, it will be possible to write addons in any language.