Continous delivery with sbt

CONTINOUS DELIVERY
WITH SBT
JENKINS, DOCKER, GATLING AND MORE
Created by Wojciech Pituła

BENEFITS
Repeatable deploys
History of deploys
No knowledge needed to deploy
Fast rollback to previous version

COMMIT
> ...
> sbt test
> ...
> git push

SBT RELEASE
project/plugins.sbt
addSbtPlugin("com.github.gseitz" % "sbtrelease" % "1.0.0")
shell
> sbt release

RELEASE PROCESS
BUILD.SBT
import sbtrelease.ReleasePlugin.autoImport.ReleaseTransformations._
releaseProcess := Seq[ReleaseStep](
    checkSnapshotDependencies,
    inquireVersions,
    runTest,
    setReleaseVersion,
    commitReleaseVersion,
    tagRelease,
    ReleaseStep(releaseStepTask(publish in Docker)),
    publishArtifacts,
    setNextVersion,
    commitNextVersion,
    pushChanges
)

inquireVersions
ReleaseStep(releaseStepTask(publish in Docker))
publishArtifacts
pushChanges

RELEASE: INQUIRE VERSIONS
VERSION.SBT
version in ThisBuild := "0.1.40SNAPSHOT"
inquireVersions
publishArtifacts
pushChanges

RELEASE: PUBLISH ARTIFACTS
optional
> sbt publish
inquireVersions
publishArtifacts
pushChanges

BUILD.SBT
publishMavenStyle := true
publishArtifact in Test := false
pomIncludeRepository := { _ => false }
publishTo := {
    val nexus = "http://nexus.int.wpsa.pl/"
    if (isSnapshot.value)
        Some("snapshots" at nexus + "content/repositories/snapshots"
    else
        Some("releases" at nexus + "content/repositories/releases")
}

RELEASE: DOCKER
plugins.sbt
addSbtPlugin("com.typesafe.sbt" % "sbtnativepackager" % "1.0.3")
shell
> sbt docker:publish
inquireVersions
publishArtifacts
pushChanges

BUILD.SBT
enablePlugins(JavaAppPackaging)
dockerBaseImage := "java:8"
dockerRepository := Some("hub.docker.grupawp.pl/itrd")

RELEASE: PUSH
Push bumped version and tag to origin
inquireVersions
publishArtifacts
pushChanges

DEPLOY SCRIPT
#!/usr/bin/env bash
set xue
APP_VERSION=$1
HOST=$2
APP_NAME=abtestsservice
DOCKER_IMAGE=hub.docker.grupawp.pl/itrd/abtestsservice:$APP_VERSION
shift 2
RUN_OPTS=$@
ssh t o StrictHostKeyChecking=no jenkinsci@$HOST << EOF
    docker pull $DOCKER_IMAGE
    docker stop $APP_NAME
    docker rm $APP_NAME
    docker run name $APP_NAME d p 8080:8080 $DOCKER_IMAGE $RUN_OPTS
EOF
# verify if docker is running
sleep 30
ssh t o StrictHostKeyChecking=no jenkinsci@$HOST 'RUNNING=`docker inspe

MACHINE SETUP
ANSIBLE PLAYBOOK

hosts: all
  sudo: yes
  tasks:
     name: install dockerengine
      yum: name=dockerengine state=present
     name: create jenkins user
      user: name=jenkinsci groups=docker state=present shell=/bin/bash ho
     name: Set up authorized_keys for the deploy user
      authorized_key: user=jenkinsci
                      key="{{ item }}"
      with_file:
         id_rsa.pub_noweci
         id_rsa.pub

TESTS
Triggered automatically after deploy

GATLING
An open-source load testing framework based on Scala,
Akka and Netty
High performance
Ready-to-present HTML reports
Scenario recorder and developer-friendly DSL

GATLING SCENARIO
Put in src/it/scala
class AddAndDeleteSingleTestSimulation extends Simulation {
                    val httpConf = http.baseURL("some.url")
  val testScenario = scenario("AddAndGetSingleTest")
    .exec(
      http("PostNewTest")
                    .post("some/endpoint")
        .header("ContentType", "application/json")
                    .body(StringBody("{body}"))
        .check(status.is(201))
    )
    .exec(
      http("GetCreatedTest")
                    .get("some/endpoint")
        .check(status.is(200), jsonPath("$.testDef.name").is(testName))
    )
    .exec(
      http("DeleteCreatedTest")

PLUGINS.SBT
addSbtPlugin("io.gatling" % "gatlingsbt" % "2.1.5")
BUILD.SBT
enablePlugins(GatlingPlugin)
configs(IntegrationTest, GatlingIt)
Defaults.itSettings

20150909 12:38:33 +02:00, durationGLOBAL DETAILS
> Global Information
Expand all groups | Collapse a
ASSERTIONS
Assertion
For all requests: count of failed requests is 0
STATISTICS
Executions Response Time (ms)
KO OK
0
1
Number of reques
Number of Requests
t < 800 ms 800 ms < t < 1200
ms
t > 1200 ms failed
0
1
2
3
4
5
Indicators
addanddeletesingletestsim
Active Users
Requests / sec
Responses / sec
SUCCESS

DEPLOY TO PRODUCTION
Exactly the same process like with DEV environment

DRAWBACKS AND PROBLEMS
binaries and config separation
smoke tests
production db password
data migration/schema updates
deployment downtime

Continous delivery with sbt

More Related Content

What's hot (20)

Viewers also liked (20)

Recently uploaded (20)

Continous delivery with sbt