Issue 6220 - add travis-ci configuration for adblockpluscore

.travis.yml

Index: .travis.yml
diff --git a/.travis.yml b/.travis.yml
new file mode 100644
index 0000000000000000000000000000000000000000..344e86ac9e48c69238f901439823c93d8628ccef
--- /dev/null
+++ b/.travis.yml
@@ -0,0 +1,22 @@
+language: cpp

[sergei, 2018/01/11 21:53:13]

The language is cpp because it will simplify it when we start to compile
emscripten code for native applications.

+
+os:
+- linux
+- osx
+
+dist: trusty
+
+python: '2.7'
+
+install:
+  - nvm install 8.9.4

[sergei, 2018/01/11 21:53:13]

current latest LTS, For the beginning IMO it's enough, however we should
actually test against several versions, e.g. the versions of V8 which are used
in chrome browsers which supported by our extension.

+
+before_script:
+  - ./ensure_dependencies.py
+  - npm install
+
+script:
+  - npm test
+
+notifications:
+  email: false

[tlucas, 2018/01/17 12:41:40]

Do we not want to be notified about failed builds?
Also, FWIW we could add some sugar and notify #adblockplus about succeeded
builds ;)

[sergei, 2018/01/17 14:25:30]

Just would like to precise that it can be configured whether it's for failed
builds or even always.
This looks attractive actually, perhaps we should add it, I modified the issue
description.

IMO we should keep it silent for the beginning until we see that it is working
smoothly and see that we really need such information. I have some experience
with such notifications, usually e-mail notifications become a spam pretty soon,
so I would propose to disable them and drop a message in IRC channel.

In addition we should take into account the actual workflow, unfortunately we
don't push too often to the main repository, and we are more or less aware when
it happens (at least I'm notified in IRC by corresponding keywords) and can
track the CI status, on the other hand the default configuration should not
bother IMO us nor the author of changes. Let's say I am a third party person (or
even I'm who I'm) and want to contribute, in order to do it I fork the repo,
make some changes and before sending it to codereview I run CI for the fork, and
this CI should not send any e-mail to anybody but me (if I really want it) nor
send anything to IRC.