... | ... | @@ -21,7 +21,7 @@ flatpak: |
|
|
MANIFEST_PATH: "build-aux/flatpak/org.gnome.NautilusDevel.yml"
|
|
|
MESON_ARGS: "-Dprofile=Devel"
|
|
|
FLATPAK_MODULE: "nautilus"
|
|
|
RUNTIME_REPO: "https://sdk.gnome.org/gnome-nightly.flatpakrepo"
|
|
|
RUNTIME_REPO: "https://nightly.gnome.org/gnome-nightly.flatpakrepo"
|
|
|
APP_ID: "org.gnome.NautilusDevel"
|
|
|
extends: .flatpak
|
|
|
```
|
... | ... | @@ -57,6 +57,15 @@ stop_review: |
|
|
```
|
|
|
The template will create a Flatpak bundle with `flatpak build-bundle` and the runtime pointing to the value of RUNTIME_REPO variable. Once the deploy is done you will see a play button in the MR that will download the generated Flatpak bundle.
|
|
|
|
|
|
### Flatpak builds on every commit to master
|
|
|
|
|
|
The nightly builds can be published to GNOME [Nightly Flatpak Repository](https://nightly.gnome.org/gnome-nightly.flatpakrepo), by adding the following job. It will publish the build on the master branch, but only if it is marked as *protected* in gitlab.
|
|
|
|
|
|
```yaml
|
|
|
nightly:
|
|
|
extends: '.publish_nightly'
|
|
|
```
|
|
|
|
|
|
### Saving build and test logs & cache builds
|
|
|
If the CI fails, we need a way to retrieve the logs. For this we use the artifacts tool of GitLab too. The provided template exports the meson-logs.txt and the testlog.txt files as part of the artifacts.
|
|
|
|
... | ... | @@ -75,7 +84,7 @@ flatpak: |
|
|
MANIFEST_PATH: "build-aux/flatpak/org.gnome.NautilusDevel.yml"
|
|
|
MESON_ARGS: "-Dprofile=Devel"
|
|
|
FLATPAK_MODULE: "nautilus"
|
|
|
RUNTIME_REPO: "https://sdk.gnome.org/gnome-nightly.flatpakrepo"
|
|
|
RUNTIME_REPO: "https://nigthly.gnome.org/gnome-nightly.flatpakrepo"
|
|
|
APP_ID: "org.gnome.NautilusDevel"
|
|
|
extends: .flatpak
|
|
|
|
... | ... | @@ -88,6 +97,9 @@ review: |
|
|
stop_review:
|
|
|
stage: deploy
|
|
|
extends: '.stop_review'
|
|
|
|
|
|
nightly:
|
|
|
extends: '.publish_nightly'
|
|
|
```
|
|
|
|
|
|
# Parallel installation
|
... | ... | |