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

Gradle Build Optimizations #24764

Merged
merged 2 commits into from
Jul 26, 2023
Merged

Conversation

clayburn
Copy link
Contributor

@clayburn clayburn commented Dec 22, 2022

This change includes a few Gradle Build optimizations, including:

  • Updating to Gradle 7.6.1
  • Improving caching of the Checkstyle tasks

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

  • Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
  • Update CHANGES.md with noteworthy changes.
  • If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

Build python source distribution and wheels
Python tests
Java tests
Go tests

See CI.md for more information about GitHub Actions CI.

@github-actions
Copy link
Contributor

Assigning reviewers. If you would like to opt out of this review, comment assign to next reviewer:

R: @apilloud for label java.
R: @damccorm for label build.

Available commands:

  • stop reviewer notifications - opt out of the automated review tooling
  • remind me after tests pass - tag the comment author after tests pass
  • waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

@codecov
Copy link

codecov bot commented Dec 22, 2022

Codecov Report

Merging #24764 (2a07fa4) into master (967db6f) will increase coverage by 1.96%.
The diff coverage is n/a.

❗ Current head 2a07fa4 differs from pull request most recent head c032a38. Consider uploading reports for the commit c032a38 to get more accurate results

@@            Coverage Diff             @@
##           master   #24764      +/-   ##
==========================================
+ Coverage   70.94%   72.91%   +1.96%     
==========================================
  Files         861      746     -115     
  Lines      104795    99264    -5531     
==========================================
- Hits        74344    72374    -1970     
+ Misses      28894    25524    -3370     
+ Partials     1557     1366     -191     
Flag Coverage Δ
python 82.38% <ø> (+2.37%) ⬆️

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

see 434 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@github-actions
Copy link
Contributor

Reminder, please take a look at this pr: @apilloud @damccorm

@github-actions
Copy link
Contributor

github-actions bot commented Jan 4, 2023

Assigning new set of reviewers because Pr has gone too long without review. If you would like to opt out of this review, comment assign to next reviewer:

R: @robertwb for label java.
R: @Abacn for label build.

Available commands:

  • stop reviewer notifications - opt out of the automated review tooling
  • remind me after tests pass - tag the comment author after tests pass
  • waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

@github-actions
Copy link
Contributor

Reminder, please take a look at this pr: @robertwb @Abacn

@github-actions
Copy link
Contributor

Assigning new set of reviewers because Pr has gone too long without review. If you would like to opt out of this review, comment assign to next reviewer:

R: @kennknowles for label java.
R: @damccorm for label build.

Available commands:

  • stop reviewer notifications - opt out of the automated review tooling
  • remind me after tests pass - tag the comment author after tests pass
  • waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

@github-actions
Copy link
Contributor

Reminder, please take a look at this pr: @kennknowles @damccorm

@github-actions
Copy link
Contributor

Assigning new set of reviewers because Pr has gone too long without review. If you would like to opt out of this review, comment assign to next reviewer:

R: @lukecwik for label java.
R: @Abacn for label build.

Available commands:

  • stop reviewer notifications - opt out of the automated review tooling
  • remind me after tests pass - tag the comment author after tests pass
  • waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

@kennknowles
Copy link
Member

Looks like a lot of tests are red. I didn't look into why, but it seems likely to do with this change?

@github-actions
Copy link
Contributor

github-actions bot commented Feb 9, 2023

Reminder, please take a look at this pr: @lukecwik @Abacn

@clayburn clayburn force-pushed the gradle-optimizations branch from a6357da to 2a07fa4 Compare February 9, 2023 13:41
@clayburn clayburn closed this Feb 9, 2023
@clayburn clayburn reopened this Feb 9, 2023
@kennknowles
Copy link
Member

Some of the failures appear to be new intra-project dependency issues discovered by the upgrade to that analysis plugin. I suggest separating that upgrade from the gradle upgrade, if possible.

@clayburn
Copy link
Contributor Author

@kennknowles Thanks for the feedback. I rebased yesterday but didn't get a chance to analyze the results. I've removed the analysis plugin update from this PR.

@kennknowles
Copy link
Member

Run Java_GCP_IO_Direct PreCommit

@kennknowles
Copy link
Member

Seeing enough green that I am optimistic. Kicking the test that had an NPE.

@github-actions
Copy link
Contributor

Reminder, please take a look at this pr: @lukecwik @Abacn

@clayburn
Copy link
Contributor Author

clayburn commented Jul 6, 2023

@damccorm apologies, I missed that this was merge conflicted. I've rebased the PR.

@kennknowles
Copy link
Member

Run Java_Spark3_Versions PreCommit

1 similar comment
@kennknowles
Copy link
Member

Run Java_Spark3_Versions PreCommit

@kennknowles
Copy link
Member

run java precommit

@github-actions
Copy link
Contributor

Reminder, please take a look at this pr: @robertwb @damccorm

@github-actions
Copy link
Contributor

Assigning new set of reviewers because Pr has gone too long without review. If you would like to opt out of this review, comment assign to next reviewer:

R: @Abacn for label java.
R: @Abacn for label build.

Available commands:

  • stop reviewer notifications - opt out of the automated review tooling
  • remind me after tests pass - tag the comment author after tests pass
  • waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

@damccorm
Copy link
Contributor

R: @kennknowles

@damccorm
Copy link
Contributor

(could you take this one to completion since you've started reviewing?)

@github-actions
Copy link
Contributor

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control

@kennknowles
Copy link
Member

Ha! If by "started review" you mean "kicked the tests" :-p

@kennknowles
Copy link
Member

Everything is green now but we have to resolve the conflicts.

clayburn added 2 commits July 25, 2023 09:53
As configured before, the `configProperties` field has an absolute path
sensitivity introduced by the reference to the suppressions file. This
change causes the path to be relative to the project root, which can
facilitate cache hits when absolute paths change (for example, when the
build is run from a CI system and a remote cache is populated, then consumed
from a local build).

This refactoring matches recommendations found in the Gradle documentation for
structuring Checkstyle configuration files:

https://docs.gradle.org/current/userguide/checkstyle_plugin.html#sec:checkstyle_built_in_variables

This change also configure Checkstyle via the `CheckstyleExtension` rather than
the `Checkstyle` tasks
@clayburn clayburn force-pushed the gradle-optimizations branch from fc6d9eb to c032a38 Compare July 25, 2023 14:54
@clayburn
Copy link
Contributor Author

@kennknowles, the conflicts should now be resolved ✅

@kennknowles
Copy link
Member

Filed #27666 for the Kinesis failure.

Filed #27667 for the Python coverage failure.

@kennknowles
Copy link
Member

Run Python_Coverage PreCommit

@kennknowles
Copy link
Member

Run Java_Amazon-Web-Services2_IO_Direct Precommit

@Abacn
Copy link
Contributor

Abacn commented Jul 25, 2023

Run Java_PVR_Flink_Batch PreCommit

@kennknowles
Copy link
Member

Green. Hooray!

@kennknowles kennknowles merged commit c754e58 into apache:master Jul 26, 2023
@clayburn clayburn deleted the gradle-optimizations branch July 27, 2023 18:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants