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

[do not merge] gradle cache build expt #12829

Draft
wants to merge 4 commits into
base: master
Choose a base branch
from
Draft

Conversation

chakru-r
Copy link
Collaborator

Checklist

  • The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
  • Links to related issues (if applicable)
  • Tests for the changes have been added/updated (if applicable)
  • Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
  • For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

HAving these as two separate tasks caused copy to always be out-of-date when
rename is run, and rename to be out-of-date when rename is done. Gradle
does not like inplace updates of any files. By combining it, the copy+rename
now appear to produce a new artificat that will be up-to-date if no sources
have changed. This caused lot of downstream jars to get rebuilt since this jar
is always out-of-dat and rebuilt everytime.
@chakru-r chakru-r changed the title [do not merge] fix clean to run during evaluate instead of config stage [do not merge] gradle cache build expt Mar 10, 2025
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.

1 participant