New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flatpak & CI improvements #55
Flatpak & CI improvements #55
Conversation
53bef67
to
86931ad
Compare
I'm not ecstatic about fighting Ubuntu 18.04 to check for the different backends, but at least all backends are compiled by the Flatpak jobs. |
I'm totally ok with adding newer Ubuntu, on top of that one, there. runs-on: ubuntu-latest
container: ubuntu:21.10 For example. (Note the |
35aca14
to
0cf3dba
Compare
Note that 21.04 and 21.10 have GTK4 while 20.04 doesn't. |
0217ee1
to
7b54325
Compare
This is a common practice when dealing with in-tree manifests. We want flatpak-builder to build the current checkout, instead of pulling from the master branch.
Build all available Flatpak manifests (for GTK3, GTK4, and Qt5), and generate bundles.
This is a safer approach since it prevents apt from getting stuck waiting for human input on a CI environment.
Fix indentation. Set a pretty name.
Build it both on Ubuntu 18.04 and 20.04
7b54325
to
94ad7f4
Compare
3caf93e
to
d0a6388
Compare
d0a6388
to
0f70e59
Compare
This is roughly the limit I'm comfortable growing the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
Whats the plan for building the qt backend? |
I'm not touching anything Qt-related anymore until @grulja lands the improved |
Generate Flatpak bundles for all manifests we have in-tree.
Cleanup and increment the builds to include: