From 204033598f09c218aec5c9cc64ebf1c0f6dfbcd3 Mon Sep 17 00:00:00 2001 From: Charlie Lye Date: Thu, 28 Sep 2023 22:07:08 +0100 Subject: [PATCH] chore: Remove build system tainting now we have ci cmds in comments. (#2589) --- build-system/scripts/build | 1 - build-system/scripts/check_rebuild | 6 ------ 2 files changed, 7 deletions(-) diff --git a/build-system/scripts/build b/build-system/scripts/build index e1a23cc8614..ff7c81d82b0 100755 --- a/build-system/scripts/build +++ b/build-system/scripts/build @@ -69,7 +69,6 @@ cd $BUILD_DIR # If we have previously successful commit, we can early out if nothing relevant has changed since. if [[ $FORCE_BUILD == 'false' ]] && check_rebuild cache-"$CONTENT_HASH" $REPOSITORY; then echo "No rebuild necessary." - untag_remote_image $REPOSITORY tainted exit 0 fi diff --git a/build-system/scripts/check_rebuild b/build-system/scripts/check_rebuild index 5762f47dbe7..22d351b1575 100755 --- a/build-system/scripts/check_rebuild +++ b/build-system/scripts/check_rebuild @@ -14,13 +14,7 @@ REPOSITORY=$2 [[ "$COMMIT_MESSAGE" == *"[ci rebuild]"* ]] && exit 1 if ! image_exists $REPOSITORY $TAG; then - echo "Rebuild required." - exit 1 -elif image_exists $REPOSITORY tainted; then - # If a tainted tag exists, remove it and exit with failure to rebuild. - echo "$REPOSITORY has been tainted. Will rebuild." exit 1 else - echo "No rebuild required." exit 0 fi