Currently, I use a CI server to test and build a plugin for Rhino and upload it to our server.
To distribute the latest version of the plugin without needing to edit the food4rhino page every time, I use a URL rewrite to redirect
mysite.com/download/plugin.rhi to whatever the latest version is i.e.
mysite.com/download/plugin_188.8.131.52.rhi. This technique works well, but I’d like to integrate a yak release into the project (and that way have food4rhino reference the yak package rather than the server rewrite).
From what I can tell there are two challenges here:
- Get the CLI: The yak CLI is bundled with Rhino. Is there a way I can retrieve the latest version of the CLI on the server without Rhino? We use RhinoCommon from NuGet.
Authorization: Yak requires a Rhino Account login. Is there a way I can:
- Generate a longer lived access token/api key (that ideally has reduced scopes), so I can store it in the secrets for the CI server
- Provide an access token to the Yak CLI via a command
There’s a lot of appeal for us in having a non-customized server instance and installing all dependencies as part of the CI.
Has anyone got a cloud-hosted CI server creating builds for Yak?