before_script_deploy environment : production variables : HEROKU_API_KEY : $HEROKU_PRODUCTION_KEY script : - dpl -provider=heroku -app=$HEROKU_APP_NAME -api-key=$HEROKU_PRODUCTION_KEY - heroku run rails db:migrate -exit-code -app $HEROKU_APP_NAME only : - master staging : type : deploy extends. AWS Elastic Beanstalk # are supported too: production : type : deploy extends. before_script_deploy : before_script : - curl | sh - gem install dpl # This deploy job uses a simple deploy flow to Heroku, other providers, e.g.

Since we are deploying to Heroku that requires us to run migration manually after each deployment, we should install Heroku CLI before the deploy stage. The deployments will be processed with the help of dpl gem.

from master branch, deploy to production.

The deployments to run only from particular branches, ie., Once the tests are passing, we can configure the deployments in the next stage. We can configure different environments for the project in Operations -> Environments. The protected variables will be exported only in protected branches.

We can mark the variables Protected & Masked depending on our setup. To add these navigate to Variables section in CI / CD Settings of the project. Test : stage : tests before_script : - ruby -v # Print out ruby version for debugging - apt-get update -q & apt-get install nodejs postgresql-client -yqq # Install yarn as outlined in () - curl -o-L | bash # Make available in the current terminal - export PATH='$HOME/.yarn/bin:$HOME/.config/yarn/global/node_modules/.bin:$PATH' - yarn install - gem install bundler - bundle config set path 'vendor' - bundle install -j $(nproc) - bundle exec rake db:migrate -quiet - bundle exec rake db:test:prepare -quiet script : - bundle exec rails test Add Environment variablesīefore we configure the deployment, we need to add the ENV variables to Gitlab’s project configuration.

Heroku rails master key