Drone exec workspace base/path with services

Drone Support
1

Using drone 0.8.4 and came across something of an oddity in how workspace bases/paths are resolved.

Consider this .drone.yml file:

workspace:
  base: /test-base
  path: test-path

services:
  test:
    image: alpine
    detach: true
    commands:
      - pwd

pipeline:
  build:
    image: alpine
    commands:
      - pwd

When running locally

$ drone exec
[test:L0:0s] + pwd
/
[build:L0:0s] + pwd
/test-base/test-path

When running on drone server:

+ pwd
/test-base/test-path

+ pwd
/test-base/test-path

Is it intended for the base/path to NOT be used by the services block when executing locally via the CLI? As it is, I need to reference a config file for a service differently between local/CI runs.

2

Turns out this was fixed, but the drone docs were still pointing to version 0.8.0 for the drone-cli.

drone-cli 0.8.0

$ drone exec
[test:L0:0s] + pwd
/
~/[build:L0:0s] + pwd
/test-base/test-path

drone-cli 0.8.3

drone0.8.3 exec
[test:L0:0s] + pwd
/test-base/test-path
[build:L0:0s] + pwd
/test-base/test-path

Documentation update PR: https://github.com/drone/docs/pull/322