mirror of
https://gitlab.freedesktop.org/gstreamer/gstreamer.git
synced 2024-11-25 11:11:08 +00:00
a31c8cf370
This is mostly done to remove the hardcoded HOME env var that ci-templates appends to the image. See [1] [1] https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/2433#note_2243222 But it also allows us to add extra things useful for local development to it, as long they don't interfere with the build enviornment. This also means we can switch the build image to be based on top of the normal fedora one rather than toolbox, so it will no longer advertise the toolbox compatible labels since it was buggy anyway. Part-of: <https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/7455> |
||
---|---|---|
.. | ||
docker | ||
fluster/visl_references/test_suites | ||
fuzzing | ||
gitlab | ||
meson | ||
scripts | ||
README.txt | ||
run_retry.ps1 |
GStreamer Continuous Integration ================================ This repository contains all material relevant to the GStreamer Continuous Integration system. * Docker images * Build scripts and code Basic instructions for reproducing CI issues locally ==================================================== Note the URL of the image in the job logs, for instance: ``` Using docker image sha256:ac097589af0f486321adf7e512f2237c55533b9b08dabb49164a521a374d406d for registry.freedesktop.org/ocrete/gstreamer/amd64/fedora:2022-12-10.0-main with digest registry.freedesktop.org/ocrete/gstreamer/amd64/fedora@sha256:a2f7be944964a115ada2b3675c190bc9a094a5b35eba64a1ac38d52d55d13663 ``` Pull the image: ``` docker pull registry.freedesktop.org/ocrete/gstreamer/amd64/fedora:2022-12-10.0-main ``` Run it: ``` docker run -it fedora:2022-12-10.0-main ``` At this point, you want to clone the relevant branch, eg if the issue occurs with main: ``` git clone https://gitlab.freedesktop.org/gstreamer/gstreamer.git cd gstreamer ``` Adapt the above to your situation. Now, export the relevant variables by observing the job logs and `.gitlab-ci.yml` at he root of the GStreamer repository, then run the steps listed in the script section.