Git - Getting Started

Getting Setup

See how to configure your SSH keys before you get started.

Creating your first repository

Browse to your Forge management page - https://[ACCOUNT].forge.cloudbees.com/

Click on "Create new code repository" and then fill in the required information. We recommend Git repositories - they tend to fit disconnected and remote development models better than Subversion repositories.

After you have filled in your details; click "Create"

A few moments later your repository will be provisioned - this should only take a few seconds for Git (and around 30s for Subversion) and then page will refresh.

Now that your repository has been created, you can check-out from it and commit / push to it.

Email Notifications

If you wish to be emailed whenever someone in your team makes a change, simply fill in a target email address that will be notified when a change occurs.

For performance reasons there is a limit of 3 addresses that may be emailed for each commit. If you require more than that, it is recommended that you setup a mail forwarder in your mailing system - e.g. dev-team@example.com which forwards to each team member.

Examples

Below the repository details you will find a range of examples which cover checking into your repository or migrating from another repository to your CloudBees repository.

Troubleshooting

If you have difficulty connecting to Git or SVN then there are a few basic steps you can take

Git

Basic Connectivity

If your keys are configured you will be given a message telling you who you are authenticating as.

You might also see this, which also indicates a successful connection:

If your keys aren't configured you will not be able to authenticate.
ssh git@git.cloudbees.com
Permission denied (publickey,gssapi-with-mic).