Add option for propagating all environment variables about docker-buildkite-plugin HOT 6 CLOSED

Agreed! Any suggestions on what the syntax for that would look like?

steps:
  - command: "echo \$BUILDKITE_COMMIT"
    plugins:
      - docker#v2.0.0:
         image: bash
         build-environment: true

from docker-buildkite-plugin.

I think something like propagate-env: true or include-all-env: true or automatic-environment: true avoiding something like build as that is a bit confusing re docker build

steps:
  - command: "echo \$BUILDKITE_COMMIT"
    plugins:
      - docker#v2.0.0:
         image: bash
         propagate-env: true

from docker-buildkite-plugin.

Just to be clear… we'd just want the job environment variables sent down from the web UI yeah (the ones in the environment tab)? Not necessarily any environment variables picked up from the Elastic CI Stack environment? (like secrets)

from docker-buildkite-plugin.

I would have thought all of them, e.g what you'd normally have in a naked step?

from docker-buildkite-plugin.

Yeah, I'd imagine that we'd load all of them via the envfile.

from docker-buildkite-plugin.

@toolmantim / @lox have you had any time to poke #80?

from docker-buildkite-plugin.