Environment variable "on" different based on declaration place

Hi,

I’m running this config local/remotely and I’m getting different env V value. Is on special value? Is there docs about it? This is kind of bug for me, because in all 3 jobs V should be set to on

docker: &docker
  docker:
    - image: busybox
    
version: 2
jobs:
  build:
    <<: *docker
    environment:
      V: on
    steps:
      - run: env # displays: true
          
  test:   
    <<: *docker
    steps:
      - run:
          command: env # displays: 1
          environment:
            V: on

  lint:
    <<: *docker
    steps:
      - run: V=on env # displays: on

Maybe it is getting converted to boolean true? Try putting it in quotes.

That’s right. Didn’t know about this yaml “feature”

From yaml 1.1 spec:
For example, the boolean “ true ” might also be written as “ yes

But there is nothing about “on”.

Thanks

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.