... | ... | @@ -123,10 +123,11 @@ For verification purposes you can check the list of ildap group members with a c |
|
|
|
|
|
## How to use the continuous integration (CI) service?
|
|
|
|
|
|
Besides using Inria's Continuous Integration platform [ci.inria.fr](https://ci.inria.fr), you can use gitlab's integrated CI pipelines. This tool is more suited to the execution of simple and lightweight tasks, than for complex deployment pipelines.
|
|
|
Besides using Inria's Continuous Integration platform [ci.inria.fr](https://ci.inria.fr), you can use gitlab's integrated CI pipelines, see the [official documentation](https://docs.gitlab.com/ee/ci/) and the complete [gitlab-ci yaml reference](https://docs.gitlab.com/ee/ci/yaml/).
|
|
|
|
|
|
You will need to set up a CI runner (small tool in charge of running the CI
|
|
|
tasks themselves) and then register the runner with your project.
|
|
|
Concerning the machines setup to run the tests you can either use existing "shared runners" (to be used with docker images), see section _Use existing shared runners_ hereafter, or you will need to install [gitlab-runner](https://docs.gitlab.com/runner/install/) on your specific machine and then register the runner with your project, see section _Installing your own specific runners_.
|
|
|
|
|
|
In addition, if you look for "real life" gitlab-ci examples, please visit this dedicated group [gitlabci_gallery](https://gitlab.inria.fr/gitlabci_gallery). It contains several subgroups and git repositories showing some interesting key features of gitlab-ci and possible integrations with external tools/platforms (ci.inria.fr, terraform, github, a supercomputer, etc).
|
|
|
|
|
|
### Enabling CI on a gitlab project
|
|
|
|
... | ... | @@ -149,7 +150,7 @@ myjob: |
|
|
- whoami
|
|
|
```
|
|
|
|
|
|
### Installing runners
|
|
|
### Installing your own specific runners
|
|
|
|
|
|
To perform the actual build, you need to install GitLab Runner. Runners can run anywhere : you can use a virtual machine on [ci.inria.fr](https://ci.inria.fr) to host your GitLab runner.
|
|
|
|
... | ... | @@ -161,7 +162,7 @@ See : |
|
|
|
|
|
#### Installation example on a GNU/linux slave from ci.inria.fr ("ci" user account)
|
|
|
```
|
|
|
sudo wget -O /usr/local/bin/gitlab-runner https://gitlab-runner-downloads.s3.amazonaws.com/latest/binaries/gitlab-runner-linux-amd64
|
|
|
sudo curl -L --output /usr/local/bin/gitlab-runner "https://gitlab-runner-downloads.s3.amazonaws.com/latest/binaries/gitlab-runner-linux-amd64"
|
|
|
sudo chmod +x /usr/local/bin/gitlab-runner
|
|
|
sudo gitlab-runner install --user=ci --working-directory=/builds
|
|
|
sudo gitlab-runner start
|
... | ... | @@ -206,8 +207,8 @@ In order to answer when asked |
|
|
it is important to know that "gitlab-ci tags" are NOT git tags. The tags you enter here are useful to specify conditional execution in the configuration file .gitlab-ci.yml.
|
|
|
See :
|
|
|
|
|
|
* <https://docs.gitlab.com/ce/ci/yaml/#tags>
|
|
|
* and <https://docs.gitlab.com/ce/ci/yaml/#only-and-except>
|
|
|
* <https://docs.gitlab.com/ee/ci/yaml/#tags>
|
|
|
* and <https://docs.gitlab.com/ee/ci/yaml/#only--except>
|
|
|
|
|
|
for more details.
|
|
|
|
... | ... | |