GStreamer multimedia framework
Find a file
Tim-Philipp Müller 7ed820aa1f gitlab/ci_template: run valgrind tests automatically
Don't valgrind everything for all changes though,
but only those modules most likely to be affected
by changes in the current ci project. So, valgrind

 - gstreamer only for gstreamer core changes
 - gst-plugins-base for core/base changes
 - gst-plugins-good for core/base/good changes
 - gst-plugins-ugly for core/base/ugly changes
 - gst-plugins-bad for core/base/good changes

In other words: don't valgrind core/base if it's
good/bad/ugly that's being changed, for example.
Don't valgrind -good or -ugly for changes in -bad,
etc.

Meaning:

 - for changes in core, valgrind core/base/good/ugly/bad
 - for changes in base, valgrind base/good/ugly/bad
 - for changes in good, valgrind good/bad
 - for changes in ugly, valgrind ugly
 - for changes in bad, valgrind bad

More modules to be added later once they're valgrind
clean on the CI.

https://gitlab.freedesktop.org/gstreamer/gst-ci/merge_requests/80
2019-03-25 17:31:44 +00:00
docker Always print timestamps when running Cerbero 2019-03-25 21:49:29 +05:30
fuzzing Run gst-indent through the files 2018-12-03 17:39:09 +02:00
gitlab gitlab/ci_template: run valgrind tests automatically 2019-03-25 17:31:44 +00:00
jenkins jenkins: Update meson-fedora 2017-10-28 10:59:08 +02:00
.gitignore Add gitignore 2017-10-28 11:01:33 +02:00
.gitlab-ci.yml gitlab/ci_template: refresh the image builds 2019-03-14 20:51:08 +02:00
README.txt Initial commit 2017-10-21 12:07:02 +02:00

GStreamer Continuous Integration
================================

This repository contains all material relevant to the GStreamer
Continuous Integration system.

* Jenkins scripts

* Docker images

* Build scripts and code