mirror of
https://gitlab.freedesktop.org/gstreamer/gstreamer.git
synced 2024-11-22 09:41:07 +00:00
578680a530
It's both easier to use that way and we can also reuse it when building locally. Part-of: <https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/4281> |
||
|---|---|---|
| .. | ||
| docker | ||
| fuzzing | ||
| gitlab | ||
| meson | ||
| scripts | ||
| README.txt | ||
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.