-
Notifications
You must be signed in to change notification settings - Fork 86
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
Running different tasks results into different dependency graphs #880
Comments
Thanks for the report. Different dependency graphs for different Gradle task executions is expected: this represents the actual dependencies resolved during the build. However, each of these graphs should have a different correlator, which should correspond to the graph file name |
This is working as expected in the automated tests:
If you compare Can you please run a test to print out the values of |
Hey, after analyzing the But they still produce different scopes for the same dependencies depending on the executed tasks: I have no idea which dependencies are shown in the web view, if ever. |
Thanks for confirming.
This is quite possible: a dependency that is used as a direct dependency for one execution could still be used as an indirect dependency in a different execution. Do you have build scans for the 2 different executions (this should provide an explanation of what's going on). By the way when inspecting your project I discovered a separate issue with Dependency Submission. |
I run the following Gradle tasks:
build
anddetekt
, so I get 3 dependency graphs (build
,detekt
,cleanup
). These files differs:detekt
) misses many artifacts.direct
in the first graph, butindirect
in the second run.cleanup
graph is empty.AFAIK GitHub uses the latest one (same correlator, higher timestamp) as final results, resulting in less dependencies.
Results: https://github.com/hfhbd/ComposeTodo/suites/15996628865/artifacts/913210709
CI run: https://github.com/hfhbd/ComposeTodo/actions/runs/6133473569/job/16645352703
CI config:
The text was updated successfully, but these errors were encountered: