`remote-build` lacks support for selecting Snapcraft channel

Bug #2061517 reported by Michał Sawicz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snapcraft
New
Undecided
Unassigned

Bug Description

Launchpad has API to choose a channel for Snapcraft:

https://launchpad.net/+apidoc/devel.html#snap_build

> channels (writeable)
> Source snap channels to use for this build.
> A dictionary mapping snap names to channels to use for this build. Supported snap names: 'core', 'core18', 'core20', 'core22', 'core24', 'snapcraft', 'snapd'

Would be good to expose that on `remote-build`, and even better - default to whatever the local Snapcraft channel is, if possible.

Revision history for this message
Callahan Kovacs (mr-cal) wrote :

This API field is defined in https://github.com/canonical/craft-application/blob/24695b5d9df81b73e16e5728865b41edfca364e5/craft_application/launchpad/models/recipe.py#L57, but it is not exposed to snapcraft.

It will need to be exposed in craft-application and snapcraft will need to be able to set it.

The same implementation should be used for charms as well (for the `charm_recipe_build`).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.