sdk build
Builds SDKs from your current spec and settings. In a terminal it draws a lane per language that moves through generating, verifying, packaging, installing and ready. Piped or in CI it prints plain lines instead.
It exits with an error if any language fails, so it works as a build step, and it tells you how to retry only the ones that failed. See builds.
A build that names a Studio release with --revision publishes to the package registries once it's built, unless you've turned off auto-publish for the project. A build without it never publishes on its own.
octri sdk build [--lang <languages>] [--download] [--detach]Flags
--lang <languages>listComma-separated language IDs, such as go,typescript. octri sdk languages lists them. -l is short for it.
--downloadbooleanDownloads and unpacks the SDKs once the build finishes, as sdk download does. --out sets the folder.
--detachbooleanReturns as soon as the build is queued, with its ID. --no-watch does the same.
--version <version>stringThe version the packages are built with.
--revision <number>numberThe Studio release this build is for. The build is refused if the release changed since, and it publishes once built.
--interval <ms>numberHow often to check on the build.
Examples
Build two languages and download them
octri sdk build --lang typescript,python --download --out sdksQueue a build and return
octri sdk build --lang python --detachRelated
octri sdk builds: List builds, newest first, with each one's status and languages.octri sdk watch: Follow a running build's lanes until every language settles.octri sdk download: Download a build's packages and unpack them to read the source.octri sdk retry: Run a build's failed languages again.octri sdk publish: Publish a build's packages to npm, PyPI and the other registries.