j33pfan
Posts: 6
Joined: Wed Aug 07, 2019 2:53 pm

Azure DevOps build broke with Advanced Installer Build 2.0.4 release [SOLVED]

Yesterday, our build pipeline was working fine with Advanced Installer Build 2.0.3. Today it failed with:
##[error]Failed to execute Advanced Installer task. Error: SetOutputLocation -path "LakeShore.Calibration.Installer/SetupFiles"
On looking at the logs, I noticed that the version of Advanced Installer Build had changed to 2.0.4.

Yesterday, the successful log shows the following build path being used (with the build directory automatically pre-pended):
SetOutputLocation -path "D:\a\1\s\LakeShore.Calibration.Installer\SetupFiles"
Is this change in how the output output location path is used expected? If so, how should I fix it in our build pipeline?
Last edited by j33pfan on Fri Sep 04, 2020 6:06 pm, edited 1 time in total.
Marco28
Posts: 16
Joined: Fri Sep 15, 2017 6:14 am

Re: Azure DevOps build broke with Advanced Installer Build 2.0.4 release

We are having the same issue. Do you know when this is solved?
j33pfan
Posts: 6
Joined: Wed Aug 07, 2019 2:53 pm

Re: Azure DevOps build broke with Advanced Installer Build 2.0.4 release

I attempted to work around the issue by explicitly prepending the path with "$(Pipeline.Workspace)/". While the error was no longer displayed, the installer executable was not created in that output directory. So, we're kind-of stuck.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Azure DevOps build broke with Advanced Installer Build 2.0.4 release

Hi,

I am not sure why this happens. We have tested the scenario but cannot replicate any such issue.

Could you share with us a few screenshots with all the settings you configured for your Advanced Installer Build Task? Also, please send us the complete build log of our installer task so we can fully check it.

If there are sensitive data into your build task configuration/build log content please send us the above resources by email at support at advancedinstaller dot com.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Azure DevOps build broke with Advanced Installer Build 2.0.4 release

Hi j33pfan,

Could you please set the "Output Package folder" field like this:

$(Pipeline.Workspace)\LakeShore.Calibration.Installer\SetupFiles

or like this

$(Pipeline.Workspace)

and see how this works?

Please use the backslash (\) as folder path separator and see if this helps.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
j33pfan
Posts: 6
Joined: Wed Aug 07, 2019 2:53 pm

Re: Azure DevOps build broke with Advanced Installer Build 2.0.4 release

This is how it was originally configured, and it was working fine up until yesterday.

Code: Select all

  - task: AdvancedInstaller@2
    displayName: 'Build installer'
    inputs:
      advinstLicense: '$(AI.LicenseKey)'
      aipPath: 'LakeShore.Calibration.Installer\LakeShore.Calibration.Installer-Dev.aip'
      aipBuild: 'DevBuild'
      aipOutputFolder: 'LakeShore.Calibration.Installer/SetupFiles'
      aipExtraCommands: SetVersion $(Version)
The path is using a forward slash. But, that was working just fine until yesterday.

This is what I tried this morning to work around the issue. There was no error. But the installer executable was not created in the output folder.

Code: Select all

  - task: AdvancedInstaller@2
    displayName: 'Build installer'
    inputs:
      advinstLicense: '$(AI.LicenseKey)'
      aipPath: 'LakeShore.Calibration.Installer\LakeShore.Calibration.Installer-Dev.aip'
      aipBuild: 'DevBuild'
      aipOutputFolder: '$(Pipeline.Workspace)\LakeShore.Calibration.Installer\SetupFiles'
      aipExtraCommands: SetVersion $(Version)
I attached two log files. One when it was working, and the other when it broke. There were no pipeline configuration changes made between these builds.

Thank you for your assistance.
Attachments
Failing log.txt
(1.92 KiB) Downloaded 519 times
Successful log.txt
(2.17 KiB) Downloaded 498 times
Marco28
Posts: 16
Joined: Fri Sep 15, 2017 6:14 am

Re: Azure DevOps build broke with Advanced Installer Build 2.0.4 release

I have got it working by prepending the path with $(Build.Repository.LocalPath)\

For the OP this would be

Code: Select all

aipOutputFolder: '$(Build.Repository.LocalPath)\'LakeShore.Calibration.Installer/SetupFiles'
Marco28
Posts: 16
Joined: Fri Sep 15, 2017 6:14 am

Re: Azure DevOps build broke with Advanced Installer Build 2.0.4 release

And replace the forward slashes with back slashed

Code: Select all

aipOutputFolder: '$(Build.Repository.LocalPath)\LakeShore.Calibration.Installer\SetupFiles'
j33pfan
Posts: 6
Joined: Wed Aug 07, 2019 2:53 pm

Re: Azure DevOps build broke with Advanced Installer Build 2.0.4 release [SOLVED]

Thank you very much Marco28! That worked like a charm! Still not sure why the change occurred. But, I am very happy to have my build pipeline running again!
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Azure DevOps build broke with Advanced Installer Build 2.0.4 release [SOLVED]

Hi,

Thank you too Marco for your insights on this. Your help is greatly appreciated.

I have further debated this with my dev team and, indeed it seems that starting with our last version (2.0.4) of Advanced Installer build task there are no longer supported relative paths in the "Output Package Folder" field. So therefore you will have to make sure you specify a full path in this field.

We apologize if this caused any inconveniences for you. Thank you for your understanding.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Azure DevOps build broke with Advanced Installer Build 2.0.4 release [SOLVED]

Hi,

Just an update on this.

We have just released a new version of Advanced Installer Build task (v2.0.5) and starting with this version relative paths are supported again in the "Output Package Folder" field. So rebuilding this task with your original configuration should work again.

Hope this helped.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”