You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a gradle project with two sub projects and both use the nuget plugin. From time to time I observe the situation that after server maintenance one of the related nugetRestore tasks fails while the other one succeeds. Subsequent builds succeed then.
This suggests that the download of the nuget executable into the Gradle cache has a synchronization issue or some check for presence of the executable may lead to unexpected results.
Is it possible that the check for the nuget executable tests only for existence of the file but not for complete download of it?
The text was updated successfully, but these errors were encountered:
I do not know enought about gradle to provide a proper solution for that. The workaround is to define an explicit dependency which technically does not exist.
Hi,
using version 2.23
I have a gradle project with two sub projects and both use the nuget plugin. From time to time I observe the situation that after server maintenance one of the related nugetRestore tasks fails while the other one succeeds. Subsequent builds succeed then.
This suggests that the download of the nuget executable into the Gradle cache has a synchronization issue or some check for presence of the executable may lead to unexpected results.
Is it possible that the check for the nuget executable tests only for existence of the file but not for complete download of it?
The text was updated successfully, but these errors were encountered: