-
Notifications
You must be signed in to change notification settings - Fork 903
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
(#3461,#3487) Prevent dependency resolution from downgrading packages #3486
Conversation
This PR is in draft as I still need to run more tests as well as add more tests. And apparently bring the branch in line with the develop branch. |
64f2ded
to
1731d3e
Compare
37574fb
to
7e225aa
Compare
a4cf193
to
8b82e88
Compare
@corbob I am going to rebase this PR onto the head of develop, since my PR has now been merged, which will make reviewing this PR easier. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have left a few comments for review.
tests/packages/hasfailingnesteddependency/1.0.0/hasfailingnesteddependency.nuspec
Outdated
Show resolved
Hide resolved
tests/packages/hasnesteddependency/1.0.0/hasnesteddependency.nuspec
Outdated
Show resolved
Hide resolved
@gep13 I'll add it here instead of in the conversations... The var nullResult = packageResultsToReturn.GetOrAdd(packageName, new PackageResult(installedPackage.PackageMetadata, pathResolver.GetInstallPath(installedPackage.PackageMetadata.Id)));
nullResult.Messages.Add(new ResultMessage(ResultType.Error, logMessage)); I think, I did the The |
695754d
to
950ce5d
Compare
e1a6373
to
8841937
Compare
tests/packages/hasnesteddependency/1.0.0/hasnesteddependency.nuspec
Outdated
Show resolved
Hide resolved
7d074d5
to
0b93f0c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
When a package dependency fails to install, we will now fail the package as well.
Some of these package already existed on our internal repository, while some of them have been added for the tests being added.
We have added some tests for the install all command. This adds a new package source to the testing environment so that we can run the tests locally and in Test Kitchen.
Add a number of tests for dependency scenarios where we did not have tests before.
In the NugetService we were using a nullResult variable to allow us to add messages to the result. We do not need this variable if we're only adding a single message. This commit removes the unnecessary variables.
This updates the `test-chocolateypath` package to have a description and removes the unneeded comments. This is related to a GitLab MR that noted these things when bringing this package into the internal repository. This reverts commit ffd9aab4b40dc8b47b84de5f3ce91ea22fda7a6d.
Address review comments by using full version string for PackageResults, and use case insensitive compares when determining if a package has dependencies that failed to install.
This adds logic to the Invoke-Tests file to output if a package failed fail to pack. This allows for improved developer experience by indicating if packages fail to build. This also allows impromptu improvement to the developer experience by allowing simple changes to the script to throw in place of outputting an errorand thus not allowing tests to run without the full set of test packages.
This commit removes templated values from the test packages being added in this PR.
23b5661
to
ff7009e
Compare
Description Of Changes
--allow-downgrade
is not specified.Motivation and Context
Testing
./build.bat --testExecutionType=all --shouldRunOpenCover=false
Operating Systems Testing
Change Types Made
Change Checklist
Related Issue