Job outputs doesn't works on Windows runner.

Description

Hi, I use the sample about job outputs from the GitHub documentation (see code below). When I use “ubuntu-latest” for the job1, I can use job1 outputs into Job2.

When I use my self-hosted windows runner for the job1, I can’t use job1 outputs into Job2. In all tests, I use my self-hosted windows runner for the job2

In Diag files, we can see the “needs” node does not contains data informations in sub node “outputs”.

it looks like a bug 😃. Thanks for your help.

To reproduce

Just change the runner used on job1.

Runner version and OS

Version 2.298.2 on Windows Server 2019 Datacenter.

Script

name: test
on:
  pull_request:
    branches: [ master ]

jobs:
  job1:
    runs-on: [self-hosted, windows]
    #runs-on: ubuntu-latest
    outputs:
      output1: ${{ steps.step1.outputs.test }}
      output2: ${{ steps.step2.outputs.test }}
    steps:
      - id: step1
        run: echo "test=hello" >> $GITHUB_OUTPUT
      - id: step2
        run: echo "test=world" >> $GITHUB_OUTPUT
  job2:
    runs-on: [self-hosted, windows, csd-back]
    needs: job1
    steps:
      - run: echo ${{needs.job1.outputs.output1}} ${{needs.job1.outputs.output2}}

[NeocaseDCosta]

In fact the good answers for me is the syntax to use PowerShell instead of Bash. So the answers is use : run: echo "secondword=world" | Out-File -FilePath $Env:GITHUB_OUTPUT -Encoding utf8 -Append Instead of: run: echo "secondword=world" >> $GITHUB_OUTPUT I hope this can help someone else.

[LeonSnajdr]

Oct 25, 2022

There is also a shorter way to write this use instead of >> $GITHUB_OUTPUT in bash >> $Env:GITHUB_OUTPUT in PowerShell