Work with the launchpad team to design a solution (craft-platforms may help here) as this will require changes in both Snapcraft and Launchpad.
--platform and --build-for will have to support both of the following disparate behaviors:
Behavior 1: Lifecycle command
If there is a platform or architectures definition in the project metadata, --platform or --build-for should filter down the build plan.
Behavior 2: Legacy remote builder
If there is not a platforms or architectures definition in the project metadata, --platform or --build-for should define the build-for architectures for Launchpad to build.
Why it needs to get done
To improve the usability of the remote-builder.
A reoccurring complaint is that the project metadata must be edited to remote-build for a single architecture.
What needs to get done
Work with the launchpad team to design a solution (craft-platforms may help here) as this will require changes in both Snapcraft and Launchpad.
--platform
and--build-for
will have to support both of the following disparate behaviors:Behavior 1: Lifecycle command
If there is a
platform
orarchitectures
definition in the project metadata,--platform
or--build-for
should filter down the build plan.Behavior 2: Legacy remote builder
If there is not a
platforms
orarchitectures
definition in the project metadata,--platform
or--build-for
should define the build-for architectures for Launchpad to build.Why it needs to get done
To improve the usability of the remote-builder.
A reoccurring complaint is that the project metadata must be edited to remote-build for a single architecture.