-
Notifications
You must be signed in to change notification settings - Fork 47
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
First wave of build/test updates #224
First wave of build/test updates #224
Conversation
and also unfinished about topic
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.
Looks good, just trying to get CI going.
|
||
<ModuleVersion>1.1.2</ModuleVersion> | ||
|
||
<ArtifactsPath>$(MSBuildThisFileDirectory)artifacts</ArtifactsPath> |
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.
What a funny variable. I looked it up and sure enough MSBuildThisFileDirectory
"Include[s] the final backslash in the path."
additionalParams.Add("Verbose", verboseEnabled); | ||
|
||
return additionalParams; | ||
} | ||
|
||
private static T GetPropertyValue<T>(object value, string propertyName, T defaultValue = default) |
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.
Was this added in order to replace a library?
I can't seem to get Pester running (yes even after updating and importing Pester 5) or the package task to work. Will ping you Monday. |
Thank you so much for getting this started Patrick! Honestly you figured out the things I was going to have issues with (what with the dynamic removal, nuspec, and directory props artifacts thing), worked out great. |
PR Summary
Haven't touched the pipeline stuff yet, just getting the build script in order.
Also updated the tests to be Pester 5 compatible.
PR Context