From cfc488a439a33c44b855f9a3e2ed87aefeaea2ca Mon Sep 17 00:00:00 2001 From: Nirbheek Chauhan Date: Wed, 5 Oct 2022 06:04:10 +0530 Subject: ci: Fix triggered cerbero pipelines while tagged for release Cerbero pipelines triggered from the gstreamer monorepo were using the release tarballs while we were tagged for release in Cerbero. This means that the changes in the merge requests were not being tested by Cerbero CI at all. Part-of: --- recipes/custom.py | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/recipes/custom.py b/recipes/custom.py index 8ca7d01c..df13bc07 100644 --- a/recipes/custom.py +++ b/recipes/custom.py @@ -8,7 +8,14 @@ from cerbero.build.cookbook import CookBook from cerbero.enums import License, FatalError def running_on_cerbero_ci(): - return os.environ.get('CI_PROJECT_NAME', '') == 'cerbero' + if os.environ.get('CI_PROJECT_NAME', '') != 'cerbero': + return False + # If the cerbero CI was triggered from a merge request on the gstreamer + # monorepo, we want to use git because we want to test the changes that the + # merge request contains. + if os.environ.get('CI_GSTREAMER_TRIGGERED', '') == 'true': + return False + return True class GStreamer(recipe.Recipe): licenses = [License.LGPLv2Plus] -- cgit v1.2.3