问题
I am writing automated script for cloning GitHub source code to local machine.
I failed after installing Git in my script, it asked for close/open powershell.
So I am not able to clone code automatic after installing Git.
Here is my code:
iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))
choco install -y git
refreshenv
Start-Sleep -Seconds 15
git clone --mirror https://${username}:${password}@$hostname/${username}/$Projectname.git D:\GitTemp -q 2>&1 | %{ "$_" }
Error:
git : The term 'git' is not recognized as the name of a cmdlet,
function, script file, or operable program.
Check the spelling of the name, or if a path was included,
verify that the path is correct and try again.
Please let me what should I put for reboot PowerShell without exiting?
回答1:
You have a bootstrapping problem:
refreshenv
(an alias forUpdate-SessionEnvironment
) is generally the right command to use to update the current session with environment-variable changes after achoco install ...
command.However, immediately after installing Chocolatey itself,
refreshenv
/Update-SessionEnvironment
themselves are only available in future PowerShell sessions, because loading these commands happens via code added to profile$PROFILE
, based on environment variable$env:ChocolateyInstall
.
That said, you should be able to emulate what Chocolatey does when $PROFILE
is sourced in future sessions in order to be able to use refreshenv
/ Update-SessionEnvironment
right away, immediately after installing Chocolatey:
iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))
choco install -y git
# Make `refreshenv` available right away, by defining the $env:ChocolateyInstall
# variable and importing the Chocolatey profile module.
# Note: Using `. $PROFILE` instead *may* work, but isn't guaranteed to.
$env:ChocolateyInstall = Convert-Path "$((Get-Command choco).Path)\..\.."
Import-Module "$env:ChocolateyInstall\helpers\chocolateyProfile.psm1"
# refreshenv is now an alias for Update-SessionEnvironment
# (rather than invoking refreshenv.cmd, the *batch file* for use with cmd.exe)
# This should make git.exe accessible via the refreshed $env:PATH, so that it
# can be called by name only.
refreshenv
# Verify that git can be called.
git --version
Note: The original solution used . $PROFILE
instead of Import-Module ...
to load the Chocolatey profile, relying on Chocolatey to have updated $PROFILE
already at that point. However, ferventcoder points out that this updating of $PROFILE
doesn't always happen, so cannot be relied upon.
回答2:
You can try and use Update-SessionEnvironment:
Updates the environment variables of the current powershell session with any environment variable changes that may have occured during a Chocolatey package install.
That will test if that change is still effective after the chocolatey call.
If not, one easy workaround would be at least to use an absolute path for calling git
.
To call Git from Powershell:
new-item -path alias:git -value 'C:\Program Files\Git\bin\git.exe'
Then you can try:
git clone --mirror https://${username}:${password}@$hostname/${username}/$Projectname.git D:\GitTemp -q 2>&1 | %{ "$_" }
来源:https://stackoverflow.com/questions/46758437/how-to-refresh-the-environment-of-a-powershell-session-after-a-chocolatey-instal