chore: replace chocolatey with native binaries#6639
chore: replace chocolatey with native binaries#6639mihaibuzgau wants to merge 4 commits intomainfrom
Conversation
This comment has been minimized.
This comment has been minimized.
821cecc to
bdef5ed
Compare
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
cdd8b29 to
69056fa
Compare
|
/review |
This comment has been minimized.
This comment has been minimized.
|
/review |
This comment has been minimized.
This comment has been minimized.
110e69f to
765b462
Compare
|
/review |
This comment has been minimized.
This comment has been minimized.
765b462 to
42b39b5
Compare
|
/review |
This comment has been minimized.
This comment has been minimized.
42b39b5 to
aa336dc
Compare
|
/review |
This comment has been minimized.
This comment has been minimized.
aa336dc to
9d7b8ac
Compare
|
/review |
This comment has been minimized.
This comment has been minimized.
48e9b8d to
87bc5f9
Compare
|
|
||
| try { | ||
| $dotnetVersion = '8.0.100' | ||
| $cacheDir = 'C:\tools-cache' |
There was a problem hiding this comment.
Suggestion/Question: Is there a reason why we don't inject the cachedir as a parameter. This would enable to have a single source of truth.
.circleci/config.yml
Outdated
| name: Restoring Windows tools cache | ||
| keys: | ||
| - chocolatey-cache-full-v5-{{ arch }}-{{ checksum ".circleci/chocolatey.config" }} | ||
| - windows-tools-cache-v1-{{ arch }} |
There was a problem hiding this comment.
Issue: Based on the logs it seems the cache is not working and the dependencies are downloaded each team. This could be due to an older cache being used. Probably worth increasing to v2 to get all deps in the cache.
f606343 to
11f1ba1
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
669be61 to
a31cc6f
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
a31cc6f to
1837732
Compare
This comment has been minimized.
This comment has been minimized.
1837732 to
8dcc308
Compare
This comment has been minimized.
This comment has been minimized.
8dcc308 to
b626996
Compare
b626996 to
7e2f571
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
7e2f571 to
484e989
Compare
This comment has been minimized.
This comment has been minimized.
484e989 to
1720659
Compare
PR Reviewer Guide 🔍
|
| name: Restoring Windows tools cache | ||
| keys: | ||
| - chocolatey-cache-full-v5-{{ arch }}-{{ checksum ".circleci/chocolatey.config" }} | ||
| - windows-tools-cache-v2-{{ arch }} |
There was a problem hiding this comment.
suggestion: I don't think this caching logic will work... Previously we generated this based on the choco config (thus when a dependency version in the config change, the cache key would change). But now the cache key is static and since caches are immutable this is probably not the right behaviour.
Pull Request Submission Checklist
are release-note ready, emphasizing
what was changed, not how.
What does this PR do?
Where should the reviewer start?
How should this be manually tested?
In CircleCI, run the full Windows pipeline on a test branch:
windows amd64andsign windows amd64pass and produce expected artifacts.windows amd64pass, including SBOM tests that rely on Maven and Python.What's the product update that needs to be communicated to CLI users?
There is no functional CLI behavior change for end users; this PR only changes how Windows CI builds and tests the CLI.