Compile step fails

[peterz84]

Getting an error in the compile step:

Script:

trigger: none
name: $(Build.BuildId)

variables:
- name: 'AppVersion'
  value: '1.0.0.*'
- name: 'dockerimage'
  value: 'mcr.microsoft.com/businesscentral/onprem:1910-cu2-nl'
- name: 'bc_license'
  value: 'c:\Licenses\15.flf'

pool:
  name: BHNL Business Central Pool

steps:
- checkout: self
  clean: true

#- task: PowerShell@2
#  inputs:
#    targetType: 'inline'
#    script: 'write-host "##vso[task.setvariable variable=alops-licenseid]----------------"'

- task: ALOpsDockerStart@1
  inputs:
    docker_image: '$(dockerimage)'
    docker_parameters: |
      -v "D:\CustomSQLbak:C:/temp"
      -v "C:\Licenses:C:/licenses"
      -e licensefile=C:\licenses\15.flf
    sql_backup_file: 'c:\temp\KNK2020R1_CU2_NL.bak'

- task: ALOpsDockerWait@1
  inputs:
    search_string: 'Ready for connections!'

- task: ALOpsAppCompiler@1
  displayName: 'ALOPS Compile'
  inputs:
    usedocker: true
    targetproject: './app.json'
    nav_app_version: '$(AppVersion)'

- task: ALOpsAppPublish@1
  displayName: 'ALOPS Publish'
  inputs:
    usedocker: true
    nav_artifact_app_filter: '*.app'

#- task: ALOpsDockerRemove@1
#  enabled: true
#  condition: always()  

As you can see I disabled the DockerRemove step, to check if the app file does exist and it seems to exist in the container:

What might be the problem? Is the name too long? Does it not like the [W1] at the end?

[AdminHodor]

Dear @peterz84 ,

The pipeline looks fine. The length of the name should not matter, but I'll setup a test for this on our side.

Does the App-Name contain any 'special' characters ? We noticed in some cases ALC.EXE replaces some characters, resulting in another output file then expected. If you see the possibility emailing the [app.json] to [admin@hodor.be] I'll be glad to setup a test-pipeline trying to replica the behaviour. Ofcourse we will not disclose any information received.

Kind regards,

[peterz84]

The square brackets were the problem!

[AdminHodor]

Thanks for closing the issue, never the less we'll adjust our test-pipelines for this cases and follow up with proper updates handling this.