| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
The gnome-nightly-oci registry was moved to gitlab.gnome.org, so we
need to change the image we use when building Flatpak bundles in our
CI pipeline.
|
| | |
|
| | |
|
| |
|
|
|
| |
It was added in 814b7d7bb71920a due to too old wayland in the runtime.
5b160efc768d3 fixed it by bundling a newer wayland.
|
| |
|
|
|
| |
Avoid repeating blobs of YAML manually, and use the proper YAML
mechanism to copy-paste blobs instead.
|
| |
|
|
| |
We can easily revert this when things are fixed again.
|
| |
|
|
|
|
| |
There where some problems (??) with ccache not detecting changes during meson
checks. Setting CCACHE_DISABLE during the meson execution makes ccache not use
the cache and pass things directly to the compiler.
|
| | |
|
| |
|
|
|
| |
The YAML is getting hard to modify, so let's use a simple script like we
do for the other CI jobs.
|
| |
|
|
| |
Forcibly remove any ccache use, even if it's installed.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
When building GTK through the CI infrastructure, it would help to have
some ways of testing it; for instance, if we want to verify that theme
changes are useful, or if we want to run the result without necessarily
build it locally.
This is where flatpak comes in handy. By having the CI build a flatpak
buundle, and storing it as an artifact, of the GTK demos, we can easily
point developers and designers to an installable binary that won't break
their system, nor will require development tools and environments to
run.
|
| |
|
|
|
|
|
| |
The GitLab cache is kept across jobs, whether they succeeded or not:
this means that if a compiler check fails during the Meson
configuration, the small compiler program gets cached and restored the
next time the job is run, thus failing again.
|
| |
|
|
|
|
|
|
| |
I've rebuilt the new Docker image we use for CI to include GStreamer in
the dependencies.
We really need to have the Docker registry hosted on gnome.org, to avoid
pointing people at Dockerhub.
|
| |
|
|
| |
The meson-logs directory is under the `_build` directory.
|
| |
|
|
|
| |
We should save the logs directory when the CI pipeline fails, so that we
have a chance at debugging the failure.
|
| |
|
|
|
| |
This saves another 30sec here and reducing clone operations on the
gnome gitlab instance is probably a good idea as well.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The CI runner is pretty slow to set up (takes about 6 minutes to get
through the system dependencies needed to build GTK), and does not work
with dependencies as subprojects.
Until we figure out how to make it work, and make it work a bit faster,
we should drop CI and rely on Continuous for a while longer.
We can revert this commit as soon as we find out how to make things
work.
|
| | |
|
| |
|
