BigW Consortium Gitlab

test-and-deploy-ruby-application-to-heroku.md 2.54 KB
Newer Older
1 2
# Test and Deploy a ruby application with GitLab CI/CD

3
This example will guide you how to run tests in your Ruby on Rails application and deploy it automatically as Heroku application.
4

5
You can checkout the example [source](https://gitlab.com/ayufan/ruby-getting-started) and check [CI status](https://gitlab.com/ayufan/ruby-getting-started/builds?scope=all).
6

7 8
## Configure the project

9
This is what the `.gitlab-ci.yml` file looks like for this project:
10

11 12
```yaml
test:
13
  stage: test
14 15 16 17 18 19 20 21
  script:
  - apt-get update -qy
  - apt-get install -y nodejs
  - bundle install --path /cache
  - bundle exec rake db:create RAILS_ENV=test
  - bundle exec rake test

staging:
22
  stage: deploy
23 24 25 26 27 28 29
  script:
  - gem install dpl
  - dpl --provider=heroku --app=gitlab-ci-ruby-test-staging --api-key=$HEROKU_STAGING_API_KEY
  only:
  - master

production:
30
  stage: deploy
31 32 33 34 35 36 37 38
  script:
  - gem install dpl
  - dpl --provider=heroku --app=gitlab-ci-ruby-test-prod --api-key=$HEROKU_PRODUCTION_API_KEY
  only:
  - tags
```

This project has three jobs:
39
1. `test` - used to test Rails application,
40
2. `staging` - used to automatically deploy staging environment every push to `master` branch
41
3. `production` - used to automatically deploy production environment for every created tag
42

43 44 45 46
## Store API keys

You'll need to create two variables in your project's **Settings > CI/CD > Variables**:

47 48 49 50 51
1. `HEROKU_STAGING_API_KEY` - Heroku API key used to deploy staging app,
2. `HEROKU_PRODUCTION_API_KEY` - Heroku API key used to deploy production app.

Find your Heroku API key in [Manage Account](https://dashboard.heroku.com/account).

52 53
## Create Heroku application

54 55 56
For each of your environments, you'll need to create a new Heroku application.
You can do this through the [Dashboard](https://dashboard.heroku.com/).

57 58
## Create Runner

59 60
First install [Docker Engine](https://docs.docker.com/installation/).
To build this project you also need to have [GitLab Runner](https://about.gitlab.com/gitlab-ci/#gitlab-runner).
61
You can use public runners available on `gitlab.com`, but you can register your own:
62

63
```
64
gitlab-runner register \
65
  --non-interactive \
66
  --url "https://gitlab.com/" \
67
  --registration-token "PROJECT_REGISTRATION_TOKEN" \
68
  --description "ruby-2.2" \
69
  --executor "docker" \
70
  --docker-image ruby:2.2 \
71 72 73
  --docker-postgres latest
```

74
With the command above, you create a Runner that uses [ruby:2.2](https://hub.docker.com/r/_/ruby/) image and uses [postgres](https://hub.docker.com/r/_/postgres/) database.
75

76
To access PostgreSQL database you need to connect to `host: postgres` as user `postgres` without password.