You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If architectures are defined in a snapcraft.yaml file and provided with --build-for, launchpad will fail to create artifacts but snapcraft will exit successfully with no error messages.
Defining architectures in a snapcraft.yaml file and providing --build-for is a known issue (LP#1885150), but this bug report is about the UX - there is no validation, warning, or error message.
Possible solutions
Warn if architectures are defined in a snapcraft.yaml and provided as a build argument
Error if no artifacts are produced
Work with the launchpad team to improve how builds are planned
mr-cal
changed the title
New remote builder does not fail if launchpad fails to create artifacts
remote build: fail if launchpad fails to create artifacts
Aug 21, 2024
Bug Description
If architectures are defined in a snapcraft.yaml file and provided with
--build-for
, launchpad will fail to create artifacts but snapcraft will exit successfully with no error messages.Defining architectures in a snapcraft.yaml file and providing
--build-for
is a known issue (LP#1885150), but this bug report is about the UX - there is no validation, warning, or error message.Possible solutions
To Reproduce
snapcraft remote-build --launchpad-accept-public-upload --verbosity=trace --build-for arm64
Environment
n/a
snapcraft.yaml
Relevant log output
remote-build logs:
launchpad logs:
Additional context
No response
The text was updated successfully, but these errors were encountered: