BatchScriptExecutor Execute does not maintain state during directory changes about localappveyor HOT 5 CLOSED

I have a quick and dirty work around.
Rather than executing immediately, generate a bat or ps1 with the steps. Execute the file generated at the end of ScriptBlockExecuterStep. Execute or when switching between batch and powershell, discard the file after execution to prevent multiple execution.

from localappveyor.

This is by design. Each line is, effectively, it's own script. This is true for both localappveyor and appveyor itself.

To achieve what you want you've to make the line a block. This is YAML sintax and there are multiple subtle different ways of represent blocks.

Your example would be:

build_script:
  - |-
    echo --------------------------------------------------------------------------------
    echo Build tinyformat
    mkdir build
    cd build 
    cmake -G "%COMPILER%" .. 
    cmake --build . --config %CONFIGURATION%

If you look at appveyor.yml reference, you can see that you can even mix both batch and powershell scripts for example. Just because the lines are contiguous it doesn't mean they run within the same context.

install:
  # by default, all script lines are interpreted as batch
  - echo This is batch
  # to run script as a PowerShell command prepend it with ps:
  - ps: Write-Host 'This is PowerShell'
  # batch commands start from cmd:
  - cmd: echo This is batch again
  - cmd: set MY_VAR=12345

from localappveyor.

That’s good to know I guess I chose the wrong app to test with. I’ll raise an issue with the tinyformat people instead. Thanks.

from localappveyor.

I hope AppVeyor is not doing something smart and joining lines together if they are of the same type. At least is not what they state in their docs.

I've added few tests to represent these scenarios: 26fb516

from localappveyor.

It looks like appveyor might be doing something funky behind the scenes. Tinyformat's appveyor reports that they're passing with the current config.

from localappveyor.