matelich
Posts: 7
Joined: Fri Dec 05, 2008 6:38 pm

issue with /execute in build script

We switched to Azure signing with the helpful instructions on the site, works great on our mainline build script, looks like this:

Code: Select all

	echo ;aic > aic.txt
	echo SetProperty ProductName="Zetec Software (Prototype)" >> aic.txt
	echo SetAzureKeyVaultSecret %AZURE_KEYVAULT_SECRET% >> aic.txt
	echo Build -buildslist EddynetVelocity  >> aic.txt
	%ADVANCEDINSTALLER% /execute %EDDYNETVELOCITYPROJECTFILE% aic.txt -nofail >> %ADVANCEDINSTALLEROUT%
However, the same signing settings in my .aip and same script section is failing on my release candidate branch. The output is
Parse error in file: "e:\dev\eddynet-EVR_V1_19_0_0\projects\aic.txt" at line: [1] column: [0] (code: not well-formed (invalid token)).
I can manually run the /execute command in a prompt with no problem. Any suggestions?
Catalin
Posts: 7504
Joined: Wed Jun 13, 2018 7:49 am

Re: issue with /execute in build script

Hello,

I think this might have to do with the following line:

Code: Select all

echo ;aic > aic.txt
what does that exactly do? If I'm not mistaken, it's used to write to the aic.txt file?

I'm asking this because the aic.txt file should already contain that, so adding it again might trigger this parsing error.
I can manually run the /execute command in a prompt with no problem
Do you run only the execute command, or the entire script? If you encapsulate that into a batch file and run it whole, does it still work?

Best regards,
Catalin
Catalin Gheorghe - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
matelich
Posts: 7
Joined: Fri Dec 05, 2008 6:38 pm

Re: issue with /execute in build script

Yes, I was using that to dynamically generate 3 different flavors of aic.txt. I since realized you could use %ENV% vars in the aic.txt.

Unfortunately, it doesn't seem to have helped. I reworked the script to use:

Code: Select all

;aic 
SetProperty ProductName="%EVRBuildProductName%" 
SetAzureKeyVaultSecret %AZURE_KEYVAULT_SECRET%
Build -buildslist %EVRBuildList%  
But I'm still getting the same parse error message.

I can still use this scheme successfully in a powershell prompt and the old scheme is still working fine on my mainline build. I'm guessing that one batch file is doing something odd that throws off AI, but I can't think what it might be.

Return to “Common Problems”