From 89a3d74b932ba979d33b0eaef5892157e7af2b28 Mon Sep 17 00:00:00 2001
From: Alex Plate <aleksei.plate@jetbrains.com>
Date: Wed, 3 Jul 2024 19:32:03 +0300
Subject: [PATCH] Try not to use the configuration cache in gradle automations
at the moment
This is done because the current implementation of the gradle commands is not correct and the cache fails on GitHub actions.
---
.github/workflows/closeYoutrackOnCommit.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.github/workflows/closeYoutrackOnCommit.yml b/.github/workflows/closeYoutrackOnCommit.yml
index 6c91bc012..f2dbc4c03 100644
--- a/.github/workflows/closeYoutrackOnCommit.yml
+++ b/.github/workflows/closeYoutrackOnCommit.yml
@@ -34,7 +34,7 @@ jobs:
echo "LAST_COMMIT=$(git rev-list -n 1 tags/workflow-close-youtrack)" >> $GITHUB_ENV
- name: Update YouTrack
- run: ./gradlew updateYoutrackOnCommit
+ run: ./gradlew updateYoutrackOnCommit --no-configuration-cache # No configuration cache to avoid fails on GH Actions
env:
SUCCESS_COMMIT: ${{ env.LAST_COMMIT }}
YOUTRACK_TOKEN: ${{ secrets.YOUTRACK_TOKEN }}