-
Notifications
You must be signed in to change notification settings - Fork 446
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
remote build: platform definitions cannot be parsed by Launchpad #4858
Comments
This was referenced Jun 17, 2024
4 tasks
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/CRAFT-3069.
|
4 tasks
upstream bug: https://bugs.launchpad.net/launchpad/+bug/2072622 |
4 tasks
This is mostly fixed by the upstream bug but #4994 solves scenarios with the |
mr-cal
added
the
bug
Actual bad behavior that don't fall into maintenance or documentation
label
Aug 21, 2024
mr-cal
changed the title
New remote builder fails with some platforms definitions
remote build: platform definitions cannot be parsed by Launchpad
Aug 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Description
Problem 1
Launchpad fails to parse many
platforms
definitions.We need to complete canonical/craft-platforms#5 and sync with the Launchpad team to consume that build planner.
Problem 2
The legacy remote builder would only allow snaps that could build a single artefact on a
build-on
architecture. That is an architecture could only appear once in allbuild-on
entries.The new remote builder doesn't restrict this. This is a problem because Launchpad's API appears not to distinguish between
build-on
andbuild-for
, so it is not clear Snapcraft can request builds.To Reproduce
snapcraft remote-build --platform amd64
Environment
n/a
snapcraft.yaml
Relevant log output
Additional context
No response
The text was updated successfully, but these errors were encountered: