Opened 2 years ago

Last modified 7 months ago

#6220 closed change

add CI for adblockpluscore — at Initial Version

Reported by: sergz Assignee:
Priority: Unknown Milestone:
Module: Core Keywords: closed-in-favor-of-gitlab
Cc: kzar, hfiguiere, tlucas, mjethani, erikvold Blocked By:
Blocking: Platform: Unknown / Cross platform
Ready: no Confidential: no
Tester: Unknown Verified working: no
Review URL(s):

https://codereview.adblockplus.org/29663680/
https://codereview.adblockplus.org/29663688/
https://codereview.adblockplus.org/29714583/
https://codereview.adblockplus.org/29716557/
https://gitlab.com/eyeo/adblockplus/adblockpluscore/merge_requests/1
https://codereview.adblockplus.org/29875559/

Description

Background

It will help a lot if we have CI for the core, mainly because we want to be sure that not only JS part but also the code which is used in native applications on different platforms (e.g. in libadblockplus-andoid) is at least compilable.

I propose to have a configuration for travis-ci (host-platforms: {linux, osx}, target-platfoms: {linux, osx, android}), for appveyor (windows) and optionally for circle-ci because we have a mirror on github which is easily integrable with the services, these services seem the most popular ones and everyone, who is willing to contribute, can easily and for free use them before sending a codereview/pull request.

What to change

  • create corresponding configurations for master branch (JS tests only)
  • based on the config for master branch create a config for emscripten. Details will come later because it can require additional investigations regarding preparation of emscripten and meson.

Additional notes

This approach is already in a working form #5133 for libadblockplus.

Change History (0)

Note: See TracTickets for help on using tickets.