remote-build

Command remote-build sends the current project to be built remotely. After the build is complete, packages for each architecture are retrieved and will be available in the local filesystem.

If the project contains a platforms or architectures key, then the project’s build plan is used. The build plan can be filtered using the --build-for argument.

If the project doesn’t contain a platforms or architectures key, then the architectures to build for are defined by the --build-for argument.

If there are no architectures defined in the project file or with --build-for, then the default behavior is to build for the host architecture of the local machine.

Interrupted remote builds can be resumed using the –recover option, followed by the build number informed when the remote build was originally dispatched. The current state of the remote build for each architecture can be checked using the –status option.

To set a timeout on the remote-build command, use the option --launchpad-timeout=<seconds>. The timeout is local, so the build on launchpad will continue even if the local instance of snapcraft is interrupted or times out.

Usage

snapcraft remote-build [options]

Options

--build-id

Specific build ID to retrieve.

--launchpad-accept-public-upload

Acknowledge that uploaded code will be publicly available.

--launchpad-timeout

Time in seconds to wait for launchpad to build.

--project

Upload to the specified Launchpad project.

--recover

Recover an interrupted build.

--build-for

Comma-separated list of architectures to build for.

--status

Display remote build status.

Global options

-h or --help

Show this help message and exit.

-q or --quiet

Only show warnings and errors, not progress.

-v or --verbose

Show debug information and be more verbose.

--verbosity

Set the verbosity level to ‘quiet’, ‘brief’, ‘verbose’, ‘debug’ or ‘trace’.

-V or --version

Show the application version and exit.