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

https://hub.docker.com/r/livexp/android-sdk/

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，相当于是一个独立的（假设性说法）机器，它会运行编译通过源代码问价的 GitLab CI 接口。

一个 Runner ，既可以指定到一个项目，也可以用于多个项目。一个用于所有项目的 Runner，又叫 shared runner。

最好，GitLab Runner 不要与 GitLab 安装在同一台机器上。

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.