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
All the debugging we did this week made me notice an other small issue with your extension. You download the resharper cli nuget package straight in the artifact directory. This means that if no other task wipe the content of the directory after yours run, the publish artifact task will end up publishin the nuget packge.
I think a simple fix could be to download it in the source directory, though this might also cause issues for tasks that copies all nupkg files to the artifact directory later. At least, it wouldn't be there by default.
A better fix would be to do something similar to the "Use NuGet" task which stores its files in the tools folder, outside of the build directory. This is a bigger change because you will also have to consider than the file might stay there across build so it will impact how the package gets updated.
Anyway, just my two cents. It would be really appreciated if you could look into this.
I also see this behavior, and it slows down my builds significantly, would be really great if this can be fixed.
Anyway, thanks for the great work so far!
Regards,
Wouter
The text was updated successfully, but these errors were encountered:
Comment from Etienne Maheu copied from the VSTS Marketplace Q&A page:
Hello,
All the debugging we did this week made me notice an other small issue with your extension. You download the resharper cli nuget package straight in the artifact directory. This means that if no other task wipe the content of the directory after yours run, the publish artifact task will end up publishin the nuget packge.
I think a simple fix could be to download it in the source directory, though this might also cause issues for tasks that copies all nupkg files to the artifact directory later. At least, it wouldn't be there by default.
A better fix would be to do something similar to the "Use NuGet" task which stores its files in the tools folder, outside of the build directory. This is a bigger change because you will also have to consider than the file might stay there across build so it will impact how the package gets updated.
Anyway, just my two cents. It would be really appreciated if you could look into this.
I also see this behavior, and it slows down my builds significantly, would be really great if this can be fixed.
Anyway, thanks for the great work so far!
Regards,
Wouter
The text was updated successfully, but these errors were encountered: