Configure the volumes path using variables or secrets

[Hentioe]

For example, I'm copying the build artifacts to the host's path in one of the steps, but I don't want to publicize my server's path, or I want to make woodpecker-ci's configuration more generic. Can I use variables or secrets instead of hardcoding?

deploy-to-host:
  image: busybox
  commands:
    - cp -R public /hugo-blog/
  volumes:
    - <MY_HOST_PATH>:/hugo-blog

[qwerty287]

Can I use variables

With global env vars, this is possible.

or secrets

This is not possible currently as secrets are not passed to the preprocessor/env var substitution.

[anbraten]

Looking at it. It this really working to overwrite the env for a specific step (never saw that before):

steps:
  build:
-   image: golang:1.18
+   image: golang:${GOLANG_VERSION}
    commands:
      - [...]
    environment:
      - [...]
+     - WOODPECKER_ENVIRONMENT=GOLANG_VERSION:1.18

[anbraten]

never mind is already updated in the next docs ...

[Hentioe]

🥳👍 Thanks to @qwerty287's answer, I managed to achieve my goal through global environment variables.