gitlab-org--gitlab-foss/doc/development/ci_setup.md

# CI setup

This document describes what services we use for testing GitLab and GitLab CI.

We currently use three CI services to test GitLab:

1. GitLab CI on [GitHost.io](https://gitlab-ce.githost.io/projects/4/) for the [GitLab.com repo](https://gitlab.com/gitlab-org/gitlab-ce)
2. GitLab CI at ci.gitlab.org to test the private GitLab B.V. repo at dev.gitlab.org
3. [Semephore](https://semaphoreapp.com/gitlabhq/gitlabhq/) for [GitHub.com repo](https://github.com/gitlabhq/gitlabhq)

| Software @ configuration being tested | GitLab CI (ci.gitlab.org) | GitLab CI (GitHost.io) | Semaphore |
|---------------------------------------|---------------------------|---------------------------------------------------------------------------|-----------|
| GitLab CE @ MySQL                     | ✓                         | ✓ [Core team can trigger builds](https://gitlab-ce.githost.io/projects/4) |           |
| GitLab CE @ PostgreSQL                |                           |                                                                           | ✓ [Core team can trigger builds](https://semaphoreapp.com/gitlabhq/gitlabhq/branches/master) |
| GitLab EE @ MySQL                     | ✓                         |                                                                           |           |
| GitLab CI @ MySQL                     | ✓                         |                                                                           |           |
| GitLab CI @ PostgreSQL                |                           |                                                                           | ✓         |
| GitLab CI Runner                      | ✓                         |                                                                           | ✓         |
| GitLab Shell                          | ✓                         |                                                                           | ✓         |
| GitLab Shell                          | ✓                         |                                                                           | ✓         |

Core team has access to trigger builds if needed for GitLab CE.

We use [these build scripts](https://gitlab.com/gitlab-org/gitlab-ci/blob/master/doc/examples/build_script_gitlab_ce.md) for testing with GitLab CI.

# Build configuration on [Semaphore](https://semaphoreapp.com/gitlabhq/gitlabhq/) for testing the [GitHub.com repo](https://github.com/gitlabhq/gitlabhq)

Language: Ruby
Ruby verion: 2.1.2
database.yml: pg

Build commands

```bash
sudo apt-get install cmake libicu-dev -y (Setup)
bundle install --deployment --path vendor/bundle (Setup)
cp config/gitlab.yml.example config/gitlab.yml (Setup)
bundle exec rake db:create (Setup)
bundle exec rake spinach (Thread #1)
bundle exec rake spec (Thread #2)
```

Use rubygems mirror.
CI setup docs Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> 2014-09-18 09:45:18 -04:00			`# CI setup`

Add semaphore config to ci testing doc. 2014-09-19 07:23:53 -04:00			`This document describes what services we use for testing GitLab and GitLab CI.`
CI setup docs Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> 2014-09-18 09:45:18 -04:00
Add semaphore config to ci testing doc. 2014-09-19 07:23:53 -04:00			`We currently use three CI services to test GitLab:`
CI setup docs Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> 2014-09-18 09:45:18 -04:00
Point to correct project on githost.io. 2014-10-15 13:25:47 -04:00			`1. GitLab CI on [GitHost.io](https://gitlab-ce.githost.io/projects/4/) for the [GitLab.com repo](https://gitlab.com/gitlab-org/gitlab-ce)`
Add semaphore config to ci testing doc. 2014-09-19 07:23:53 -04:00			`2. GitLab CI at ci.gitlab.org to test the private GitLab B.V. repo at dev.gitlab.org`
			`3. [Semephore](https://semaphoreapp.com/gitlabhq/gitlabhq/) for [GitHub.com repo](https://github.com/gitlabhq/gitlabhq)`
CI setup docs Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> 2014-09-18 09:45:18 -04:00
Add semaphore config to ci testing doc. 2014-09-19 07:23:53 -04:00			`\| Software @ configuration being tested \| GitLab CI (ci.gitlab.org) \| GitLab CI (GitHost.io) \| Semaphore \|`
Describe who can trigger builds and where, add no red tests policy to contributing doc. 2014-10-15 06:48:37 -04:00			`\|---------------------------------------\|---------------------------\|---------------------------------------------------------------------------\|-----------\|`
			`\| GitLab CE @ MySQL \| ✓ \| ✓ [Core team can trigger builds](https://gitlab-ce.githost.io/projects/4) \| \|`
			`\| GitLab CE @ PostgreSQL \| \| \| ✓ [Core team can trigger builds](https://semaphoreapp.com/gitlabhq/gitlabhq/branches/master) \|`
			`\| GitLab EE @ MySQL \| ✓ \| \| \|`
			`\| GitLab CI @ MySQL \| ✓ \| \| \|`
			`\| GitLab CI @ PostgreSQL \| \| \| ✓ \|`
			`\| GitLab CI Runner \| ✓ \| \| ✓ \|`
			`\| GitLab Shell \| ✓ \| \| ✓ \|`
			`\| GitLab Shell \| ✓ \| \| ✓ \|`

			`Core team has access to trigger builds if needed for GitLab CE.`
Add semaphore config to ci testing doc. 2014-09-19 07:23:53 -04:00
			`We use [these build scripts](https://gitlab.com/gitlab-org/gitlab-ci/blob/master/doc/examples/build_script_gitlab_ce.md) for testing with GitLab CI.`

			`# Build configuration on [Semaphore](https://semaphoreapp.com/gitlabhq/gitlabhq/) for testing the [GitHub.com repo](https://github.com/gitlabhq/gitlabhq)`

			`Language: Ruby`
			`Ruby verion: 2.1.2`
			`database.yml: pg`

			`Build commands`

			```bash
			`sudo apt-get install cmake libicu-dev -y (Setup)`
			`bundle install --deployment --path vendor/bundle (Setup)`
			`cp config/gitlab.yml.example config/gitlab.yml (Setup)`
			`bundle exec rake db:create (Setup)`
			`bundle exec rake spinach (Thread #1)`
			`bundle exec rake spec (Thread #2)`
			```

			`Use rubygems mirror.`