Merge pull request circleci#7031 from circleci/RT-552/update-runner-working-directory

RT-522: update working directory for runner

Author: devinmarieb

jekyll/_cci2/runner-config-reference.adoc

@@ -104,7 +104,9 @@ runner:
 === runner.working_directory
 `$LAUNCH_AGENT_RUNNER_WORK_DIR`
 
-This directory takes a fully qualified path and allows you to control the default working directory used by each job. If the directory already exists, the task agent will need permissions to write to the directory. If the directory does not exist, then the task agent will need permissions to create the directory. If `%s` is present in the value, this value will be replaced with a different value for each job. Note that these directories will not automatically be removed.
+This directory takes a fully qualified path and allows you to control the default working directory used by each job. If the directory already exists, the task agent will need permissions to write to the directory. If the directory does not exist, then the task agent will need permissions to create the directory. If installing multiple launch-agents on the same machine, each launch-agent will need a unique working directory.
+
+NOTE: These directories will not automatically be removed, please see `cleanup_working_directory` to configure cleanup of directory.
 
 Example:
 
@@ -113,6 +115,17 @@ runner:
   working_directory: /opt/circleci/workdir
 ```
 
+CircleCI recommends using a knowable directory, however it is possbile to specify `%s` in the path. This value will be replaced with a different value for each job. This is a substitution that is only knowable at job runtime, under the environment variable `$CIRCLE_WORKING_DIRECTORY`. 
+
+Example:
+
+```yaml
+runner:
+  working_directory: /opt/circleci/%s
+```
+
+
+
 === runner.cleanup_working_directory
 `$LAUNCH_AGENT_RUNNER_CLEANUP_WORK_DIR`
 
@@ -253,4 +266,4 @@ jobs:
     steps:
       - run: echo "Hi I'm on Runners!"
 ```
-The job will then execute using your self-hosted runner when you push the config to your VCS provider.
+The job will then execute using your self-hosted runner when you push the config to your VCS provider.

jekyll/_cci2/runner-installation-linux.adoc

@@ -36,7 +36,7 @@ api:
 runner:
   name: RUNNER_NAME
   command_prefix: ["sudo", "-niHu", "USERNAME", "--"]
-  working_directory: /opt/circleci/workdir/%s
+  working_directory: /var/opt/circleci/workdir
   cleanup_working_directory: true
 ```
 
@@ -71,8 +71,9 @@ These will be used when executing the task agent. These commands must be run as
 ```shell
 id -u USERNAME &>/dev/null || sudo adduser --disabled-password --gecos GECOS USERNAME
 
-sudo mkdir -p /opt/circleci/workdir
-sudo chown -R USERNAME /opt/circleci/workdir
+sudo mkdir -p /var/opt/circleci/workdir
+sudo chown -R USERNAME /var/opt/circleci/workdir
+sudo chmod 0750 /var/opt/circleci/workdir
 ```
 
 Consider running the following additional command if you would like to use certified orbs that work on Cloud on your self-hosted runner, without errors. Note that this enables code to execute root commands on your machine, and changes to the system may persist after the job is run.
@@ -87,8 +88,9 @@ echo "USERNAME ALL=(ALL) NOPASSWD:ALL" >> /etc/sudoers
 ```shell
 id -u USERNAME &>/dev/null || sudo adduser -c GECOS USERNAME
 
-sudo mkdir -p /opt/circleci/workdir
-sudo chown -R USERNAME /opt/circleci/workdir
+sudo mkdir -p /var/opt/circleci/workdir
+sudo chown -R USERNAME /var/opt/circleci/workdir
+sudo chmod 0750 /var/opt/circleci/workdir
 ```
 
 Consider running the following additional command if you would like to use certified orbs that work on Cloud on your self-hosted runner, without errors. Note that this enables code to execute root commands on your machine, and changes to the system may persist after the job is run.

jekyll/_cci2/runner-installation-mac.adoc

@@ -31,7 +31,7 @@ api:
 runner:
   name: RUNNER_NAME
   command_prefix : ["sudo", "-niHu", "USERNAME", "--"]
-  working_directory: /tmp/%s
+  working_directory: /var/opt/circleci/workdir
   cleanup_working_directory: true
 
 logging: