Re: Building nightly flatpak apps in the CI
Hi again, it has been decided that the old service at sdk.gnome.org will be discontinued on October 31st. This gives you about 10 more days to migrate. Regards, Abderrahim ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Building nightly flatpak apps in the CI
On Wed, Sep 18, 2019, at 16:05, Michael Catanzaro wrote: > On Wed, Sep 18, 2019 at 8:05 pm, Abderrahim Kitouni > wrote: > > Some apps use Devel as a suffix to the app-id, some separating it > > with a dot, and some not. > > The dot is pretty important IMO, because without it the app ID just > looks silly. Compare: > > org.gnome.EpiphanyDevel > > vs. > > org.gnome.Epiphany.Devel Aesthetics aside, I would make the case for not using a dot. Your normal build and your nightly build are two separate entities. That is, your nightly build isn’t a sub-component of your normal build (in my mind). For example (and please correct me if I’m wrong), a flatpak sandbox will let you claim any DBus name that is a dot-name underneath your APP_ID. It feels weird to me that a normal flatpak could intrude on the bus namespace of its nightly build (not that it would, but still).___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Building nightly flatpak apps in the CI
Hi, Something that we forgot to mention, is that due to the moving nature of the Nightly runtime, when you migrate the please consider setting up a recurring scheduled pipeline [1] in order to rebuild your applications against the latest Runtime changes/ABI regardless if there was git activity. I suggest you make pick a weekly schedule during some random hour in the Night to avoid ddosing the runners. If your project isn't getting daily activity feel free to make set the scheduled pipeline to Nightly or even twice a day. [1] https://docs.gitlab.com/ce/user/project/pipelines/schedules.html Cheers, Jordan ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Building nightly flatpak apps in the CI
On Wednesday, September 18, 2019 11:05 PM, Michael Catanzaro wrote: > On Wed, Sep 18, 2019 at 8:05 pm, Abderrahim Kitouni > akito...@gnome.org wrote: > > > Some apps use Devel as a suffix to the app-id, some separating it > > with a dot, and some not. > > The dot is pretty important IMO, because without it the app ID just > looks silly. Compare: > > org.gnome.EpiphanyDevel > > vs. > > org.gnome.Epiphany.Devel I agree, I'd also prefer to if people took the chance to change their app ids to something that looks better like .Devel since users will have to reinstall anyway due to the migration. > Some apps use Devel as a suffix to the app-id, some separating it with a dot, and some not. Some use (Nightly) or (Developement) as either a prefix or suffix to the app name. Prefixes, Suffixes are not such a big deal since they are easy to change. I propose an emoji/ascii '☢️' Suffix that can be added with a single line straight from the flatpak-manifest, nothing else needed. (Note the space in the string) `"desktop-file-name-suffix" : " ☢️",` The plan forward would be that Nightly builds have their own Nightly icons to make it more distinct. The icons will be generated from the same .svg as the normal icon with Icon Preview [1] and committed to the repo. A lot of work has been done to achieve that in the Design Tooling Hackfests and its almost ready for mass adoption. I recall Boxes Nightly already uses [2] the new icon and could serve as an example. Ping the Design Team to get your Nightly .svgs [1] https://gitlab.gnome.org/World/design/icon-tool [2] https://gitlab.gnome.org/GNOME/gnome-boxes/blob/3d525217d637dd87c7161dfdb541a0c18e4b41b9/data/icons/hicolor/scalable/apps/org.gnome.BoxesDevel.svg Cheers, Jordan publickey - jordan@alatiera.com - 0x0BDAD30B.asc Description: application/pgp-keys ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Building nightly flatpak apps in the CI
On Wed, Sep 18, 2019 at 8:05 pm, Abderrahim Kitouni wrote: Some apps use Devel as a suffix to the app-id, some separating it with a dot, and some not. The dot is pretty important IMO, because without it the app ID just looks silly. Compare: org.gnome.EpiphanyDevel vs. org.gnome.Epiphany.Devel ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Building nightly flatpak apps in the CI
Hi again, On ر, سبتمبر 18, 2019 at 2:21 م, Abderrahim Kitouni wrote: The transition should be very easy if you're already following the DevOps with flatpak initiative [3] using the CI templates. The guide has been updated to reflect the latest changes. Here are a couple examples on what needs to be changed (see the individual commits) https://gitlab.gnome.org/GNOME/gnome-todo/merge_requests/91 https://gitlab.gnome.org/GNOME/gnome-builder/merge_requests/216 If you would like to use different build flags, or a different application id between the nightly build and the MR review builds, you can do so by using a template for the common variables, and a different job between master and non-master branches. See [4] for an example. It has been brought to my attention that we don't have a clear policy on how to use application ids and application names between different builds. Some apps use Devel as a suffix to the app-id, some separating it with a dot, and some not. Some use (Nightly) or (Developement) as either a prefix or suffix to the app name. It would be nice to agree on a convention and apply it, especially now that we're going to modify all apps. Abderrahim ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Building nightly flatpak apps in the CI
Dear GNOME developers, we currently have a collection of apps that are continuously being built [1] and published to sdk.gnome.org. We'd like to move this to the CI of individual apps so that maintainers are aware of build failures as they occur, and to free up some resources of our infrastructure. Starting today, the repositories on sdk.gnome.org are considered deprecated, and should disapear soon. (We'll be keeping it at least until 3.35.1 is released). The new home for nightly flatpak builds of apps is https://nightly.gnome.org/repo/ The repository currently contains the runtimes and a single app, Epiphany. For users, no configuration changes are needed. The gnome-nightly repository has been redirected, the flatpak remote should be updated automatically. You only need to reinstall apps from the gnome-nightly repository as they become available there. You can find the flatpakref files here [2]. The transition should be very easy if you're already following the DevOps with flatpak initiative [3] using the CI templates. The guide has been updated to reflect the latest changes. Please make sure your master branch is protected so you can use the secret token defined on the GNOME group in gitlab. If your app isn't in the GNOME group and you would like to publish the nightlies, please contact us on #release-team on IRC, and we'll work something out. If you would like to use different build flags, or a different application id between the nightly build and the MR review builds, you can do so by using a template for the common variables, and a different job between master and non-master branches. See [4] for an example. If you use a different branch name for your main developement branch (e.g. mainline), you also need to rewrite the only clause in the nightly job. [5] This builds only for x86_64 for now. i386 builds are going to be dropped, and ARM builds will need to be added later once we have an ARM CI runner we can use for apps. If you need help, please contact me or alatiera on IRC (you can find us on #gnome-hackers or #release-team). [1] https://gitlab.gnome.org/GNOME/gnome-apps-nightly [2] https://nightly.gnome.org/repo/appstream/ [3] https://gitlab.gnome.org/GNOME/Initiatives/wikis/DevOps-with-Flatpak [4] https://gitlab.gnome.org/GNOME/epiphany/commit/662b22c7560aa1fada8b853745d63fc377af7f80 [5] https://gitlab.gnome.org/GNOME/citemplates/blob/master/flatpak/flatpak_ci_initiative.yml#L132 ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
