gitlab-ci: adding docs for token gen

CI.md

@@ -37,10 +37,3 @@ Wormhole code is: 8-amusement-drumbeat
 ```
 
 4. This will kickoff the flash and reply with a gitlab pipeline URL.
-
-## Gitlab CI
-
-See the pipelines defined: https://github.com/socallinuxexpo/scale-network/blob/master/.gitlab-ci.yml
-
-Our [autoflash process](./openwrt/docs/AUTOFLASH.md) leverages `gitlab-runners` to be able to interact with real hardware so that
-we can automate the flashing process to test our openwrt images.

README.md

@@ -11,7 +11,8 @@
 ## Table of Contents
 
 - [CONTRIBUTING](./CONTRIBUTING.md)
-- [CI](./CI.md)
+- [GitHub Actions CI](./CI.md)
+- [Gitlab CI](./docs/gitlab-ci.md)
 - [MAPS](./MAPS.md)
 - [SWITCH CONFIG](./switch-configuration/README.md)
 - [OPENWRT](./openwrt/README.md)

docs/gitlab-ci.md

@@ -0,0 +1,20 @@
+# Gitlab
+
+See the pipelines defined: https://github.com/socallinuxexpo/scale-network/blob/master/.gitlab-ci.yml
+
+Our [autoflash process](./openwrt/docs/AUTOFLASH.md) leverages `gitlab-runners` to be able to interact with real hardware so that
+we can automate the flashing process to test our openwrt images.
+
+## Generate token for runner
+
+1. Navigate to the [runner page](https://gitlab.com/groups/socallinuxexpo/-/runners)
+
+1. Click the `New Group Runner`
+
+1. Ensure that you have the right tags for the runner. These should match the `.gitlab-ci` jobs you expect to run.
+
+1. Add a description and set an appropriate timeout if different from the default.
+
+1. Take the token and place it on the runner.
+> NOTE: Runners cannot be configured with additional tags or config. These are encoded into the token. Should these
+config need to change you'll need a new token.