Skip to content
Ruby
Find file
Pull request Compare This branch is even with membase:master.
Latest commit ebca6e6 Apr 27, 2016 @ikandaswamy ikandaswamy Update toy-isha.xml
Change-Id: Iabedbcbb9392d3635615d0d599b1e233bcb44563
Reviewed-on: http://review.couchbase.org/63438
Reviewed-by: Isha Kandaswamy <isha@couchbase.com>
Tested-by: Isha Kandaswamy <isha@couchbase.com>
Failed to load latest commit information.
cbq-gui Add goutils to cbq-gui build Mar 8, 2016
couchbase-server MB-19134: Update the gocb branch for the backup project Apr 27, 2016
released MB-19055: Add 3.1.5 released manifest based on 3.1.5-1859 Apr 20, 2016
tools Add a manifest file for a tools only build Apr 26, 2016
toy Update toy-isha.xml Apr 27, 2016
.gitignore added tmp to .gitignore Mar 30, 2011
README.markdown url to get repo wasn't valid Jul 30, 2015
askeladden.xml CBD-1498: Move forestdb out of couchbaselabs Feb 27, 2015
branch-1.8.1-mb-5845.xml Be more specific when pointing to a tag for 1.8.1 hotfix branch Mar 26, 2013
branch-1.8.1.xml MB-6757: Make sure 1.8.1 build set with fixed release revision Oct 2, 2012
branch-2.0.1.xml CBD-926: Memcached should use the 2.0 branch Apr 4, 2013
branch-2.0.xml updated 2.0.0 manifest file Dec 14, 2012
branch-2.1.0.xml CBD-946: healthchecker now has 2.1.0 branch Jun 14, 2013
branch-builddeps.xml create manifest file for builddeps project Oct 12, 2012
branch-master.xml MB-19134: Update the gocb branch for the backup project Apr 27, 2016
external-override-1.8.1.xml All manifests should use the old-master gperftools branch Nov 27, 2013
external-override-2.0.1.xml All manifests should use the old-master gperftools branch Nov 27, 2013
external-override-2.0.xml All manifests should use the old-master gperftools branch Nov 27, 2013
external-override-2.0b.xml All manifests should use the old-master gperftools branch Nov 27, 2013
external-override-2.0c.xml All manifests should use the old-master gperftools branch Nov 27, 2013
external-override-2.0dp4.xml use OTP_R14B03 for dp4 and OTP_R14B04 for 1.8 and 2.0 Feb 27, 2012
external-override-2.1.0.xml All manifests should use the old-master gperftools branch Nov 27, 2013
external-override-2.1.1.xml All manifests should use the old-master gperftools branch Nov 27, 2013
external-override-2.2.0.xml All manifests should use the old-master gperftools branch Nov 27, 2013
external-override-2.2.1.xml All manifests should use the old-master gperftools branch Nov 27, 2013
external-override-2.5.0.xml fix revisions to RC1 (2.5.0-994) Dec 11, 2013
external-override-2.5.1-MB-11187.xml MB-11187: Add v8 dependencies May 28, 2014
external-override-2.5.1.xml CBD-1246: 2.5.1 manifests are copies of 2.5.0 Feb 12, 2014
external-override-2.5.2.xml MB-12274: Add 2.5.2 override manifests Nov 15, 2014
external-override-3.0.0.xml MB-11216, MB-11145: updating 3.0.0 builds to gperftools 2.2 Jun 2, 2014
external-override-3.0.1.xml CBD-1431: 3.0.1 overrides copies of 3.0.0 overrides Aug 20, 2014
external-override-3.0.2.xml Adding override manifests for 3.0.2 Oct 31, 2014
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 Yet more tweaking of git fetch Oct 11, 2014
masterish.xml CBD-1493: Add a *temporary* manifest that is sort of like Feb 5, 2015
override-1.8.1.xml MB-8102: use commits from released/1.8.1.xml Dec 3, 2013
override-2.0.1.xml All manifests should use the old-master gperftools branch Nov 27, 2013
override-2.0.xml All manifests should use the old-master gperftools branch Nov 27, 2013
override-2.0b.xml All manifests should use the old-master gperftools branch Nov 27, 2013
override-2.0c.xml All manifests should use the old-master gperftools branch Nov 27, 2013
override-2.1.0.xml All manifests should use the old-master gperftools branch Nov 27, 2013
override-2.1.1.xml CBSE-811: 2.1.1 uses override-2.1.1.xml Nov 8, 2013
override-2.2.0.xml RC1: 2.2.0-817 Aug 29, 2013
override-2.2.1.xml All manifests should use the old-master gperftools branch Nov 27, 2013
override-2.5.0.xml fix revisions to RC1 (2.5.0-994) Dec 11, 2013
override-2.5.1-MB-11187.xml MB-11187: Add v8 dependencies May 28, 2014
override-2.5.1.xml CBD-1246: 2.5.1 manifests are copies of 2.5.0 Feb 12, 2014
override-2.5.2.xml MB-12274: Add 2.5.2 override manifests Nov 15, 2014
override-3.0.0.xml Revert "Beta-2 refresh: Re-building build 1055 plus two couchbase-cli… Aug 8, 2014
override-3.0.1.xml CBD-1431: 3.0.1 overrides copies of 3.0.0 overrides Aug 20, 2014
override-3.0.2.xml Adding override manifests for 3.0.2 Oct 31, 2014
override-3.0.x.xml Revert "Resetting 3.0.x world for 3.0.3-MP2 build" Dec 18, 2015
override-master.xml Revert "MB-11406: Revert *master* only to Erlang R14, for performance… Oct 11, 2014
override-sync-gateway.xml CBLT-39: Build package for sync gateway Sep 7, 2013
patch-manifest.rb Automatically generate manifest files based on gerrit-refspec Jan 10, 2012
rel-1.8.1.xml MB-8102: use commits from released/1.8.1.xml Dec 3, 2013
rel-2.1.1.xml CBDE-881: merge couchdb changes to 2.1.0 branch for 2.1.1 patch Nov 8, 2013
rel-2.2.0.xml MB-11037: ep-engine uses branch "MB-11037", everything else at 2.2.0-837 May 8, 2014
rel-2.2.1.xml MB-9169: neither master nor 3.0.0 have needed changes from 2.2 branch Sep 24, 2013
rel-2.5.0.xml MB-10227 branch for ns_server, else same as released/2.5.0.xml Feb 28, 2014
rel-2.5.1.xml MB-12451 Verification build to test MCD memory leak Nov 4, 2014
rel-2.5.2.xml MB-12274: Also point couchdbx-app to "2.5.1.1" branch Nov 18, 2014
rel-3.0.0.xml MB-12185: Reference memcached from "couchbase" github remote Dec 2, 2014
rel-3.0.1.xml MB-12185: Reference memcached from "couchbase" github remote Dec 2, 2014
rel-3.0.2.xml Temporarily reset rel-3.0.2.xml to 3.0.2-1636 for a rebuild. Mar 5, 2015
rel-3.0.x.xml MB-19055: Reset rel-3.0.x.xml for 3.1.5 release Apr 5, 2016
sherlock.xml Move all projects away from 'master' for mainline Sherlock Mar 1, 2016
sync-gateway-1.0.0.xml CBLT-41: build out of stable branch Sep 11, 2013
watson.xml MB-19134: Update the gocb branch for the backup project Apr 27, 2016

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, and is outside the scope of the "repo" tool, it is included in released/ manifests as a comment.

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, we build using one of the manifests in the top-level directory. Prior to 2.2.0 the files were called "branch-branch-name.xml", and starting with 2.2.0 we used files called "rel-release-name.xml"

This was to signify a change in process, in which stopped making release-specific branches (named for the release), unless a such branch was needed (and is no longer named for the release). Thus we had:

      branch-1.8.1.xml
      branch-2.0.1.xml
      branch-2.0.xml
      branch-2.1.0.xml

And going forward we have:

      rel-2.1.1.xml
      rel-2.2.0.xml
      rel-2.2.1.xml
      rel-3.0.0.xml

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.

Building With Repo

See the readme in the correct branch for tlm for the exact steps on how to build the desired version.

Get Repo

(if you didn't install from homebrew, or aren't running on Mac OS X)

Get the latest version from the google project page.

Clone the Manifest

For <branch_name> below, you probably want to one of the latest branches in released when getting started. As of this writing, that is released/2.2.0.xml unless you are working on a maintenance or experimental branch.

$ mkdir couchbase
$ cd couchbase
$ repo init -u git://github.com/couchbase/manifest.git -m <branch_name>
$ repo sync

Build

$ make
Something went wrong with that request. Please try again.