Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Gradle to 8.12 #16884

Merged
merged 1 commit into from
Jan 10, 2025
Merged

Update Gradle to 8.12 #16884

merged 1 commit into from
Jan 10, 2025

Conversation

reta
Copy link
Collaborator

@reta reta commented Dec 19, 2024

Description

Update Gradle to 8.12 (https://github.com/gradle/gradle/releases/tag/v8.12.0)

Related Issues

N/A

Check List

  • Functionality includes testing.
  • API changes companion pull request created, if applicable.
  • Public documentation issue/PR created, if applicable.

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.

Copy link
Contributor

❌ Gradle check result for 1760ba8: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Copy link
Contributor

❌ Gradle check result for a6330e2: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Copy link
Contributor

❌ Gradle check result for a541209: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Copy link
Contributor

github-actions bot commented Jan 3, 2025

❌ Gradle check result for 2b75405: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Copy link
Contributor

github-actions bot commented Jan 3, 2025

❌ Gradle check result for 3b8cfb4: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

@reta reta force-pushed the gradle.8.12 branch 3 times, most recently from 38c2092 to 9bc210a Compare January 6, 2025 16:55
Copy link
Contributor

github-actions bot commented Jan 6, 2025

❌ Gradle check result for 9bc210a: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Copy link
Contributor

github-actions bot commented Jan 6, 2025

❌ Gradle check result for 1fd7112: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Copy link
Contributor

github-actions bot commented Jan 7, 2025

❌ Gradle check result for e574749: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Copy link
Contributor

github-actions bot commented Jan 7, 2025

❌ Gradle check result for c64095e: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Copy link
Contributor

github-actions bot commented Jan 7, 2025

❌ Gradle check result for c64095e: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Copy link
Contributor

github-actions bot commented Jan 8, 2025

❌ Gradle check result for 157ddf6: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Copy link
Contributor

github-actions bot commented Jan 8, 2025

❌ Gradle check result for 66b19a4: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Copy link
Contributor

github-actions bot commented Jan 8, 2025

❌ Gradle check result for 66b19a4: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Copy link
Contributor

github-actions bot commented Jan 8, 2025

❌ Gradle check result for 29dc6c9: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Copy link
Contributor

github-actions bot commented Jan 9, 2025

❌ Gradle check result for 5a18bb9: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Signed-off-by: Andriy Redko <[email protected]>
@reta reta added backport 2.x Backport to 2.x branch Build Build Tasks/Gradle Plugin, groovy scripts, build tools, Javadoc enforcement. labels Jan 9, 2025
Copy link
Contributor

github-actions bot commented Jan 9, 2025

✅ Gradle check result for 65ef10f: SUCCESS

Copy link

codecov bot commented Jan 9, 2025

Codecov Report

Attention: Patch coverage is 13.10345% with 126 lines in your changes missing coverage. Please review.

Project coverage is 72.20%. Comparing base (2eadf12) to head (65ef10f).
Report is 5 commits behind head on main.

Files with missing lines Patch % Lines
...arch/gradle/precommit/TestingConventionsTasks.java 0.00% 25 Missing ⚠️
...ensearch/gradle/precommit/ThirdPartyAuditTask.java 0.00% 20 Missing ⚠️
...rg/opensearch/gradle/vagrant/VagrantShellTask.java 0.00% 8 Missing ⚠️
...g/opensearch/gradle/test/rest/CopyRestApiTask.java 0.00% 7 Missing ⚠️
...g/opensearch/gradle/test/GradleDistroTestTask.java 0.00% 6 Missing ⚠️
...opensearch/gradle/test/rest/CopyRestTestsTask.java 0.00% 6 Missing ⚠️
...ain/groovy/org/opensearch/gradle/NoticeTask.groovy 0.00% 5 Missing ⚠️
.../org/opensearch/gradle/docker/DockerBuildTask.java 0.00% 5 Missing ⚠️
...g/opensearch/gradle/precommit/LoggerUsageTask.java 0.00% 5 Missing ⚠️
...org/opensearch/gradle/precommit/PrecommitTask.java 0.00% 4 Missing ⚠️
... and 16 more
Additional details and impacted files
@@             Coverage Diff              @@
##               main   #16884      +/-   ##
============================================
- Coverage     72.27%   72.20%   -0.08%     
+ Complexity    65324    65207     -117     
============================================
  Files          5299     5299              
  Lines        303475   303499      +24     
  Branches      43934    43932       -2     
============================================
- Hits         219334   219137     -197     
- Misses        66197    66386     +189     
- Partials      17944    17976      +32     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@reta reta merged commit 9bb1fbe into opensearch-project:main Jan 10, 2025
45 of 46 checks passed
@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.x 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/OpenSearch/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch/backport-2.x
# Create a new branch
git switch --create backport/backport-16884-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 9bb1fbe2d615602971cb786d06ff80ba377d1c7f
# Push it to GitHub
git push --set-upstream origin backport/backport-16884-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-16884-to-2.x.

reta added a commit to reta/OpenSearch that referenced this pull request Jan 10, 2025
Signed-off-by: Andriy Redko <[email protected]>
(cherry picked from commit 9bb1fbe)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport 2.x Backport to 2.x branch backport-failed Build Build Tasks/Gradle Plugin, groovy scripts, build tools, Javadoc enforcement. skip-changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants