Ruby Shell
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
analytics
cbq-gui
cbq
couchbase-lite-android CBD-2159 update release to 2.0.0 and start_build at the next version … Nov 8, 2017
couchbase-lite-core
couchbase-lite-ios
couchbase-lite-net
couchbase-server
moxi
released
tools
toy
.gitignore
README.markdown
branch-1.8.1-mb-5845.xml
branch-1.8.1.xml
branch-2.0.1.xml
branch-2.0.xml
branch-2.1.0.xml
branch-builddeps.xml
branch-master.xml
external-override-1.8.1.xml
external-override-2.0.1.xml All manifests should use the old-master gperftools branch Nov 27, 2013
external-override-2.0.xml
external-override-2.0b.xml
external-override-2.0c.xml
external-override-2.0dp4.xml
external-override-2.1.0.xml
external-override-2.1.1.xml
external-override-2.2.0.xml
external-override-2.2.1.xml
external-override-2.5.0.xml
external-override-2.5.1-MB-11187.xml
external-override-2.5.1.xml
external-override-2.5.2.xml
external-override-3.0.0.xml
external-override-3.0.1.xml
external-override-3.0.2.xml
external-override-3.0.x.xml Revert "Resetting 3.0.x world for 3.0.3-MP2 build" Dec 18, 2015
external-override-builddeps.xml create manifest file for builddeps project Oct 12, 2012
external-override-master.xml Revert "MB-11406: Revert *master* only to Erlang R14, for performance… Oct 11, 2014
fetch-manifest.rb
masterish.xml
override-1.8.1.xml
override-2.0.1.xml
override-2.0.xml
override-2.0b.xml
override-2.0c.xml
override-2.1.0.xml
override-2.1.1.xml
override-2.2.0.xml
override-2.2.1.xml
override-2.5.0.xml
override-2.5.1-MB-11187.xml
override-2.5.1.xml
override-2.5.2.xml
override-3.0.0.xml
override-3.0.1.xml
override-3.0.2.xml
override-3.0.x.xml
override-master.xml
override-sync-gateway.xml
patch-manifest.rb
rel-1.8.1.xml
rel-2.1.1.xml
rel-2.2.0.xml
rel-2.2.1.xml
rel-2.5.0.xml
rel-2.5.1.xml MB-12451 Verification build to test MCD memory leak Nov 4, 2014
rel-2.5.2.xml
rel-3.0.0.xml
rel-3.0.1.xml
rel-3.0.2.xml
rel-3.0.x.xml
sherlock.xml
sync-gateway-1.0.0.xml CBLT-41: build out of stable branch Sep 11, 2013
watson.xml

README.markdown

Which Manifest Do I Use?

Released Versions of Couchbase Server

When we make a release, we take the manifest emitted from the builder and store it in the released/ directory. This manifest only has exact commit SHAs, so that it explicitly describes which revision was used, in both Couchbase and external repositories.

It also gives the revision of the "voltron" repo used in the build. Voltron contains build instructions --- like RPM spec files -- that are used at the top level before the manifest is used to fetch files from the source repos. Because the voltron repo is private, it is marked with the "notdefault" group so "repo" will not attempt to download it unless the command "repo init -g all" is specified.

To replicate a released build use a manifest from the released/ directory.

Versions of Couchbase Server Prior to Release

If you want to build the development branch you should use "branch-master.xml".

While preparing for a product release, based on the version of Couchbase server being handled, the manifest to use for the build can be in one of several locations:

  • For spock and later versions, in the couchbase-server/ subdirectory
  • For watson and previous versions, in the top-level directory
    • This includes the branch-master manifest
  • For branch manifests, in the couchbase-server// subdirectories
    • The exceptions to this are sherlock 4.0.0 and 4.1.0

You will not need to use any of these manifests unless you are contributing changes towards a Couchbase release.

Couchbase Experimental Builds

The toy/ directory is used by Couchbase developers for experimental builds, and so are probably not of interest to anyone not familiar with the context of the experiment.