Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regression - env var yaml integer no longer exported to enviroment #1640

Closed
ameergituser opened this issue May 9, 2024 · 1 comment
Closed
Labels
area: env Changes related to environment variables.

Comments

@ameergituser
Copy link

input

version: '3'

tasks:
  default:
    env:
      CC: x86_64-w64-mingw32-gcc
      CGO_ENABLED: 1
      GOOS: windows
      GOARCH: amd64
    cmds:
      - echo CC=$CC CGO_ENABLED=$CGO_ENABLED GOOS=$GOOS GOARCH=$GOARCH

output: Task version: v3.36.0

CC=x86_64-w64-mingw32-gcc CGO_ENABLED=1 GOOS=windows GOARCH=amd64

output: Task version: v3.37.0

CC=x86_64-w64-mingw32-gcc CGO_ENABLED= GOOS=windows GOARCH=amd64

Comment:
Note CGO_ENABLED env var was not set for v3.37.0
Converting the integer var into a string works around this issue.

  • Operating system: Linux dev 5.15.0-106-generic 116-Ubuntu
  • Experiments enabled: No
@task-bot task-bot added the state: needs triage Waiting to be triaged by a maintainer. label May 9, 2024
@andreynering andreynering added type: bug Something not working as intended. area: env Changes related to environment variables. and removed state: needs triage Waiting to be triaged by a maintainer. labels May 9, 2024
@andreynering
Copy link
Member

Hi @ameergituser,

This was fixed by @vmaerten on #1641 and I'll release a patch in minutes.

@pd93 pd93 removed the type: bug Something not working as intended. label Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: env Changes related to environment variables.
Projects
None yet
Development

No branches or pull requests

4 participants