Remote builds¶
Experimental
The remote-build
command is an experimental feature and therefore subject to
change.
Remote builds offload package builds to the build farm hosted by Launchpad. With remote builds, you can assemble multiple packages simultaneously and build for all supported architectures.
Remote builds are launched by running the remote-build
command. Craft Application will
upload the Git repository on the current working directory to Launchpad on your behalf,
under your account. To upload the repository to an existing Launchpad project, append
the --project
option and the project’s name. Once the remote-build
command is
entered, it will trigger builds for the Craft Application project present on the root of the
repository and continuously monitor the status of the new builds.
Note that all architectures defined in the package's project file are built – there’s currently no way to restrict the set of platforms to build remotely.
Once all builds are done (either through a successful build or a failure), the package files will be downloaded to the current directory, together with the build logs.
Prerequisites¶
In order to perform remote builds, the following conditions must be met:
You must have a Launchpad account, as the remote builds are performed on Launchpad.
The Craft Application project must be version-controlled by Git. This is because Craft Application uses a Git-based workflow to upload the project to Launchpad.
The repository hosting the Craft Application project must not be a shallow clone, because Git does not support pushing shallow clones.