Skip to content
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

[release/6.0.4xx] [build] Fix invalid cache management by 'dotnet tool restore'. #15263

Closed

Conversation

rolfbjarne
Copy link
Member

Fix invalid cache management by 'dotnet tool restore' by deleting 'dotnet tool's cache.

This is a backport of #15227.

…l restore'.

Fix invalid cache management by 'dotnet tool restore' by deleting 'dotnet tool's cache.

This is a backport of xamarin#15227.
@rolfbjarne rolfbjarne added the not-notes-worthy Ignore for release notes label Jun 14, 2022
@rolfbjarne
Copy link
Member Author

rolfbjarne commented Jun 14, 2022

This fixes a random build failure in this branch (which will be nice to have if we branch off release/6.0.5xx from this branch at some point).

This needs another build fix first: #15264.

@vs-mobiletools-engineering-service2
Copy link
Collaborator

🔥 [PR Build] Build failed 🔥

Build failed for the job 'Build packages'

Pipeline on Agent
Hash:

@vs-mobiletools-engineering-service2
Copy link
Collaborator

🔥 [PR Build] Build failed 🔥

Build failed for the job 'Generate API diff'

Pipeline on Agent
Hash:

@vs-mobiletools-engineering-service2
Copy link
Collaborator

📚 [PR Build] Artifacts 📚

Artifacts were not provided.

Pipeline on Agent
Hash: 943b8bc36a4f374027575457dd8977de5ff68d02

@rolfbjarne
Copy link
Member Author

Moved this into #15264, since both of these PRs need the other PR to build.

@rolfbjarne rolfbjarne closed this Jun 14, 2022
@rolfbjarne rolfbjarne deleted the 6.0.4xx-backport-15227 branch November 4, 2022 07:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
not-notes-worthy Ignore for release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants