fixup! Add a build definition for Azure DevOps

It is not strictly necessary to start a command in PowerShell with `&`,
but it is safer.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
This commit is contained in:
Johannes Schindelin
2018-12-19 13:23:29 +01:00
parent 02451caa3c
commit a4c8e46019

View File

@@ -179,22 +179,22 @@ jobs:
if (Test-Path $path) {
cd $path; c
if (Test-Path .git) {
git init; c
& git init; c
} else {
git status
& git status
}
} else {
git init $path; c
& git init $path; c
cd $path; c
}
git config core.autocrlf false; c
git config core.untrackedCache true; c
& git config core.autocrlf false; c
& git config core.untrackedCache true; c
if (($set_origin -ne 0) -and !(git config remote.origin.url)) {
git remote add origin $url; c
& git remote add origin $url; c
}
git fetch --depth=1 $url master; c
git reset --hard FETCH_HEAD; c
git clean -df; c
& git fetch --depth=1 $url master; c
& git reset --hard FETCH_HEAD; c
& git clean -df; c
}
# Initialize Git for Windows' SDK
@@ -205,7 +205,7 @@ jobs:
"/git-sdk-64/`n/test-cache/`n" | Out-File -NoNewLine -Encoding ascii -Append "$(Build.SourcesDirectory)\.git\info\exclude"
displayName: 'Initialize the Git for Windows SDK'
- powershell: |
git-sdk-64\git-cmd --command=usr\\bin\\bash.exe -lc @"
& "git-sdk-64\git-cmd.exe" --command=usr\\bin\\bash.exe -lc @"
export MAKEFLAGS=-j10
export DEVELOPER=1
export NO_PERL=1