summaryrefslogtreecommitdiff
path: root/.gitlab-ci.yml
Commit message (Collapse)AuthorAgeFilesLines
* ci: Pin to older ci templateCorey Berla2023-05-041-1/+1
| | | | | | | | The ci template was changed to run-tests during the build which causes our pipelines to fail. Revert to a previous ci template until this is sorted out See: https://gitlab.gnome.org/GNOME/citemplates/-/merge_requests/37
* ci: Make flatpak@aarch64 job manual in some casesOndrej Holy2023-01-241-1/+6
| | | | | | The flatpak@aarch64 is not allowed on other branches than master but is allowed on forks. It would be nice to allow manual run in those cases to save resources, but to allow testing aarch64-specific fixes.
* ci: Disable pages job on forksOndrej Holy2023-01-241-1/+1
| | | | | | The pages job is allowed on forks currently. It is not desired to run it there and it is going to fail there anyway. Let's explicitly disable this job on forks.
* ci: Replace only/except with rulesOndrej Holy2023-01-241-18/+14
| | | | | The only/except keywords were deprecated in favor of rules. Let's replace them with rules.
* ci: Fix $CI_DEFAULT_BRANCH usage for pages jobOndrej Holy2023-01-241-2/+2
| | | | | | | The pages job is not running currently on master. This is because `only: refs: $CI_DEFAULT_BRANCH` is not supported (e.g. see https://gitlab.com/gitlab-org/gitlab/-/issues/29591). Let's fix that using one of the suggestions from that issue.
* ci: Publish docs to nautilus pagesCorey Berla2023-01-161-0/+15
| | | | | | We are generating the docs, so lets make them accessible online. See: https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/941
* ci: Remove old incorrect commandCorey Berla2023-01-161-1/+0
|
* ci: Prefer the json manifest António Fernandes2022-12-211-1/+1
| | | This is what Builder uses.
* ci: build for aarch64Zander Brown2022-08-301-6/+21
| | | | | | | Rebase on the current flatpak-ci style/guidelines, thus enabling aarch64 builds (and publshing nautilus on gnome-nightly for aarch64) https://gitlab.gnome.org/GNOME/Initiatives/-/wikis/DevOps-with-Flatpak
* Update (or drop) the Docker image used by Flatpak jobBartłomiej Piotrowski2022-07-271-1/+0
| | | | | | The gnome-runtime-images have been recently migrated to Quay. This is already reflected in the template. Please note this MR has been created semi-automatically. If it doesn't make sense, feel free to close it.
* ci: Make the update image job work with fedora:latestOndrej Holy2021-10-111-3/+3
| | | | | For some reason, "buildah login" is not enough with fedora:latest and "buildah push --creds" needs to be used to make it work again.
* ci: Use lineup-parameters python scriptOndrej Holy2021-10-111-1/+0
| | | | | | | The lineup-parameters.c is hard to use with meson. Let's use the python rewrite from https://gitlab.gnome.org/GNOME/epiphany/-/blob/master/data/lineup-parameters instead.
* ci: Remove fedora jobOndrej Holy2021-10-111-15/+0
| | | | | | The fedora job was there before the flatpak job. But now we relies on flatpak job and the fedora job doesn't really give much benefits. It is rather waste of runners and maintainers time. Let's remove it.
* ci: Remove flatpak master jobOndrej Holy2021-10-111-17/+2
| | | | | | | The flatpak master job seems to be redundant currently. It uses the same image as flatpak devel and their .yml files are equal. The two flatpak jobs are relict from the times when GNOME SDK was unstable and broke CI often, which is no more true. Let's remove the flatpak master job.
* ci: Do not run style check on stable branchesOndrej Holy2021-10-111-0/+2
| | | | | | | | The style check job currently fails on stable branches since the recent uncrustify change. We could use older image on stable, or backport the code changes, but I think that the style check job on stable branches is not actually needed. Let's disable the style check job on stable branches to fix pipeline there and avoid this situation in the future.
* ci: Use fedora:latest instead of rawhideOndrej Holy2021-08-101-1/+1
| | | | | | There are various problems with the rawhide image currently and I don't know how to workaround them. Let's use fedora:latest (temporarily) to fix our pipeline.
* ci: Set nightly runtime repositoryAntónio Fernandes2021-03-061-1/+1
| | | | | | | | | | | | | | | It was set to flathub because we used to depend on a stable runtime. [1] We have since changed to depend on the unstable runtime[2], but the Nightly flatpakref still configures the wrong repo on installation. If the user didn't have the gnome-nightly repository configured in advance, then the runtime cannot be found, failing the installation.[3] Update the repo URL, which I should have done in [2]. [1] c4afd14696c670db8fbb64dcc4ea2f0807d25a94 [2] d95a616116bb8c02b01261afa3ed5b581f9f2e74 [3] https://blogs.gnome.org/antoniof/2021/03/05/files-40-beta-more-productivity-and-some-eye-candy/#comment-541
* Revert "ci: Use Fedora latest instead of rawhide temporarily"Bastien Nocera2020-12-111-1/+1
| | | | | | | GNOME CI runners have been updated to the latest libseccomp so the problem should no longer happen. This reverts commit ab55380f200e5ea03116c5871607d125deff844c.
* ci: Use Fedora latest instead of rawhide temporarilywip/oholy/ci-buildahOndrej Holy2020-11-201-1/+1
| | | | | | | | The pipeline currently fails with Fedora rawhide, because g-ir-scanner fails with failures like: "ldd: error: you do not have read permission for `/builds/GNOME/nautilus/_build/tmp-introspectgwhh729q/Nautilus-3.0'". This obviously affects more projects:, e.g. GNOME/grilo!62. Let's use Fedora latest for now as a workaround.
* ci: Remove broken triage jobOndrej Holy2020-11-201-20/+0
| | | | | | | | | The triage job is broken, which regularly causes CI failures. I've made some attemts to fix it but I failed. I don't have capacity to spent more time on it. Let's remove the job completely for now to prevent the confusing CI failures. Fixes: https://gitlab.gnome.org/GNOME/nautilus/-/issues/1625
* ci: Use Buildah instead of Docker to generate imagesOndrej Holy2020-11-201-11/+14
| | | | | | The GNOME runners are no more privileged and thus it is not possible to use Docker from the pipeline. Let's use Buildah instead Docker to fix the image generation.
* Revert "ci: Hardcode image version for style check job"António Fernandes2020-11-181-1/+1
| | | | | | This reverts commit 831203e9512b29900e8095c91332b49bbbf97047. The previous commit fixed the issue we were working around.
* ci: Hardcode image version for style check jobOndrej Holy2020-09-071-1/+1
| | | | | | | | | | | | | The style check job currently fails as uncrustify from rawhide obviously changed its behavior. It tries to change function pointer the following way: - gboolean (*each_function)(NautilusCanvasIcon *, gpointer), + gboolean ( *each_function )(NautilusCanvasIcon *, gpointer), I don't think this is right, but don't know how to fix that ellegantly. Note that this is because of "sp_before_ptr_star = false". Let's hardcode the previous image varsion to avoid this change for now.
* flatpak: Build all tests by defaultOndrej Holy2020-05-101-2/+0
| | | | | | | | | | The flatpak template has been changed recently and MESON_ARGS variable doesn't have any effect currently. Let's drop MESON_ARGS and move the build options into the manifests directly (ie. -Dtests=all). See: https://gitlab.gnome.org/GNOME/citemplates/blob/master/flatpak/flatpak_ci_initiative.yml https://mail.gnome.org/archives/desktop-devel-list/2020-April/thread.html
* ci: Run nightly job even if cross environment stage failsOndrej Holy2020-04-151-0/+2
| | | | | | | Currently, the nightly job is skipped if fedora rawhide, or flatpak master job fails. This is not wanted as the nightly should be published if flatpak devel job succeeds. Let's allow failures of those jobs to not block the deploy stage.
* ci: Do not show update image job on merge requestsOndrej Holy2020-04-151-1/+4
| | | | | | The update image job is always shown (under the GNOME namespace), however, fedora rawhide job is used only on master/web. So let's show this job only on master/web as well.
* ci: Run fedora rawhide job always on masterOndrej Holy2020-04-151-2/+1
| | | | | | | | The fedora job is run only on schedules and tags. The job is pretty fast now. So let's run it always on master so we know about possible breakages immediately and not after several days. Fixes: https://gitlab.gnome.org/GNOME/nautilus/-/issues/1441
* Revert "ci: Use test stage for flatpak devel job"Ondrej Holy2020-04-051-1/+0
| | | | | | | This reverts commit e7c2a0182a4ba2d6eb05fe170cc9b4d018a70feb, because the stage name doesn't have to be explicitely defined currently as it was changed directly in the template: https://gitlab.gnome.org/GNOME/citemplates/-/commit/5bffac6dfbd797291a90e705925a7a3973e4cc57
* ci: Use docker image to speed up jobsOndrej Holy2020-04-051-5/+21
| | | | | | | | Fedora and style check jobs install dependencies on each run. This causes that the pipelines take a long time. Let's use a custom docker image to not block runners for such a long time and to get the pipeline results faster. This commit also adds a new job to generate the docker image for us.
* ci: Add artifacts for style check jobOndrej Holy2020-04-051-1/+8
| | | | | It is not easy to find out why the style check job failed. Let's expose the style check job diff over artifacts to make it easier.
* ci: Add style-check jobOndrej Holy2020-04-051-0/+8
| | | | | | The whole code was reformatted using uncrustify script, but MRs are not checked using the script. Let's add style-check job to prevent wrongly formated MRs to be merged.
* ci: Fix alignment of triage jobsOndrej Holy2020-04-051-15/+15
| | | | | Triage jobs use just 2 spaces as tab size, whereas other jobs are using 4. Let's fix this.
* ci: Replace underscore by space in stage nameOndrej Holy2020-04-051-3/+3
| | | | | | The stage and job names can contain spaces and they are already used in job names. Let's replace underscore in cross_environemnt stage to make the pipeline output nicer.
* ci: Remove obsolete review jobsOndrej Holy2020-04-051-8/+0
| | | | | Teh review and stop_review jobs are no more needed as per flatpak_ci_initiative.yml comments. Let't remove them to make the file more readable.
* ci: Move code from template directly to jobOndrej Holy2020-04-051-7/+4
| | | | | The distro_test template is used only by one job. Let's move the code directly to that job to make the file more readable.
* ci: Remove dead codeOndrej Holy2020-04-051-53/+1
| | | | | | The coverage is not computed since the commit a5a405d, but .gitlab-ci.yml still contains some coverage related code which is not currently used. Let's remove that code to make it more readable.
* ci: Use test stage for flatpak devel jobOndrej Holy2020-03-091-0/+1
| | | | | | | | | | The flatpak devel job uses .pre stage currently. This seems to be the reason why pipelines are not triggered in some cases according: https://gitlab.com/gitlab-org/gitlab/issues/198518. Let's use the unused test stage instead to fix the pipeline and to make the pipeline output nicer.
* ci: Fix flatpak master jobOndrej Holy2020-03-061-0/+1
| | | | | | | | The flatpak master job fails currently. This is because it tries to rewrite artifacts from flatpak devel job which fails with permission denied error, because the runners are not more privileged. Let's use empty dependencies for flatpak master job to ensure that the artifacts from flatpak devel job are not passed in.
* flatpak: Unpin most dependenciesAntónio Fernandes2020-02-061-1/+1
| | | | | | We are near 3.36, so let's update the dependencies. gexiv2 git master is failing to build locally, so I've updated it to the latest tag that builds locally.
* CI: publish nightly buildAntónio Fernandes2019-09-301-0/+5
| | | | See https://mail.gnome.org/archives/desktop-devel-list/2019-September/msg00028.html
* CI: Update runtime reposAntónio Fernandes2019-09-281-2/+2
| | | | | | The stable org.gnome.Platform runtime has moved to flathub a while now. The nightly org.gnome.Platform runtime has recently moved to nightly.gnome.org, as per https://mail.gnome.org/archives/desktop-devel-list/2019-September/msg00028.html
* CI: drop superfluous overridesAntónio Fernandes2019-09-281-4/+1
| | | They are provided by the template we inherit from.
* flatpak: Update to 3.34 runtimeAntónio Fernandes2019-09-181-1/+1
| | | | | | | Also, bundle intltool, because the 3.34 Sdk doesn't include it but tracker-miners still depends on it. Intltool lines taken from https://github.com/flathub/shared-modules.git
* .gitlab-ci.yml: Skip pages for nowErnestas Kulik2019-04-301-2/+2
| | | | Seems that not producing output will cause failures.
* .gitlab-ci.yml: Try harder to exclude coverage reportsErnestas Kulik2019-04-301-1/+1
|
* .gitlab-ci.yml: Remove coverage report from artifactsErnestas Kulik2019-04-301-1/+1
| | | | Oversight from a5a405d669d302292cde98a0038b6a045bf596e9.
* .gitlab-ci.yml: Disable coverage reports for flatpakErnestas Kulik2019-04-141-2/+2
| | | | | | | https://gitlab.com/freedesktop-sdk/freedesktop-sdk/merge_requests/1120 https://gitlab.com/freedesktop-sdk/freedesktop-sdk/issues/740 Good to know that libgcov is useless.
* Update .gitlab-ci.ymlCarlos Soriano2019-03-211-1/+1
|
* Flatpak: Remove gtk4 manifestCarlos Soriano2019-03-211-14/+0
| | | The gtk4 branch should have the proper manifest already
* Flatpak: Use Devel profile for Master and Gtk4Carlos Soriano2019-03-211-4/+4
| | | Was giving errors in the CI and doesn't really provide much benefits
View Lorry Controller Status