Mitigate the CI failure caused by 500 Internal Server Error

[LantaoJin]

Description

Today, the CI always fails with

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':opensearch-sql-plugin:shadowJar'.
> Could not resolve all dependencies for configuration ':opensearch-sql-plugin:runtimeClasspath'.
   > Could not resolve com.github.babbel:okhttp-aws-signer:1.0.2.
     Required by:
         project :opensearch-sql-plugin > project :ppl > project :common
      > Could not resolve com.github.babbel:okhttp-aws-signer:1.0.2.
         > Could not get resource 'https://ci.opensearch.org/ci/dbc/snapshots/maven/com/github/babbel/okhttp-aws-signer/1.0.2/okhttp-aws-signer-1.0.2.pom'.
            > Could not GET 'https://ci.opensearch.org/ci/dbc/snapshots/maven/com/github/babbel/okhttp-aws-signer/1.0.2/okhttp-aws-signer-1.0.2.pom'. Received status code 403 from server: Forbidden

      > Could not resolve com.github.babbel:okhttp-aws-signer:1.0.2.
Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
         > Could not get resource 'https://ci.opensearch.org/ci/dbc/snapshots/lucene/com/github/babbel/okhttp-aws-signer/1.0.2/okhttp-aws-signer-1.0.2.pom'.

            > Could not GET 'https://ci.opensearch.org/ci/dbc/snapshots/lucene/com/github/babbel/okhttp-aws-signer/1.0.2/okhttp-aws-signer-1.0.2.pom'. Received status code 403 from server: Forbidden
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
      > Could not resolve com.github.babbel:okhttp-aws-signer:1.0.2.

         > Could not get resource 'https://jitpack.io/com/github/babbel/okhttp-aws-signer/1.0.2/okhttp-aws-signer-1.0.2.pom'.
For more on this, please refer to https://docs.gradle.org/8.14/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
            > Could not GET 'https://jitpack.io/com/github/babbel/okhttp-aws-signer/1.0.2/okhttp-aws-signer-1.0.2.pom'. Received status code 500 from server: Internal Server Error
3 actionable tasks: 3 executed

Add build cache to mitigate the failures when download 'https://jitpack.io'

Related Issues

Resolves #[Issue number to be closed when this PR is merged]

Check List

• New functionality includes testing.
• New functionality has been documented.
• New functionality has javadoc added.
• New functionality has a user manual doc added.
• New PPL command checklist all confirmed.
• API changes companion pull request created.
• Commits are signed per the DCO using --signoff or -s.
• Public documentation issue/PR created.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[qianheng-aws]

Does this mean only downloading "com.github.babbel" from source 'https://jitpack.io'?

[LantaoJin]

yes

[opensearch-trigger-bot]

The backport to 2.19-dev failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/sql/backport-2.19-dev 2.19-dev
# Navigate to the new working tree
pushd ../.worktrees/sql/backport-2.19-dev
# Create a new branch
git switch --create backport/backport-4646-to-2.19-dev
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 2cb1d7349a13237fab3c084ca62e170a391f1927
# Push it to GitHub
git push --set-upstream origin backport/backport-4646-to-2.19-dev
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/sql/backport-2.19-dev

Then, create a pull request where the base branch is 2.19-dev and the compare/head branch is backport/backport-4646-to-2.19-dev.