Issue 6651,6220 - add gitlab-ci config

.gitlab-ci.yml

Index: .gitlab-ci.yml
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
new file mode 100644
index 0000000000000000000000000000000000000000..734c9d83d6fd8cf4be78583d9cb68e81fe639db4
--- /dev/null
+++ b/.gitlab-ci.yml
@@ -0,0 +1,26 @@
+# This file is part of Adblock Plus <https://adblockplus.org/>,
+# Copyright (C) 2006-present eyeo GmbH
+#
+# Adblock Plus is free software: you can redistribute it and/or modify
+# it under the terms of the GNU General Public License version 3 as
+# published by the Free Software Foundation.
+#
+# Adblock Plus is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with Adblock Plus.  If not, see <http://www.gnu.org/licenses/>.
+
+---
+
+tests:
+  tags:

[tlucas, 2018/09/05 12:45:35]

You said the tag will likely be adjusted - keep in mind, that changing a tag
here will end up in the necessity to re-provision the runners. I suggest to
settle on a tag now, before the runners are provisioned (also keep in mind, the
provisioning of the runners is now semi-blocked until we are sure which tags you
will use (or none))

[sergei, 2018/09/05 12:49:47]

I would ask dev-ops team to make the decision regarding tags, I can only
contribute my opinion there. As soon as the decision is made it will be
reflected firstly on gitlab in order to check that the everything works and then
in this codereview to let other to review it. So firstly runners then CI config,
in this case there will be no need to re-provision runners.

[tlucas, 2018/09/06 07:14:13]

I suggest to not bother dev-ops about this decision, FWIW i expect them to be
indifferent about the tags ;)

And since i'll likely be asked what you ask them about this, i might as well
just answer directly: let's stick to nodejs for this, since it's nodejs running
here.

[Sebastian Noack, 2018/09/06 19:36:27]

As far as I understand, tags serve to match jobs with runners. So if we'd have a
cluster of runners, this would tell the CI to only run this job on a runner that
is tagged "nodejs". However, we only have one runner at the moment, and once we
add more runners, we don't know yet, how we will tag those. So (unless I
misunderstood something), I wouldn't configure any tags for now (which would
also be consistent with the configuration we have for adblockpluschrome).

+    - nodejs
+  before_script:
+    - mkdir -p .git/info
+    - ./ensure_dependencies.py
+    - npm install
+  script:
+    - npm test