env Variables ara not resolved inside job name #444

New Issue

yekanchi · 2023-12-10T06:51:11Z

yekanchi commented

2023-12-10 06:51:11 +00:00

Tried to use env variables inside job name but the variables do not resolve:
it resolves inside run section.

defaults:
  run:
    shell: powershell
env:
  TEST_VAR: "TEST_Variable_12455"    
jobs:
  Build:
    runs-on: win-x64
    steps:
      - name: Checkout ${{ env.TEST_VAR}}
        uses: actions/checkout@v3
      - name: "Test Variables: "
        run: Write-Host ""${{ env.TEST_VAR}}""

in the above workflow - name: Checkout ${{ env.TEST_VAR}} part does not work properly.

Tried to use env variables inside job name but the variables do not resolve: it resolves inside run section. ```yaml defaults: run: shell: powershell env: TEST_VAR: "TEST_Variable_12455" jobs: Build: runs-on: win-x64 steps: - name: Checkout ${{ env.TEST_VAR}} uses: actions/checkout@v3 - name: "Test Variables: " run: Write-Host ""${{ env.TEST_VAR}}"" ``` in the above workflow ` - name: Checkout ${{ env.TEST_VAR}}` part does not work properly.

yekanchi referenced this issue

2024-03-04 04:28:47 +00:00

`configuration variables` does not work for `runs-on` #445

sillyguodong referenced this issue

2024-03-04 05:24:50 +00:00

`configuration variables` does not work for `runs-on` #445

sillyguodong added the

kind

bug

label 2024-03-04 05:51:29 +00:00

sillyguodong self-assigned this 2024-03-04 05:51:34 +00:00

sillyguodong commented

2024-03-06 03:01:47 +00:00

@yekanchi Hi, after reviewing the code, I found that implementing this feature at the moment may be difficult.
and I found that there are also some similar issues in the Gitea repository.

and i think it will be resolved if https://github.com/go-gitea/gitea/issues/24604 is completed.

@yekanchi Hi, after reviewing the code, I found that implementing this feature at the moment may be difficult. and I found that there are also some similar issues in the Gitea repository. - https://github.com/go-gitea/gitea/issues/28207 - https://github.com/go-gitea/gitea/issues/26307 ... and i think it will be resolved if https://github.com/go-gitea/gitea/issues/24604 is completed.

👍 1

yekanchi commented

2024-03-06 12:30:41 +00:00

@yekanchi Hi, after reviewing the code, I found that implementing this feature at the moment may be difficult.
and I found that there are also some similar issues in the Gitea repository.

https://github.com/go-gitea/gitea/issues/28207

https://github.com/go-gitea/gitea/issues/26307
...

and i think it will be resolved if https://github.com/go-gitea/gitea/issues/24604 is completed.

thanks for the review. i will follow the mentioned gitea issue.

> @yekanchi Hi, after reviewing the code, I found that implementing this feature at the moment may be difficult. > and I found that there are also some similar issues in the Gitea repository. > - https://github.com/go-gitea/gitea/issues/28207 > - https://github.com/go-gitea/gitea/issues/26307 > ... > > and i think it will be resolved if https://github.com/go-gitea/gitea/issues/24604 is completed. > thanks for the review. i will follow the mentioned gitea issue.

Sign in to join this conversation.

No Milestone

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gitea/act_runner#444