GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||
GeezerVison is showing github.com — Make it easier to install the dotnet CLI tools by JamesWTruher · Pull Request #1139 · PowerShell/PSScriptAnalyzer Conversation
Contributor
PR SummarySometimes the build of script analyzer fails because version specified in PS> ./build.ps1 -bootstrap will determine which version of the CLI is needed, validate whether the proper version is already present, and if not, will install it. This does not validate whether the net452 targeting framework is installed, that must be done manually. PR Checklist
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactionsAlso harden logic for running the installation script
Collaborator
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
5 of 6 tasks
…e starting to build
James Truher (JamesWTruher)
removed request for
Travis Plunk (TravisEz13) and
Rob Holt (rjmholt)
… dotnet CLI update build script to handle WMF4 better (theoretically) Use output of dotnet --version if there are problems with --list-sdks set failure of finding dotnet as a warning, we will attempt to install it during bootstrap this handles the case of a blank slate where dotnet has never been installed
James Truher (JamesWTruher)
force-pushed
the
bootstrap
branch
3 times, most recently
from
badeae0 to
fcf73b6
Compare
James Truher (JamesWTruher)
force-pushed
the
bootstrap
branch
2 times, most recently
from
6d7ec14 to
f0dab58
Compare
James Truher (JamesWTruher)
force-pushed
the
bootstrap
branch
from
f0dab58 to
e3752cc
Compare
Sometimes you can't even invoke dotnet if the version is too low Throw away stderr of dotnet execution under some case and emit it in others. Change ToString of PortableVersion to enable better sorts Sometimes we need the raw version so the installation script works, but sometimes we need to be able to compare it with other versions.
James Truher (JamesWTruher)
force-pushed
the
bootstrap
branch
2 times, most recently
from
4686c98 to
866f35b
Compare
Also add additional verbose output to improve debuggability print response from upload
James Truher (JamesWTruher)
force-pushed
the
bootstrap
branch
from
866f35b to
264652d
Compare
James Truher (JamesWTruher)
force-pushed
the
bootstrap
branch
from
cf72691 to
cd1cbb9
Compare
…ppveyors test result recognition We've had trouble with LANG being set to something that causes problems, so make sure we report what it is. Removed a bit of the verbosity which was added for debugging Fix some errors in the module discovered by the tests Change logic when downloading the dotnet install script Also enforce en_US.UTF-8 language to ensure that appveyor can see our test results
Contributor
Author
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
Christoph Bergmeister (bergmeister)
approved these changes
|
|
Christoph Bergmeister (@bergmeister) thanks for the feedback and here are answers to questions:
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
* Add bootstrapping code to install dotnet * fix logic for downloading proper dotnet installer. * add a version checker for installed dotnet Also harden logic for running the installation script * Add bootstrapping code to install dotnet * Handle missing dotnet, and install it. * Add logic for checking the appropriate version of the Cli tools before starting to build * Update appveyor.psm1 to use build script bootstrapping for installing dotnet CLI update build script to handle WMF4 better (theoretically) * make the hunt for the dotnet executable more generic and try harder to find the exe * Fix typo when checking for usable versions of dotnet * use -version rather than ambiguous -v when installing dotnet * Improve error message when hunting for cli version Use output of dotnet --version if there are problems with --list-sdks * ignore errors when first attempting to find dotnet executable set failure of finding dotnet as a warning, we will attempt to install it during bootstrap this handles the case of a blank slate where dotnet has never been installed * Improve logic for handling a system where dotnet has never been installed * fine tune messages emitted during the hunt for dotnet * additional logic for finding dotnet executable * harden search for dotnet Sometimes you can't even invoke dotnet if the version is too low * Attempt to quieten build output. Throw away stderr of dotnet execution under some case and emit it in others. Change ToString of PortableVersion to enable better sorts * Fix tostring method for portable version * add -Raw flag to Get-GlobalJsonSdkVersion Sometimes we need the raw version so the installation script works, but sometimes we need to be able to compare it with other versions. * Attempt to harden the upload code Also add additional verbose output to improve debuggability print response from upload * upgrade pester version to 4.4.4 * Force the testsuite TestFixture to be named 'Pester' to get through appveyors test result recognition * Emit env:LANG to output before executing tests We've had trouble with LANG being set to something that causes problems, so make sure we report what it is. Removed a bit of the verbosity which was added for debugging * Create tests for build module Fix some errors in the module discovered by the tests * Add additional tests Change logic when downloading the dotnet install script Also enforce en_US.UTF-8 language to ensure that appveyor can see our test results
* Add bootstrapping code to install dotnet * fix logic for downloading proper dotnet installer. * add a version checker for installed dotnet Also harden logic for running the installation script * Add bootstrapping code to install dotnet * Handle missing dotnet, and install it. * Add logic for checking the appropriate version of the Cli tools before starting to build * Update appveyor.psm1 to use build script bootstrapping for installing dotnet CLI update build script to handle WMF4 better (theoretically) * make the hunt for the dotnet executable more generic and try harder to find the exe * Fix typo when checking for usable versions of dotnet * use -version rather than ambiguous -v when installing dotnet * Improve error message when hunting for cli version Use output of dotnet --version if there are problems with --list-sdks * ignore errors when first attempting to find dotnet executable set failure of finding dotnet as a warning, we will attempt to install it during bootstrap this handles the case of a blank slate where dotnet has never been installed * Improve logic for handling a system where dotnet has never been installed * fine tune messages emitted during the hunt for dotnet * additional logic for finding dotnet executable * harden search for dotnet Sometimes you can't even invoke dotnet if the version is too low * Attempt to quieten build output. Throw away stderr of dotnet execution under some case and emit it in others. Change ToString of PortableVersion to enable better sorts * Fix tostring method for portable version * add -Raw flag to Get-GlobalJsonSdkVersion Sometimes we need the raw version so the installation script works, but sometimes we need to be able to compare it with other versions. * Attempt to harden the upload code Also add additional verbose output to improve debuggability print response from upload * upgrade pester version to 4.4.4 * Force the testsuite TestFixture to be named 'Pester' to get through appveyors test result recognition * Emit env:LANG to output before executing tests We've had trouble with LANG being set to something that causes problems, so make sure we report what it is. Removed a bit of the verbosity which was added for debugging * Create tests for build module Fix some errors in the module discovered by the tests * Add additional tests Change logic when downloading the dotnet install script Also enforce en_US.UTF-8 language to ensure that appveyor can see our test results
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.