How to make your own toy build

One time setup...

Follow the manifest's README instructions to make sure you can successfully build couchbase. If your code doesn't build on your own dev box, it won't build on our buildslaves.

Copy the branch-2.0.xml manifest to toy/toy-YOURNAME.xml. For example...

cd manifest && cp branch-2.0.xml toy/toy-steve.xml

Note, the toy build system looks for manifests that follow the naming pattern of "toy/toy-*.xml".

Modify your toy/toy-YOURNAME.xml to point to the work-in-progress branches where your changes live...

These git repositories (a.k.a, "remotes") need to be publically accessible.

For example, I might have my own personal github account and my own fork/branch of ep-engine, like at git://github.com/steveyen/ep-engine.git, "paxos-experimental" branch.

In my toy/toy-steve.xml file, I would then add a new <remote name="steve" fetch="git://github.com/steveyen"/> and change the ep-engine project to use that new, steveyen remote and paxos-experimental revision (<project name="ep-engine" path="ep-engine" remote="steve" revision="paxos-experimental"/>).