[PATCH 2/2] CI: allow hashserver to be specified in environment

If the sstate is being mounted into the container then the hashserver
also needs to be shared, and not stored inside the build tree. Mark
BB_HASHSERVE as being set via an environment variable so the GitLab
runner environment can set the correct location.

This fixes a long-standing problem causing substandard reuse, which now
is detected and causes a warning in oe-core[1].

[1] oe-core 491de0db64a ("sanity.bbclass: warn when sstate is outside of
    build dir, but hash equiv database is inside it")

Signed-off-by: Ross Burton <[email protected]>
---
 ci/base.yml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/ci/base.yml b/ci/base.yml
index cb1fe91439..75e87a841c 100644
--- a/ci/base.yml
+++ b/ci/base.yml
@@ -33,6 +33,7 @@ repos:
 
 env:
   BB_LOGCONFIG: ""
+  BB_HASHSERVE: "auto"
 
 local_conf_header:
   base: |
-- 
2.43.0