Static Builds Overview
A workspace builds its application on every deployment: it clones the repository, runs the prepare stage and starts the services. That is right while you develop. Once a version is finished, you want an immutable artifact that goes to production as it was tested, without a rebuild, and that can be handed to other teams or shipped to other Codesphere installations without access to the source repository.
Creating a Static Build
This page explains how to prepare a landscape for export and how to run the export, from the Landscape Config Editor or through the Public API.
Consuming Static Builds
A static build artifact can be deployed in two ways: create a workspace from it to run one instance yourself, or publish it as a managed service provider so that other teams deploy it from the service catalog.