Internals

The system receives a commit hook, which is published to a message queue. The payload is as follows:

{ 
  "owner"   : "thekid",
  "repo"    : "xp-experiments", 
  "tag"     : "r5.9.0RC3",
  "version" : "5.9.0RC3",
  "user"    : "thekid" 
}

A subscriber listens to this message queue, downloads the ChangeLog and a zipfile, and creates the release build, copying the generated files into a specified target directory. Once that is done, a message is posted in the build queue with the following payload:

{ 
  "vendor"   : "xp-framework",
  "module"   : "xp-framework", 
  "release"  : { 
    "version"  : { "number" : "5.9.0RC4" , "series" : "5.9" }, 
    "revision" : "r5.9.0RC4", 
    "date"     : "2013-03-19T14:55:42+01:00",
    "notes"    : "\nHeads up!\n~~~~~~~~~\n- Removed ...",
  },
  "build"    : {
    "base"     : "core",
    "naming"   : { "main" : "xp-rt-{VERSION}" , "test" : "xp-test-{VERSION}" },
    "finalize" : "XpRelease"
  }
  "checkout" : "/tmp/checkout/xp-framework/xp-framework/r5.9.0RC4/" 
}

Note: This can be pushed to a fanout, for example, and can then be distributed to many build systems. All you need to change is the build queue's name.