Builds turn your code into container images. They are powered by Cloud Native Buildpacks, which works with nearly any language or framework to automatically run whatever build steps are necessary for your code. Builds are started when you push code to GitHub and a trigger matches that code.
Spaceship uses Cloud Native Buildpacks to automatically detect the type of code you have in your repository and build that into a container image. Buildpacks have two important functions: the ability to detect if they apply to a code base and what actions to take to build that code into its usable form.
A Buildpack generally works with a single language, so we arrange them into stacks of Buildpacks that cover many different languages and frameworks. For instance, we have a TypeScript app and a Ruby service that run through the same Stack, despite being two very different languages with entirely different build processes.
Spaceship provides a set of Buildpack Stacks that cover the most popular languages and frameworks typically used in development today. You can choose which Stack to use from your app's Settings page.
Spaceship includes a set of 5 default Buildpack Stacks. These cover the most popular languages in use today. If you need to support a language not listed here, please get in touch.
When a build completes successfully, an image is generated on the Magic Container Registry. You can view any build page to get the URI to this image, which is in the format of [registry.onspaceship.com/team-handle/app-handle](<http://registry.onspaceship.com/team-handle/app-handle>) with a sha256 hash on the end. You can use this with Docker, Kubernetes, or other OCI-compliant container image tools.