Make sure package verification failure fails the AppVeyor build (#6337)

This commit is contained in:
Travis Plunk
2018-03-08 15:58:59 -08:00
committed by Dongbo Wang
parent e42c1db395
commit 2d58072460
2 changed files with 4 additions and 13 deletions
+3 -12
View File
@@ -446,7 +446,6 @@ function Get-ReleaseTag
# Implements AppVeyor 'on_finish' step
function Invoke-AppveyorFinish
{
$exitCode = 0
try {
$releaseTag = Get-ReleaseTag
@@ -488,7 +487,7 @@ function Invoke-AppveyorFinish
}
# Smoke Test MSI installer
log "Smoke-Testing MSI installer"
Write-Log "Smoke-Testing MSI installer"
$msi = $artifacts | Where-Object { $_.EndsWith(".msi")}
$msiLog = Join-Path (Get-Location) 'msilog.txt'
$msiExecProcess = Start-Process msiexec.exe -Wait -ArgumentList "/I $msi /quiet /l*vx $msiLog" -NoNewWindow -PassThru
@@ -498,7 +497,7 @@ function Invoke-AppveyorFinish
$exitCode = $msiExecProcess.ExitCode
throw "MSI installer failed and returned error code $exitCode. MSI Log was uploaded as artifact."
}
log "MSI smoke test was successful"
Write-Log "MSI smoke test was successful"
# only publish assembly nuget packages if it is a daily build and tests passed
if((Test-DailyBuild) -and $env:TestPassed -eq 'True')
@@ -552,14 +551,6 @@ function Invoke-AppveyorFinish
}
catch {
Write-Host -Foreground Red $_
}
finally {
# A throw statement would not make the build fail. This function is AppVeyor specific
# and is the only command executed in 'on_finish' phase, so it's safe that we request
# the current runspace to exit with the specified exit code. If the exit code is non-zero,
# AppVeyor will fail the build.
# See this link for details:
# https://help.appveyor.com/discussions/problems/4498-powershell-exception-in-test_script-does-not-fail-build
$host.SetShouldExit($exitCode)
throw $_
}
}
+1 -1
View File
@@ -2286,7 +2286,7 @@ function Test-FileWxs
}
catch
{
#ignore any error pushing the artifact
Write-Warning -Message "Pushing MSI File fragment failed."
}
}