Skip to content


Subversion checkout URL

You can clone with
Download ZIP


Making BOSH docs more apparent #1

wants to merge 1 commit into from

2 participants


I poured over this repo for a while but couldn't find any actual docs on BOSH itself. Mr. Watters was kind enough to point me at them [1] but I suspect you'll want to make it easier to find them. This README tweak makes their location more apparent.



Dear Cloud Foundry contributor,

If you are reading this message, it means you submitted a pull request in the Cloud Foundry GitHub repository.

First of all, thanks! We really appreciate your participation.

Recently we made some changes in how we are verifying and reviewing open source contributions like yours. In addition, we changed the way we can expose our internal development in real-time. The changes are exciting, as they allow all our staff to collaborate seamlessly with you, which increases our mutual velocity and gives the community a bigger stake in our direction.

The Cloud Foundry team uses Gerrit, a code review tool that originated in the Android Open Source Project. We also use GitHub as an official mirror, though all pull requests are accepted via Gerrit.

Follow these steps to make a contribution to any of our open source repositories:

  1. Complete our CLA Agreement for individuals or corporations.
  2. Sign up for an account on our public Gerrit server at
  3. Create and upload your public SSH key in your Gerrit account profile.
  4. Set your name and email:

            git config --global "Firstname Lastname"
            git config --global ""
  5. Install our gerrit-cli gem:

            gem install gerrit-cli
  6. Clone the Cloud Foundry repo:
    Note: to clone the BOSH repo, or the Documentation repo, replace
    vcap with bosh or oss-docs

            gerrit clone ssh://
            cd vcap
  7. Make your changes, commit, and push to gerrit:

            git commit
            gerrit push

Once your commits are approved by our Continuous Integration Bot (CI Bot) as well as our engineering staff, return to the Gerrit interface and MERGE your changes. The merge will be replicated to GitHub automatically at If you get feedback on your submission, we recommend squashing your commit with the original change-id. See the squashing section here for more details:


Really? I need a CLA in place just to make a 5 line, non-code change to a README?


I took the lazy road and filed an issue for this: #2

I understand VMware needs a CLA, but you'll probably get a lot more people filing issues for small fixes as opposed to actually fixing them with this in place. I'm not sure there's much you can do about it as CLAs tend to be all or nothing, but it's unfortunate.

Anyways, looking forward to watching BOSH grow. Looks like a promising chunk of code.

@olegshaldybin olegshaldybin referenced this pull request from a commit
@olegshaldybin olegshaldybin Fixed release upload regression
Recent package matching optimization required an updated director to
work properly. We tried to make it backward compatible by doing full
matching when talking to the older director but it wasn't enough: the
list of packages fetched from director has no information of which
version a package belongs to, so CLI could delete more packages than
needed trying to repack the tarball. Fixed by making change work exactly
as it was working before: if no package matching can be performed,
exhaustive name/version comparison is performed instead of just sha1

This should make it work with both old and new director as advertised.

Test plan:

- uploaded release to older director;
- uploaded release to new director;
- changed release name and retried #1 and #2.

Change-Id: I457c6c399db6b2cea12e4b4ef9c0d93c65c82013
@takeshi takeshi referenced this pull request from a commit
@joeldsa joeldsa Bumped the version of the login server to 1.1.0

Chloe Jackson (1):
      Style update

Dave Syer (13):
      [cfid-72] Add /autologin endpoint
      [cfid-72] Ensure that caller knows user password as well
      [cfid-9] Add some INFO logging for attempted/failed authentications
      Merge pull request #1 from jacksoncvm/develop
      [cfid-72] Add support for form-encoded requests in /autologin
      Merge branch 'feature/autologin' into develop
      Merge branch 'release/1.0.0' into develop
      [cfid-134] don't expect client details when rendering response
      [cfid-72] Fix compiler error with javac
      Add command line instructions to README
      Add /healthz explicitly to login server
      Update .gitreview
      [cfid-153] Fix tricky bug with cookies for UAA

Joel D'sa (1):
      Removed snapshots and bumped the version to 1.1.0

Change-Id: Idd5b0f0fb145cb9edb92a3f702dfe101c06c9dc4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Apr 11, 2012
  1. tweaking readme to make BOSH-specific visisble.

    Mark Phillips authored
This page is out of date. Refresh to see the latest.
Showing with 7 additions and 1 deletion.
  1. +7 −1
@@ -1,4 +1,10 @@
-# Cloud Foundry OSS Resources #
+BOSH is an open source tool chain for release engineering, deployment and lifecycle management of large scale distributed services. BOSH was originally developed in the context of the Cloud Foundry but the framework is general purpose and can be used to deploy other distributed services on top of Infrastructure-as-a-Service (IaaS) products such as VMware vSphere, Amazon Web Services, or OpenStack.
+Comprehensive documentation for BOSH can be found [here](
+## Cloud Foundry OSS Resources
_Cloud Foundry Open Source Platform as a Service_
Something went wrong with that request. Please try again.