build.snapcraft.io should honour target-architectures when that lands in snapcraft #556

Open
popey opened this Issue Mar 28, 2017 · 9 comments

Comments

Projects
None yet
9 participants

popey commented Mar 28, 2017

My yaml has:-
architectures: [amd64]
Because I know it fails to build on armhf, and I'm only testing on amd64, so pointless wasting cpu cycles on 40 min armhf builds.
I realise build is explicitly limited to amd64 and armhf (and currently not i386), but it would be nice if I could force not to build on armhf for example.

@evandandrea evandandrea changed the title from build.snapcraft.io ignore architectures in yaml to build.snapcraft.io ignores "architectures" field in snapcraft.yaml Apr 21, 2017

@ghost ghost added the Status: Proposal label Apr 24, 2017

@ghost ghost removed the Status: Proposal label Apr 25, 2017

I am running into the same issue for a different use case. A snapcraft.yaml that ingests a tarball from CI and said tarball is amd64 only, but there are now builds in the store for armhf and amd64.

Collaborator

evandandrea commented May 25, 2017

Also encountered here

Collaborator

cjwatson commented May 25, 2017

Sadly this isn't what the architectures field means in snapcraft.yaml. Setting that field declares that you're building a single multi-architecture snap that works on that set of architectures: you get a *_multi.snap with that set of architectures in its meta/snap.yaml. That's not at all what's wanted here.

I agree that we should have the feature of being able to declare what architectures you want the snap to be built for, but it can't be done with the existing architectures field.

Collaborator

evandandrea commented May 31, 2017

Sorry for the confusion. I just spoke with Sergio and Snapcraft will gain an option for specifying what architectures a snap should be built on:
https://lists.ubuntu.com/archives/snappy-app-devel/2016-April/000654.html

@evandandrea evandandrea changed the title from build.snapcraft.io ignores "architectures" field in snapcraft.yaml to build.snapcraft.io should honour target-architectures when that lands in snapcraft May 31, 2017

Collaborator

evandandrea commented Jun 5, 2017

Another reason for letting the developer limit the target architectures in the snapcraft.yaml, anbox's build badge shows as "failing" because it's (seemingly) not intended to work on ARM.

Collaborator

evandandrea commented Jun 5, 2017

@sergiusens, can you estimate when this might land in snapcraft?

@elopio elopio referenced this issue in ethereum/cpp-ethereum Nov 3, 2017

Merged

Update the snapcraft metadata #4640

Contributor

elopio commented Nov 3, 2017

For reference, this is the discussion in the forum:
https://forum.snapcraft.io/t/snapcraft-build-on-hint-for-builders/939

Collaborator

matthewpaulthomas commented Nov 6, 2017

Looks like the current dependency is snapcraft#1681.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment