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

chore: Upgrade gradle version #84

Merged
merged 3 commits into from
Aug 27, 2021
Merged

chore: Upgrade gradle version #84

merged 3 commits into from
Aug 27, 2021

Conversation

findingrish
Copy link

No description provided.

@findingrish findingrish requested a review from a team August 27, 2021 09:30
@@ -1,4 +1,4 @@
rootProject.name = "query-service"
rootProject.name = "query-service-root"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why is this change?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

@aaron-steinfeld aaron-steinfeld left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the build issue is due to bad config in the proto plugin that's being caught with the stricter gradle, we've run into it before.

Source sets for api project can add in the generated dirs, but not duplicate the default source sets (which is causing the double inclusion):

sourceSets {
  main {
    java {
      srcDirs("build/generated/source/proto/main/java", "build/generated/source/proto/main/grpc_java")
    }
  }
}

@@ -1,5 +1,5 @@
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-6.7.1-all.zip
distributionUrl=https\://services.gradle.org/distributions/gradle-7.1.1-all.zip
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

given that we're upgrading gradle, can we go to 7.2?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@codecov
Copy link

codecov bot commented Aug 27, 2021

Codecov Report

Merging #84 (3fe242c) into main (16056f2) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##               main      #84   +/-   ##
=========================================
  Coverage     81.62%   81.62%           
  Complexity      391      391           
=========================================
  Files            37       37           
  Lines          1513     1513           
  Branches        162      162           
=========================================
  Hits           1235     1235           
  Misses          205      205           
  Partials         73       73           
Flag Coverage Δ
integration 81.62% <ø> (ø)
unit 79.20% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.


Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 16056f2...3fe242c. Read the comment docs.

@github-actions

This comment has been minimized.

@findingrish findingrish merged commit 895ba1b into main Aug 27, 2021
@findingrish findingrish deleted the gradle-upgrade branch August 27, 2021 17:16
@github-actions
Copy link

Unit Test Results

  22 files  ±0    22 suites  ±0   10s ⏱️ +3s
113 tests ±0  113 ✔️ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 895ba1b. ± Comparison against base commit 16056f2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants