patch: Fix no such file or directory during commit #100
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Gradle fairly aggressively tries to cleanup stale output files, with the goal of reliable build caching to avoid the need to run "./gradlew clean". However, this is problematic for tasks that have overlapping output directories, as it makes it difficult for Gradle to track what's stale. In a prior version we added the @UntrackedTask annotation to all of the publish tasks to avoid Gradle's state tracking. However, we use the built-in Gradle Copy task for one part of our chain, which does not have that annotation. In cases where the .gradle directory was not present, we would see the repository directory get deleted after the gitPublishCopy task ran, because Gradle thought it was stale. In other cases it seemed to be fine. While I don't understand the details of how Gradle makes those stale/fresh decisions, particularly in the absence of the .gradle directory, it seems the key is using the runtime method equivalent of the @UntrackedTask annotation (Task.doNotTrackState) to tell Gradle not to do its state tracking for this one task. We could still have issues in the future, but this seems to get us over the immediate hurdle. Fixes #99
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Gradle fairly aggressively tries to cleanup stale output files, with the goal of reliable build caching to avoid the need to run "./gradlew clean". However, this is problematic for tasks that have overlapping output directories, as it makes it difficult for Gradle to track what's stale.
In a prior version we added the @UntrackedTask annotation to all of the publish tasks to avoid Gradle's state tracking. However, we use the built-in Gradle Copy task for one part of our chain, which does not have that annotation.
In cases where the .gradle directory was not present, we would see the repository directory get deleted after the gitPublishCopy task ran, because Gradle thought it was stale. In other cases it seemed to be fine.
While I don't understand the details of how Gradle makes those stale/fresh decisions, particularly in the absence of the .gradle directory, it seems the key is using the runtime method equivalent of the @UntrackedTask annotation (Task.doNotTrackState) to tell Gradle not to do its state tracking for this one task.
We could still have issues in the future, but this seems to get us over the immediate hurdle.
Fixes #99