gstreamer/ci
2023-11-18 16:37:07 +00:00
..
docker ci: Update to Rust 1.74 2023-11-17 02:48:59 +00:00
fluster/visl_references/test_suites ci: Use generated test suites data for visl 2023-10-31 10:18:46 -04:00
fuzzing fuzzing: correct typos in README.txt 2023-08-30 10:55:56 +00:00
gitlab ci: Propagate MESON_COMMIT to cerbero pipeline 2023-03-31 15:15:55 +00:00
meson gst-omx: Retire the whole package 2023-07-16 19:10:03 +00:00
scripts ci: Move a couple of scripts from yaml to dedicated files 2023-11-18 16:37:07 +00:00
README.txt ci/README: basic instructions for running locally 2023-01-09 22:26:52 +00:00

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.