Deployment tools.

Tests -> Publish -> Expensive Tests -> Bless

Loosely couples build and deploy steps.

Intended for pull, rather than push, model.

Written in Ruby, compiles as a Ruby Gem.

Produces .deb packages, so currently only useful for deploying to Debian/Ubuntu-like systems.

We have a bunch of different services. All of them need to be tested separately, then tested together, then put into production. Along the way, many different testing or QA environments might need to run them. Ploy provides facilities for making that easy.

$ ploy help [command]
$ ploy publish [.ploy-publish.yml]
$ ploy oracle /path/to/metadata.d
$ ploy client -f conf.yml -d DEPLOYMENT1 -d DEPLOYMENT2
$ ploy install -b BUCKET -d DEPLOYMENT [-B BRANCH] [-v VERSION]
$ ploy bless -b BUCKET -d DEPLOYMENT -B BRANCH -v VERSION
$ ploy bless -b BUCKET -f INFO_FILE

The 'help' command actually works, so you should definitely use that.

---
bucket: bucketname
deploy_name: some-project
dist_dirs:
  - dir: dist
    prefix: /usr/local/someproject
prep_cmd: lineman build
upstart_files:
 - conf/some-project-initfile
postinst: |
  # This script will be in /var/lib/dpkg/info/${PACKAGE_NAME}.postinst
  # once the package is installed. Ploy adds #!/bin/bash to the top
  # automatically.

---
name: some-project
sha: 67e4c66509f6ab1672f0b02f527a23c39a7937bc
github_url: http://github.com/org/some-project
git_url: git@github.com:org/some-project
last_committer: Bob Bobson <bob@example.com>

---
locked: false
bucket: bucketname
packages:
  some-package:
    branch: master
    version: current
  another-package:
    branch: fix-branch
    version: current

1. A user pushes code to github
2. A CI server (e.g. Travis) runs tests
3. If the tests pass, the CI server calls "ploy publish" to publish the build
4. Some test environment is polling for new builds with "ploy install", and advertising available versions with "ploy oracle"
5. A smoke test server is watching for changes in the report from "ploy oracle"
6. When changes happen, it runs more tests
7. If the tests pass, it calls "ploy bless"
8. Production selects only from blessed builds

Improvements welcome. Error handling is minimal. Tests are thin in spots. Not much code documentation (yet).

env RUBYLIB=./lib bundle exec bin/ploy help

$ rspec spec

$ gem build ploy.gemspec

• ruby 1.9+
• fpm
• rsync
• dpkg (for tests)

Known to work on OSX and Ubuntu.

Ploy was created by Manta Media Inc, a web company in Columbus, Ohio. It is distributed under the MIT license.