summaryrefslogtreecommitdiff
path: root/zephyr/README.md
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2021-02-26 12:14:30 -0500
committerCommit Bot <commit-bot@chromium.org>2021-02-26 21:30:25 +0000
commitfceaf8c374321adcc7a145e90831dcb28f49d2be (patch)
tree575aec72cebd57331627bbd7670f8bffdeb1b5c8 /zephyr/README.md
parentb7ef48fec50611807675c19fe3f1180a8010336e (diff)
downloadchrome-ec-fceaf8c374321adcc7a145e90831dcb28f49d2be.tar.gz
zephyr: Update gitlab docs
This is working now, so updates the docs. BUG=b:178731498 BRANCH=none TEST=none Signed-off-by: Simon Glass <sjg@chromium.org> Change-Id: I4afaa0b3d57e7beae71d91d824c3925df54f3374 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2722852 Reviewed-by: Yuval Peress <peress@chromium.org>
Diffstat (limited to 'zephyr/README.md')
-rw-r--r--zephyr/README.md9
1 files changed, 7 insertions, 2 deletions
diff --git a/zephyr/README.md b/zephyr/README.md
index d06925bc70..fc9f7e7c72 100644
--- a/zephyr/README.md
+++ b/zephyr/README.md
@@ -10,8 +10,13 @@ EC.
## Gitlab integration
-As an experiment we have a basic gitlab integration. So far it just builds and
-fails.
+As an experiment we have a basic gitlab integration. It watches the EC repo and
+kicks of a build when new commits appear. So far it just builds for volteer and
+does not run any tests. For firmware branches, it also builds, but fails.
+
+The gitlab builder works without a chroot and uses the Zephyr toolchain. This
+is intended to ensure that we have a path to upstreaming our code eventually and
+do not rely on Chrome OS-specific tools. It does make use of 'zmake', however.
See the piplines [here](https://gitlab.com/zephyr-ec/ec/-/pipelines).