- 27 Jan, 2021 1 commit
-
-
Jordan Petridіs authored
This is the 3rd or 4th time we are trying this yes, (!331), but hear me out. This time is for Real! Jokes aside, its possible to avoid spawning >1 pipeline per event with gitlab 13.8. https://gitlab.com/gitlab-org/gitlab/-/issues/201845 https://gitlab.com/gitlab-org/gitlab/-/issues/299409 Part-of: <!393>
-
- 21 Jan, 2021 1 commit
-
-
Matthew Waters authored
Part-of: <!390>
-
- 23 Dec, 2020 1 commit
-
-
Jordan Petridіs authored
Most of the networking issues with the runner should be fixed now. Part-of: <!386>
-
- 17 Nov, 2020 2 commits
-
-
Jordan Petridіs authored
Part-of: <!378>
-
Jordan Petridіs authored
Close #73 #74 #75 Part-of: <!378>
-
- 29 Oct, 2020 1 commit
-
-
Nirbheek Chauhan authored
GitLab doesn't wipe images entirely before reusing them across jobs. It relies on the build scripts to not write outside the workdir. However, we create symlinks outside of the workdir, which breaks in weird ways. Specifically, when ../../gstreamer/cerbero exists, `ln -sf` creates ../../gstreamer/cerbero/cerbero, which is wrong, but doesn't cause an error. However, when the image is reused again after this, ../../gstreamer/cerbero/cerbero already exists, so `ln -sf` yields: ln: ../../gstreamer/cerbero/cerbero: cannot overwrite directory This is fixed in master after overhauling the scripts to never write outside of workdir, but for 1.16 we need to hack it by not symlinking if the target dir already exists. Originally commited to the 1.16 branch in !370 The proper fix will be backported from master, but let's fix this error in the meantime so it doesn't roadblock the 1.18 stable releases Part-of: <!374>
-
- 27 Oct, 2020 1 commit
-
-
Jordan Petridіs authored
This is meant to be used for containers that are going to be periodically rebuilt. For our usecase specifying `fdo.upstream-repo` is enough to garbage collect all the tags from the forks. We also need to rebuild the images, so they don't have include the label anymore. Part-of: <!373>
-
- 22 Oct, 2020 1 commit
-
-
Jordan Petridіs authored
With the MergeRequest rules template, its was impossible to manually create or trigger a pipeline for a branch/commit that was not part of a merge request. This tweaks the workflow:rules such that there will always be a pipeline for each commit (which will be set to a manual job trigger). There is the downside that we will now be triggering 2 pipelines in case of merge requests, but they will require manual action to be started. Part-of: <!371>
-
- 14 Oct, 2020 1 commit
-
-
Jordan Petridіs authored
Gitlab was slightly bugged in previous version, and we had to use branch-only pipelines. Let's try this again. Part-of: <!366>
-
- 28 Sep, 2020 1 commit
-
-
Jordan Petridіs authored
When quoting in rules it takes the string as literal and doesn't expand the variable Cherry-pick of 8c066ec0 Part-of: <!355>
-
- 15 Sep, 2020 1 commit
-
-
Jordan Petridіs authored
Need to rebuild the image cache to account for the wrap changes [1] [1] gst-build!188 Part-of: <!340>
-
- 14 Sep, 2020 2 commits
-
-
Tim-Philipp Müller authored
Part-of: <!335>
-
Jordan Petridіs authored
These are needed for the webrtcbin tests Part-of: <!335>
-
- 09 Sep, 2020 3 commits
-
-
Jordan Petridіs authored
We used to get this as transient dependency it seems, which broke rebuilds of the img once w/e pkg was depending on it, stopped. Part-of: <!335>
-
Jordan Petridіs authored
Part-of: <!335>
-
Jordan Petridіs authored
Close #83 Part-of: <!337>
-
- 27 Aug, 2020 2 commits
-
-
Jordan Petridіs authored
Rework rules of jobs to prever duplicate pipelines. https://docs.gitlab.com/ce/ci/yaml/README.html#prevent-duplicate-pipelines Part-of: <!331>
-
Jordan Petridіs authored
We can run the jobs always automatically since, most of the time they will be copying/reffing the existance image in the registry. Part-of: <!331>
-
- 05 Aug, 2020 1 commit
-
-
Nirbheek Chauhan authored
Part-of: <!328>
-
- 04 Aug, 2020 1 commit
-
-
Tim-Philipp Müller authored
See gst-plugins-bad!1465 Part-of: <!328>
-
- 26 Jul, 2020 2 commits
-
-
Jordan Petridіs authored
Close #80 Part-of: <!326>
-
Jordan Petridіs authored
Currently, if you have a MR open, there 2 pipelines being triggered. One normal, and one detached. Previously, if you were to rebuild an image, the jobs of the docker build stage would be executed concurrently, race and end up both rebuilding the image. Make them manual for normal pipelines to avoid such occurrence and waste of resources. Part-of: <!320>
-
- 24 Jul, 2020 1 commit
-
-
Jordan Petridіs authored
we don't need the image to be copied or rebuilt, as its currently pinned shortly and won't change anytime soon. ammends dc486667 !324 Part-of: <!325>
-
- 23 Jul, 2020 2 commits
-
-
Jordan Petridіs authored
The update to f31 from !271 triggered an error in hotdoc it seems, so rollback for now till we figure it out. https://gitlab.freedesktop.org/gdesmott/gst-plugins-base/-/jobs/3764215 Part-of: <!324>
-
Jordan Petridіs authored
Part-of: <!271>
-
- 10 Jul, 2020 1 commit
-
-
Nirbheek Chauhan authored
Needed for cerbero!540. Part-of: <!322>
-
- 09 Jul, 2020 1 commit
-
-
Mathieu Duponchelle authored
Part-of: <!321>
-
- 03 Jul, 2020 8 commits
-
-
Jordan Petridіs authored
Part-of: <!315>
-
Matthew Waters authored
It may throws various warning that are treated as errors for other repositories Part-of: <!171>
-
Jordan Petridіs authored
It was introduced in a recentish release along with pipelines for merge requests, but it required the use of rules. Part-of: <!318>
-
Jordan Petridіs authored
We only need the newer version from the image, to support the --arch arg, but we don't really use it yet so we could live without it. Part-of: <!318>
-
Jordan Petridіs authored
gst-example contains tests for check but not integrations suite Part-of: <!318>
-
Jordan Petridіs authored
Needed to catch regressions in the docs cache files. Part-of: <!318>
-
Jordan Petridіs authored
Part-of: <!318>
-
Guillaume Desmottes authored
Part-of: <!318>
-
- 02 Jul, 2020 1 commit
-
-
Thibault Saunier authored
-
- 01 Jul, 2020 1 commit
-
-
Mathieu Duponchelle authored
-
- 30 Jun, 2020 1 commit
-
-
Nirbheek Chauhan authored
Match the official steps by MSYS2 upstream for updating on CI: https://github.com/msys2/setup-msys2/blob/master/main.js#L98 Part-of: <!317>
-
- 29 Jun, 2020 2 commits
-
-
Jordan Petridіs authored
If its not CI_REGISTRY_IMAGE will be null and break the job. Instead paste a helpful message with the documentation on how to enable the registry. Part-of: <!316>
-
Jordan Petridіs authored
There isn't anything particular that needs to be on the gstreamer runners, and the other shared runners should be able to handle them fine. Part-of: <!314>
-