Have a couple questions about pipelines on runners

Keith Smith_jq4z4m

Here are my questions about my pipeline runner:

1) Exactly where are my commands going to, and are they segregated by process ID or do they run as a block?  For instance if my pipeline involves pulling an account and saving to a variable, will that be available for the next command?

2) If I am running my pipeline in windows, am I to use CMD commands or PS commands?

I ask this because just as a quick test, I set up my pipeline like this:

branches:
  feature/*:
  - step:
    runs-on:
    - self.hosted
    - windows
    name: 'Build'
    script:
      - echo "Build step on feature branches"
      - Get-Location | Write-Output
      - Get-ChildItem | Write-Output

The echo command provides output in the trace but the next two commands do nothing.  What I really want to do is to cd to a folder and do an ant build, but if I can't get even a pwd to produce output, I can't proceed.

Theodora Boudale

Hi Keith,

Windows Runners use PowerShell to run pipeline steps on your windows machine. If you define a variable during a step, it will be available to the rest of the commands in the same step (but not in a subsequent step).

You can use PowerShell commands. Many CMD commands work in PowerShell as well, for example, you can use a cd command.

You mentioned that you don't see output from certain commands.

• Can you please confirm if you are executing the runner in a supported platform that meets the minimum requirements for Windows? Could you also let us what version you are using for the first four items listed in the requirements?
  
  
• What version of the runner are you using and does it show to be the latest one? You can find that in the Pipelines build log in the section Runner.

Kind regards,
Theodora