2019-06-11 12:39:26 -04:00
---
type: tutorial
---
2019-03-07 22:34:28 -05:00
# Test and deploy a Ruby application with GitLab CI/CD
2017-11-01 11:56:40 -04:00
2019-06-11 12:39:26 -04:00
This example will guide you through how to run tests in your Ruby on Rails application and deploy it automatically as a Heroku application.
2015-08-25 21:42:46 -04:00
2019-06-11 12:39:26 -04:00
You can also view or fork the complete [example source ](https://gitlab.com/ayufan/ruby-getting-started ) and view the logs of its past [CI jobs ](https://gitlab.com/ayufan/ruby-getting-started/-/jobs?scope=finished ).
2015-08-25 21:42:46 -04:00
2017-11-01 11:56:40 -04:00
## Configure the project
2015-08-25 21:42:46 -04:00
This is what the `.gitlab-ci.yml` file looks like for this project:
2017-11-01 11:56:40 -04:00
2015-08-25 21:42:46 -04:00
```yaml
test:
2018-01-16 12:21:45 -05:00
stage: test
2015-08-25 21:42:46 -04:00
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:
2018-01-16 12:21:45 -05:00
stage: deploy
2015-08-25 21:42:46 -04:00
script:
- gem install dpl
- dpl --provider=heroku --app=gitlab-ci-ruby-test-staging --api-key=$HEROKU_STAGING_API_KEY
only:
- master
production:
2018-01-16 12:21:45 -05:00
stage: deploy
2015-08-25 21:42:46 -04:00
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:
2018-11-12 19:39:21 -05:00
- `test` - used to test Rails application.
- `staging` - used to automatically deploy staging environment every push to `master` branch.
- `production` - used to automatically deploy production environment for every created tag.
2015-08-25 21:42:46 -04:00
2017-11-01 11:56:40 -04:00
## Store API keys
2019-01-30 05:20:50 -05:00
You'll need to create two variables in your project's **Settings > CI/CD > Environment variables** :
2017-11-01 11:56:40 -04:00
2018-11-12 19:39:21 -05:00
- `HEROKU_STAGING_API_KEY` - Heroku API key used to deploy staging app.
- `HEROKU_PRODUCTION_API_KEY` - Heroku API key used to deploy production app.
2015-08-25 21:42:46 -04:00
Find your Heroku API key in [Manage Account ](https://dashboard.heroku.com/account ).
2017-11-01 11:56:40 -04:00
## Create Heroku application
2015-08-25 21:42:46 -04:00
For each of your environments, you'll need to create a new Heroku application.
2019-06-11 12:39:26 -04:00
You can do this through the [Heroku Dashboard ](https://dashboard.heroku.com/ ).
2015-08-25 21:42:46 -04:00
2017-11-01 11:56:40 -04:00
## Create Runner
2015-08-25 21:42:46 -04:00
First install [Docker Engine ](https://docs.docker.com/installation/ ).
2019-06-11 12:39:26 -04:00
2019-03-07 22:34:28 -05:00
To build this project you also need to have [GitLab Runner ](https://docs.gitlab.com/runner/ ).
2019-06-11 12:39:26 -04:00
You can use public runners available on `gitlab.com` or register your own:
2017-11-01 11:56:40 -04:00
2019-03-07 22:34:28 -05:00
```sh
2017-11-01 11:56:40 -04:00
gitlab-runner register \
2015-08-25 21:42:46 -04:00
--non-interactive \
2017-04-06 18:25:45 -04:00
--url "https://gitlab.com/" \
2015-08-25 21:42:46 -04:00
--registration-token "PROJECT_REGISTRATION_TOKEN" \
2016-01-21 10:12:49 -05:00
--description "ruby-2.2" \
2015-08-25 21:42:46 -04:00
--executor "docker" \
2016-01-21 10:12:49 -05:00
--docker-image ruby:2.2 \
2015-08-25 21:42:46 -04:00
--docker-postgres latest
```
2019-10-10 23:07:00 -04:00
With the command above, you create a Runner that uses the [ruby:2.2 ](https://hub.docker.com/_/ruby ) image and uses a [postgres ](https://hub.docker.com/_/postgres ) database.
2015-08-25 21:42:46 -04:00
2019-06-11 12:39:26 -04:00
To access the PostgreSQL database, connect to `host: postgres` as user `postgres` with no password.