Last week the secret for accessing our KeyVault in Azure expired, and after rotating this key and updating our environment variables, Advanced Installer no longer builds in GitHub or Azure Devops. We have since rotated the key out again but this has not resolved the issue.
Builds ran in GitHub and ADO both fail at the same stage, "Preparing files"
This is a dulled-down version of our build pipe, but running this directly in PowerShell builds perfectly fine.
Code: Select all
$binPath = "{0}\Caphyon\Advanced Installer 20.2.1\bin\x86" -f ${env:ProgramFiles(x86)}
$advancedInstaller = "$binPath\AdvancedInstaller.com"
. $advancedInstaller /RegisterCI $env:LICENCE_KEY
$AdvancedInstallerProject = "MEM Patching Optimizer.aip"
$AdvancedInstallerUpdaterProject = "MEMPatchingOptimizer-UpdaterConfig.aip"
$AdvancedInstallerCommand = "build.aic"
. $advancedInstaller /edit "$AdvancedInstallerProject" /SetVersion 1.1.6.0
. $advancedInstaller /execute $AdvancedInstallerProject $AdvancedInstallerCommand -nofail
. $advancedInstaller /build $AdvancedInstallerProjectThe only time GitHub and ADO successfully build is when we remove the Digital Signature option entirely (remove the AIC file)
I came across both of these forum posts but ruled out both of these as the issue by rotating our certificate secret and upgrading from 19.5 to 20.2.1
viewtopic.php?t=40656&start=30
viewtopic.php?f=2&t=51175
I've attached both my AIP and AIC for reference.
I contacted Advanced Installer support via email yesterday but have not received a response.
I had thought that the old secret was still somehow being used or referenced, but I see no reference to it in my AIP files anywhere.
Is anyone able to shed any light on this issue?
FOLLOW US
Get the latest news in Application Packaging