New MaxVersionsPerPackage to clean packages #180
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- updated SDK in global.json - validated regression and unit tests
- added new in memory package database
|
@ErikApption Thanks for you contribution! This code looks good to me. |
|
@seriouz done - let me know if you need anything else, |
seriouz
approved these changes
Sep 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added a new optional setting
MaxVersionsPerPackageto auto delete packages when there are more thanMaxVersionsPerPackageversions. We have been running out of space regularly on our bagetter server and been looking for a system to auto clean.I added corresponding unit tests, this required adding a
InMemoryPackageDatabaseimplementation. All unit tests do pass.