Issue 6890 - run npm tests in parallel (PENDING)

.gitlab-ci.yml

Index: .gitlab-ci.yml
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 4109a810e68940c367cffb763069bc325ebf23d2..a6519f23d84275fcda78a870815e841d58b83508 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -14,12 +14,46 @@
 # along with Adblock Plus.  If not, see <http://www.gnu.org/licenses/>.
 
 stages:
-  - test_ext
+  - prepare
+  - test
 
-qunit:gecko:
-  stage: test_ext
+prepare-dependencies:
+  stage: prepare
   script:
     - mkdir -p .git/info
     - pip install --user Jinja2 cryptography
+    - python ensure_dependencies.py
     - npm install
-    - npm test
+  cache:
+    key: cache_$CI_COMMIT_SHA

[wspee, 2018/08/29 08:39:47]

IDEA: Have you thought about using a hash of the dependencies as a cache key
instead of the commit hash i.e. hash dependencies, add python dependencies to
the repository via a `dependencies.txt` or similar (like you had in previous
versions) and whatever else needs to be considered?

[tlucas, 2018/09/03 09:54:45]

I guess this would work - but IMHO not feasible right now

[Sebastian Noack, 2018/09/03 19:37:35]

I kinda like that idea, but I'm not too familiar with the capabilities of GitLab
CI configuration. However, if we could simply run a command here to derive the
cache key, this seems to be as simple as:

  cat dependencies package.json | sha1sum | awk '{ print $1 }'

[tlucas, 2018/09/03 21:35:53]

Turns out - unfortunately - that we can't use commands for the key, only
variables (gitlab specific or predefined from the project settings, but also
none exported from within the job)

+    paths:
+      - ./
+    policy: push
+
+
+.test_template: &test_template
+  stage: test
+  before_script:
+    - python ensure_dependencies.py
+    - npm install
+  cache:
+    key: cache_$CI_COMMIT_SHA
+    paths:
+      - ./
+    policy: pull
+
+
+tests:gecko:
+  <<: *test_template
+  script:
+    - npm test -- -g gecko
+
+tests:chrome:
+  <<: *test_template
+  script:
+    - xvfb-run npm test -- -g chrome
+
+tests:global:

[Sebastian Noack, 2018/08/29 21:03:11]

This isn't quite "testing" we are doing here, "lint" seems to be a a better name
for this job.

[tlucas, 2018/09/03 09:54:45]

Done.

+  <<: *test_template
+  script:
+    - npm run lint