Changes between Version 10 and Version 11 of Ticket #6651


Ignore:
Timestamp:
05/18/2018 08:00:43 AM (23 months ago)
Author:
tlucas
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #6651 – Description

    v10 v11  
    66 * http://hub.eyeo.com/issues/11192 -> Discussion about storing sensitive data on gitlab.com (outcome: don't) 
    77 * Create a skeleton for a VM, which can be registered as a runner for a project on gitlab.com (case study: https://gitlab.com/triluc/vagrant-puppet-gitlab-setup ) 
    8  * http://hub.eyeo.com/issues/11275 -> requesting custom runners for gitlab.com 
     8 * (Related to the above: http://hub.eyeo.com/issues/11275 -> requesting custom runners for gitlab.com) 
    99 
    1010After implementing the tickets listed below, add a `.gitlab-ci.yml` which should invoke a gitlab-pipeline to `build` and `upload` a devbuild for `adblockpluschrome` for `Firefox` and `Chrome` any time a new commit is pushed to `master`, or for `Edge`, any time a new commit is pushed to `edge` (as soon as we get rid of the `edge`-branch, we can also trigger the job for `Edge` from the master branch as well.). Let these builds be listed in a `development` [https://docs.gitlab.com/ee/ci/yaml/#environment environment] on gitlab.com.