Preface
Quick Start : http://doc.gitlab.com/ce/ci/quick_start/README.html
YAML FILE SYnTAX：http://doc.gitlab.com/ce/ci/yaml/README.html
CI EXAMPLE： http://doc.gitlab.com/ce/ci/examples/README.html
PHP-CI EXAMPLE：http://doc.gitlab.com/ce/ci/examples/php.html
SSH KEYS MAKE SURE SECUTRITY：http://docs.gitlab.com/ce/ci/ssh_keys/README.html
Android GitLab CI
Runner
一、FATAL ERROR
FATAL: Failed to start gitlab-runner: "systemctl" failed: exit status 4, Failed to start gitlab-runner.service: Access denied
ERROR: Deleting runner... error status=only http or https scheme supported
二萝挤、Introduction
在 Gitlab CI 中蚜印，Runners 會運行你的 yaml 文件刽宪。一個 runner唯鸭，相當(dāng)于是一個獨立的（假設(shè)性說法）機(jī)器，它會運行編譯通過源代碼問價的 GitLab CI 接口藏斩。
一個 Runner 著淆，既可以指定到一個項目，也可以用于多個項目潜的。一個用于所有項目的 Runner骚揍，又叫 shared runner。
最好，GitLab Runner 不要與 GitLab 安裝在同一臺機(jī)器上信不。
Gitlab Runner
We strongly advise against installing GitLab Runner on the same machine you plan to install GitLab on. Depending on how you decide to configure GitLab Runner and what tools you use to exercise your application in the CI environment, GitLab Runner can consume significant amount of available memory.
Memory consumption calculations, that are available above, will not be valid if you decide to run GitLab Runner and the GitLab Rails application on the same machine.
It is also not safe to install everything on a single machine, because of the security reasons - especially when you plan to use shell executor with GitLab Runner.
We recommend using a separate machine for each GitLab Runner, if you plan to use the CI features.
