From 6c39166fad1f1296e05475a65b5bba65f8535ae8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jonas=20H=C3=B6ppner?= <jonas.hoeppner@garz-fricke.com>
Date: Fri, 20 May 2022 11:59:48 +0200
Subject: [PATCH] CI: deploy-gitlab-ci: Don't stop integration when one project
is already updated
Prior to this change the integration stop when one of the projects had
already the latest ref of gitlab-ci in to submodule.
---
update_submodule.py | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/update_submodule.py b/update_submodule.py
index 6c3f7602..c54b6ac6 100755
--- a/update_submodule.py
+++ b/update_submodule.py
@@ -229,7 +229,11 @@ def update_submodule_and_include_ref(
ref_name=revision_range, retry_transient_errors=True
)
if not commits:
- sys.exit("ERROR: no commits found in range %s" % revision_range)
+ logging.info(
+ "No commits found in range %s, probably submodule already up-to-date.",
+ revision_range,
+ )
+ return None, None, None, None
logging.debug("New commits: %s", commits)
# Find out if top commit is part of a merge request
--
GitLab