pennyworth is a continuous packaging system built around Opscode's Chef, Jenkins and the fpm packaging tool
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.

NOTE: This project has been abandoned.

pennyworth 0.2.2

Bruce Wayne: Rebuild it. Just the way it was, brick for brick.

Alfred Pennyworth: Just the way it was, sir?

Bruce Wayne: Yeah. Why?

Alfred Pennyworth: I thought this might be a good opportunity for improving the foundations.

Based upon the principles of continuous integration, pennyworth will help you build assets for any software you use and provides a reasonable means to distribute it throughout your nodes. By using a well tested package management system under the hood for deployment, you can easily roll back versions and manage node level conflicts.

Jenkins can be configured to search for feature branches, for advanced workflows. We’ve included some examples for basic branch tracking.

Many example data bags are included that show how to test, build and package a variety of projects, including Ruby and Clojure projects.

Librarian support

  • To test, run:
bundle install
bundle exec librarian-chef install --verbose

vagrant support

  • you can use ‘vagrant up’ to launch a virtualbox instance based on Ubuntu Natty 11.04 amd64 to run pennyworth
bundle exec vagrant up

chef cookbooks



recipe: ssh_keys

  • drops keypairs off for Jenkins, so it can talk to your Git infrastructure later.

recipe: remount_ephemeral

  • on ec2, remount the ephemeral device (with an appropriate filesystem and such) at a convenient location for jenkins

recipe: riak

  • in one of our deployments a pennyworth project required riak, so we shipped it

recipe: default

  • consumes the pennyworth databag items individually, adding them to jenkins and so on.

recipe: update_version

  • ships the update_version script which updates the “package” data bag versions for each job


  • reprepro (formerly known as mirrorer) is a nasty old debian tool that you can use to manage an APT repository
  • could easily slot something like Richard Crowley’s freight project in here


  • upstream opscode cookbook, provides apt repository LWRP which is used to install the repository hosted on the jenkins node


  • upstream opscode cookbook, installs java


  • installs the leiningen build tool for clojure

data bags


  • this allows for an API client to query the chef server for available versions
  • can be updated at end-of-build by Jenkins (examples included)


  • multiple types of jenkins jobs


  • Git based, runs test commands


  • Git based, runs test, build and package commands.
  • Examples included for building packages with fpm
  • Packages built with fpm can be included into a Reprepro package repository on the system

other tools


  • fpm allows us to build debian packages out of basically anything, including cool stuff like ruby gems and python eggs
  • we use it inside of pennyworth jenkins projects to build architecture-specific assets of varying types of projects

knife deploy plugin

  • to be documented