Changes between Initial Version and Version 8 of Ticket #6651


Ignore:
Timestamp:
05/11/2018 10:23:53 AM (2 years ago)
Author:
tlucas
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #6651

    • Property Blocked By changed from to 6339, 6369
  • Ticket #6651 – Description

    initial v8  
    33 
    44=== What to do === 
    5  * Choose a CI solution - My current favorite is [https://about.gitlab.com/features/gitlab-ci-cd/ GitLab CI], for it's scaling-method is the most simple for our ops to use (we can simply spawn VMs and register them as workers, everything would remain under our control (especially with our attempt to have gitlab selfhosted); FWIW while abp-builds-1 would lose it's role of being the only instance controlling what is build when, it could still be used as our main worker. However [https://travis-ci.com/ Travis CI] and [https://circleci.com/product/ CircleCI] also seem feasible (all tools should remain free for Adblock Plus only) 
     5 * Choose a CI solution - My current favorite is [https://about.gitlab.com/features/gitlab-ci-cd/ GitLab CI], for it's scaling-method is the most simple for our ops to use (we can simply spawn VMs and register them as workers, everything would remain under our control ~~(especially with our attempt to have gitlab selfhosted)~~ (<- this was [http://hub.eyeo.com/issues/6210#note-13 canceled]); FWIW while abp-builds-1 would lose it's role of being the only instance controlling what is build when, it could still be used as our main worker. However [https://travis-ci.com/ Travis CI] and [https://circleci.com/product/ CircleCI] also seem feasible (all tools should remain free for Adblock Plus only) 
    66 
    77 * Let the `buildtools` be able to render an appropriate configuration file for the chosen tool (In order to keep flexibility, e.g. choosing which platform's extension should be build from which branch)