Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Proposal to remove snapcraft builds from ipfs-cluster #593

Closed
2 of 4 tasks
hsanjuan opened this issue Oct 25, 2018 · 4 comments
Closed
2 of 4 tasks

Proposal to remove snapcraft builds from ipfs-cluster #593

hsanjuan opened this issue Oct 25, 2018 · 4 comments
Assignees
Labels
topic/meta Topic meta

Comments

@hsanjuan
Copy link
Collaborator

hsanjuan commented Oct 25, 2018

Basic information

  • Type (mark as appropiate):
    • Bug
    • Feature request
    • Enhancement

Description

Publishing snaps is a time sink for me due to their constant annoyances. Either builds break, or the credentials expire, or the store build requires manual approval, or, as now, they make us go and explain why we need classic confinement and after all the explanations they just don't seem to take action anyway (https://forum.snapcraft.io/t/classic-confinement-request-for-the-ipfs-cluster-snap/8056/8).

In the meantime, Travis is red. Actually we cannot even publish snaps on the stable channel from Travis because they only take edge when pushing from Travis, and they don't document any workaround. I am trying to setup their build pipeline but, it must be a joke, their DNS server is not there to resolve ipfs.io:

https://build.snapcraft.io/user/ipfs/ipfs-cluster/361367

We also have not much documentation about how to configure and nothing to orchestrate a snap cluster setup. Stats report 30 active devices for cluster: https://snapcraft.io/ipfs-cluster/metrics?period=6m

Ideally, we would hand this to a community member interested in maintaining this packaging format in a way that the Cluster team doesn't have to be fully commited to its maintenance, documentation and support.

@brianmcmichael you're the only person I can identify using snaps, please feel free to drop in your point of view here.

@hsanjuan hsanjuan added the topic/meta Topic meta label Oct 25, 2018
@koalalorenzo
Copy link

I honestly think that the usage would be a clear sign if it is meant to be supported. I realized recently that snaps packages (with snapcraft) are a little bit more complex and hard to support than other way to distribute apps (docker for example).

We are not going to support Snap packages on Orion 1.0 for very similar reasons! And I say this with a super sad face, but the usage is so low that we kinda don’t have to care. Our package on Siderus Debian repository has more downloads than our snap package

@brianmcmichael
Copy link
Contributor

I'm ok with this. I was using the snap because it was mentioned in the documentation and they are generally pretty easy to set up, but in production I went ahead with the precompiled binaries due to the confinement and user account management issues.

Snaps are probably better suited to traditional single-user style desktop apps anyways.

@hsanjuan
Copy link
Collaborator Author

Ok, so it looks that 0.7.0 will be the last snap (with some luck, if I managed to fix it again now). After that I will move the snap related code out of the way. I'll keep the store app and maybe transfer it later if someone wants to maintain it. Note this is a reversible decision anyway, we can decide to come back in the future.

@hsanjuan
Copy link
Collaborator Author

hsanjuan commented Nov 7, 2018

They finally approved the classic confinement. I'll leave the snap until it breaks next time. Then I'll remove it.

@ghost ghost added the status/in-progress In progress label Jan 18, 2019
@hsanjuan hsanjuan mentioned this issue Jan 18, 2019
lanzafame added a commit that referenced this issue Feb 9, 2019
@ghost ghost removed the status/in-progress In progress label Feb 9, 2019
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
topic/meta Topic meta
Projects
None yet
Development

No branches or pull requests

4 participants