Gitea does not appear in Snap store #1813

@lafriks commented on GitHub (May 23, 2018):

@lunny I already did :)

@lafriks commented on GitHub (May 23, 2018): @lunny I already did :)

GiteaMirror commented

@lunny commented on GitHub (May 23, 2018):

But gitea still cannot be searched in store?

@lunny commented on GitHub (May 23, 2018): But gitea still cannot be searched in store?

GiteaMirror commented

@lafriks commented on GitHub (May 23, 2018):

Don't know why. It shows as built & published but not when searching, might be some delay. Also version is v1.1.0+commit sha. To get normal version numbers we would need to switch develop -> master -> release/ workflow and tag versions on master

@lafriks commented on GitHub (May 23, 2018): Don't know why. It shows as built & published but not when searching, might be some delay. Also version is v1.1.0+commit sha. To get normal version numbers we would need to switch develop -> master -> release/ workflow and tag versions on master

GiteaMirror commented

@techknowlogick commented on GitHub (May 23, 2018):

I can't search either, but I am able to see: https://build.snapcraft.io/user/go-gitea/gitea

@techknowlogick commented on GitHub (May 23, 2018): I can't search either, but I am able to see: https://build.snapcraft.io/user/go-gitea/gitea

GiteaMirror commented

@techknowlogick commented on GitHub (May 23, 2018):

Per snap docs: Anybody can publish a snap, but doing a Snap Store search will only find snaps that are published to the stable release channel

@techknowlogick commented on GitHub (May 23, 2018): Per snap [docs](https://docs.snapcraft.io/core/usage): `Anybody can publish a snap, but doing a Snap Store search will only find snaps that are published to the stable release channel`

GiteaMirror commented

@lunny commented on GitHub (May 24, 2018):

@lafriks you should create a stable release channel.

@lunny commented on GitHub (May 24, 2018): @lafriks you should create a stable release channel.

GiteaMirror commented

@lafriks commented on GitHub (May 24, 2018):

But than we need to push current master branch build to stable that does not seems to be right :)

@lafriks commented on GitHub (May 24, 2018): But than we need to push current master branch build to stable that does not seems to be right :)

GiteaMirror commented

@lunny commented on GitHub (May 24, 2018):

@lafriks I haven't been familiar with Snap, don't know about that. Of course, we should not set master as stable.

@lunny commented on GitHub (May 24, 2018): @lafriks I haven't been familiar with Snap, don't know about that. Of course, we should not set master as stable.

GiteaMirror commented

@tbraeutigam commented on GitHub (May 24, 2018):

There's two options in that case:

Wait until a new release and push that from edge to stable
Do a manual build an upload it (in the snapcraft.yaml file, you can specify tags) -- this part is not automated though.

The easier option is definitely the former, and seeing how it's available (thanks! and great to see!) via edge for curious people, I think this should be fine?

@tbraeutigam commented on GitHub (May 24, 2018): There's two options in that case: - Wait until a new release and push that from edge to stable - Do a manual build an upload it (in the snapcraft.yaml file, you can specify tags) -- this part is not automated though. The easier option is definitely the former, and seeing how it's available (thanks! and great to see!) via edge for curious people, I think this should be fine?

GiteaMirror commented

@lofidevops commented on GitHub (May 24, 2018):

Speaking as a curious person, sudo snap install gitea --edge worked for me :) thanks for pointing out that it's available. If I find any issues I'll try to log them before the next release (when this issue is resolved and Gitea appears in the store for everyone).

@lofidevops commented on GitHub (May 24, 2018): Speaking as a curious person, `sudo snap install gitea --edge` worked for me :) thanks for pointing out that it's available. If I find any issues I'll try to log them before the next release (when this issue is resolved and Gitea appears in the store for everyone).

GiteaMirror commented

@popey commented on GitHub (May 27, 2018):

I was super excited to hear about gtiea being a snap! Thanks for making it. I also was curious and installed on my home server. It works great!

You might be interested to learn that we (snapcrafters ) have been putting some code in the yaml to detect whether it's time to build a stable release or just build to edge. We simply look for the most recent stable tagged release, compare it with what's in the beta channel, and decide at that point whether to git checkout the stable release or build edge. That way you can have one yaml, and build for both stable and unstable builds. If it builds a stable release, you can push that to the beta channel and ask your community to test it. if you're happy with the build, push that release to stable. Subsequent builds will be tip of master and pushed to edge, until another upstream stable release rolls around.

There's a few examples of this in the snapcrafters repo. The obs-studio one is probably simplest. The key parts to note are the override-build: which does the version detection, and version-script: which sets the version number in the snap.

Hope that's useful. Ping if you need info / help etc.

<3

@popey commented on GitHub (May 27, 2018): I was super excited to hear about gtiea being a snap! Thanks for making it. I also was curious and installed on my home server. It works great! You might be interested to learn that we ([snapcrafters](https://github.com/snapcrafters) ) have been putting some code in the yaml to detect whether it's time to build a stable release or just build to edge. We simply look for the most recent stable tagged release, compare it with what's in the beta channel, and decide at that point whether to git checkout the stable release or build edge. That way you can have one yaml, and build for both stable and unstable builds. If it builds a stable release, you can push that to the beta channel and ask your community to test it. if you're happy with the build, push that release to stable. Subsequent builds will be tip of master and pushed to edge, until another upstream stable release rolls around. There's a few examples of this in the snapcrafters repo. The [obs-studio](https://github.com/snapcrafters/obs-studio/blob/master/snap/snapcraft.yaml) one is probably simplest. The key parts to note are the `override-build:` which does the version detection, and `version-script:` which sets the version number in the snap. Hope that's useful. Ping if you need info / help etc. <3

GiteaMirror commented

@lafriks commented on GitHub (May 27, 2018):

we currently do new release/1.x branch from master and tag on that branch, so on master we do have no tags. So I seem not to find way to have built beta/stable releases from these branches to be published automatically.

@lafriks commented on GitHub (May 27, 2018): we currently do new `release/1.x` branch from master and tag on that branch, so on master we do have no tags. So I seem not to find way to have built beta/stable releases from these branches to be published automatically.

GiteaMirror commented

@techknowlogick commented on GitHub (May 27, 2018):

Perhaps we could have a drone plugin that'll do snapcraft releases? This would of course require creating a snap drone plugin first.

@techknowlogick commented on GitHub (May 27, 2018): Perhaps we could have a drone plugin that'll do snapcraft releases? This would of course require creating a snap drone plugin first.

GiteaMirror commented

@lunny commented on GitHub (May 28, 2018):

@techknowlogick seems a good idea.

@lunny commented on GitHub (May 28, 2018): @techknowlogick seems a good idea.

GiteaMirror commented

@popey commented on GitHub (Jul 5, 2018):

Heya! Any progress on this? I'd love to be able to install a stable version of gitea from the snap store soon. Anything I can do to help?

@popey commented on GitHub (Jul 5, 2018): Heya! Any progress on this? I'd love to be able to install a stable version of gitea from the snap store soon. Anything I can do to help?

GiteaMirror commented

@techknowlogick commented on GitHub (Jul 5, 2018):

@popey no progress yet, but snap has a docker image: https://hub.docker.com/r/snapcore/snapcraft/ that we could probably leverage instead of building a drone-plugin

@techknowlogick commented on GitHub (Jul 5, 2018): @popey no progress yet, but snap has a docker image: https://hub.docker.com/r/snapcore/snapcraft/ that we could probably leverage instead of building a drone-plugin

GiteaMirror commented

@lunny commented on GitHub (Jul 6, 2018):

I think @lafriks had created an account to publish gitea to snap store. When we release a stable version, we can publish it I think.

@lunny commented on GitHub (Jul 6, 2018): I think @lafriks had created an account to publish gitea to snap store. When we release a stable version, we can publish it I think.

GiteaMirror commented

@lafriks commented on GitHub (Jul 6, 2018):

@lunny not really... snapcraft builds only master branch so we can't really release stable there, only edge... If we want to build from other branches also, we need to build them manually or setup drone to do that somehow and publish to snapcraft store

@lafriks commented on GitHub (Jul 6, 2018): @lunny not really... snapcraft builds only master branch so we can't really release stable there, only edge... If we want to build from other branches also, we need to build them manually or setup drone to do that somehow and publish to snapcraft store

GiteaMirror commented

@lafriks commented on GitHub (Jul 6, 2018):

@popey if you have any ideas on how we could automatically build other branches & tags on them and publish to snap store, ideas are more than welcome

@lafriks commented on GitHub (Jul 6, 2018): @popey if you have any ideas on how we could automatically build other branches & tags on them and publish to snap store, ideas are more than welcome

GiteaMirror commented

@popey commented on GitHub (Jul 6, 2018):

Sure! For some other snaps (one I linked to above) we do some simple detection shell script magic in the snapcraft.yaml. Essentially we use snap info <snapname> to find out what version is currently published in the store. If the latest stable release (gained from the github api, wget or whatever) is higher, we use git checkout commands to get the right tagged version and build that. If the latest release is already in the beta channel then we just build the latest master branch. This allows one yaml to build both stable and unstable builds.

See the override-build section in https://github.com/snapcrafters/obs-studio/blob/master/snap/snapcraft.yaml#L38 and the version-script section above that for an example.

Something like that could work for you?

@popey commented on GitHub (Jul 6, 2018): Sure! For some other snaps (one I linked to above) we do some simple detection shell script magic in the snapcraft.yaml. Essentially we use `snap info <snapname>` to find out what version is currently published in the store. If the latest stable release (gained from the github api, wget or whatever) is higher, we use `git checkout` commands to get the right tagged version and build that. If the latest release is already in the beta channel then we just build the latest master branch. This allows one yaml to build both stable and unstable builds. See the `override-build` section in https://github.com/snapcrafters/obs-studio/blob/master/snap/snapcraft.yaml#L38 and the `version-script` section above that for an example. Something like that could work for you?

GiteaMirror commented

@lafriks commented on GitHub (Jul 6, 2018):

@popey but you are not building edge version from master than, right? Also we do not tag on master branch but on release/v1.x branches, will that work?

@lafriks commented on GitHub (Jul 6, 2018): @popey but you are not building edge version from master than, right? Also we do not tag on master branch but on `release/v1.x` branches, will that work?

GiteaMirror commented

@Follpvosten commented on GitHub (Aug 30, 2018):

I think the original issue (gitea not appearing in the snap store or when using snap find) is fixed as of now - with the current version of snapd, snap find gitea results in this:

Name   Version                    Publisher  Notes  Summary
gitea  v1.5.0-rc1+git166.b9ae16d  gitea      -      Gitea - A painless self-hosted Git service

You still have to install it using snap install --edge, but at least it's visible now.

@Follpvosten commented on GitHub (Aug 30, 2018): I think the original issue (gitea not appearing in the snap store or when using `snap find`) is fixed as of now - with the current version of snapd, `snap find gitea` results in this: Name Version Publisher Notes Summary gitea v1.5.0-rc1+git166.b9ae16d gitea - Gitea - A painless self-hosted Git service You still have to install it using `snap install --edge`, but at least it's visible now.

GiteaMirror commented