Skip to content

fix: use setup-dotnet built-in NuGet cache#313

Merged
MO2k4 merged 2 commits intomasterfrom
fix/nuget-cache
Mar 31, 2026
Merged

fix: use setup-dotnet built-in NuGet cache#313
MO2k4 merged 2 commits intomasterfrom
fix/nuget-cache

Conversation

@MO2k4
Copy link
Copy Markdown
Owner

@MO2k4 MO2k4 commented Mar 31, 2026

Summary

  • Replaced manual actions/cache step with setup-dotnet's built-in cache: true option
  • The previous ~/.nuget/packages path didn't resolve correctly on Windows runners, so the NuGet cache was never restored
  • setup-dotnet handles the platform-specific NuGet packages path automatically

Test plan

  • Verify CI build succeeds
  • Check for "Cache restored" in the setup-dotnet step output

MO2k4 added 2 commits March 31, 2026 14:27
The manual actions/cache step used ~/.nuget/packages which doesn't
resolve correctly on Windows runners. setup-dotnet's built-in cache
handles the platform-specific path automatically.
- Cache ~/.intellijPlatform so the Rider SDK (~1GB) isn't re-downloaded
  on every run
- On master, run only publishPlugin (which already depends on
  buildPlugin) instead of running buildPlugin then publishPlugin
  separately, avoiding a full double .NET compile
- Add --parallel flag to Gradle for concurrent subproject execution
@sonarqubecloud
Copy link
Copy Markdown

@MO2k4 MO2k4 merged commit 533fb74 into master Mar 31, 2026
6 checks passed
@MO2k4 MO2k4 deleted the fix/nuget-cache branch March 31, 2026 13:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant