Track published outputs to avoid conflict with :clean task
#410
Conversation
This file contains hidden or 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
Tasks of type `PublishToMavenRepository` do not track their outputs as they are typically used to publish to an external Maven repository. However, here such tasks are used to publish to `build/maven-repo` in the root project. Since Gradle's task graph was not aware of these untracked outputs, the `:clean` task was allowed to run in parallel of the subproject's publishing tasks. In some cases, this caused `:clean` to fail; in other cases, the contents of the custom local Maven repository were incomplete which caused downstream tasks to fail.
|
Looks like the GitHub Actions workflows are not set up to support contribution from forks. I think I think something like |
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.
Tasks of type
PublishToMavenRepositorydo not track their outputs asthey are typically used to publish to an external Maven repository.
However, here such tasks are used to publish to
build/maven-repointhe root project. Since Gradle's task graph was not aware of these
untracked outputs, the
:cleantask was allowed to run in parallel ofthe subproject's publishing tasks. In some cases, this caused
:cleanto fail; in other cases, the contents of the custom local Maven
repository were incomplete which caused downstream tasks to fail.
This should resolve the problem of running
./gradlew clean check integrationTestrepeatedly.