-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Description
Describe the bug
When using workflow level environment variables they do not work when I use them to substitute for jobs.build.name or jobs.build.runs-on. See workflow file below for example:
name: Testing workflow leve env vars
on:
push:
branches:
- develop
env:
aws_account: cfaittoolsnp
environment: dev
jobs:
build:
name: Deploy|${{ env.aws_account }}
runs-on: ${{ env.aws_account }}
steps:
- name: Checkout
uses: actions/checkout@v2
- name: Init
run: |
echo ${{ env.aws_account }}
To Reproduce
Steps to reproduce the behavior:
1.- Run the workflow file above to receive the following error:
The workflow is not valid. .github/workflows/dev.yml (Line: 15, Col: 11): Unrecognized named-value: 'env'. Located at position 1 within expression: env.aws_account,.github/workflows/dev.yml (Line: 16, Col: 14): Unrecognized named-value: 'env'. Located at position 1 within expression: env.aws_account
Expected behavior
The expected behavior is that using the workflow file above the build.name would be Deploy|cfaittoolsnp and the build.runs-on would be cfaittoolsnp.
Runner Version and Platform
Running latest version of linux self-hosted runner.
OS of the machine running the runner? linux (ubuntu 18.04)