YACS | Sessions

Continuous Integration & Delivery

Featuring...

In Practice...

The Config

# .travis.yml

language: ruby
rvm:
  - 2.2.3
before_script:
  - psql -c 'create database "yacs-test";' -U postgres

In your project...

In your settings...

Travis-CI + Github makes this very easy with pre-build integrations

Travis uses helpful sane defaults, simplifying config

The PR

The Build

The Pass

The Review

Continuous Delivery & Continuous Deployment

'What is these tests? Where are my deploy?'

CD - What and Why?

• Applies the principles from CI to deployment
• Ensures the state of the app is always shippable
  • Requires testing in a production-like environment ('staging')
• Introduces automated deployment
  • Continuous Delivery: Manual deployment to production
  • Continuous Deployment: Automated deployment to production with every update

Continuous Delivery

• Ensures the state of the app is always shippable
  • Requires testing in a production-like environment ('staging')

Pull Request

Automated Testing

Deploy to Staging

Acceptance Testing

Deploy to Production

Auto

Auto

Auto

Manual

• After acceptance testing, deploying to production is manual
  • Is not mandator to deploy every update
• This model is universally applicable

Listen to Your Heart

With a little creativity, we can make a simple Github integration

We're using the same system as Heroku's auto-deploy and Slack's notifications

Github will POST to the provided address whenever a branch is updated

Listen to the Rain

# deploy_server.rb

require 'sinatra'

post '/deploy' do
  if verify_webhook(request: request, secret: 'GET CREATIVE')
    system('sh ../app/deploy.sh')
  end
end

# deploy.sh

puma_ctl stop

git pull

mkdir -p ./tmp/pids/puma

bundle exec rake db:create db:migrate
bundle exec rake assets:precompile
puma_ctl start

1. Check out the branch
2. Run the deploy server
3. Profit!!