ITK/Git/Account: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
No edit summary |
mNo edit summary |
||
| Line 13: | Line 13: | ||
# Add your ssh public key at http://review.source.kitware.com/#settings,ssh-keys | # Add your ssh public key at http://review.source.kitware.com/#settings,ssh-keys | ||
==Firewall blocks SSH traffic== | ===Firewall blocks SSH traffic=== | ||
If you are stuck behind a firewall that blocks SSH traffic (port 22), the following alternative URL may be used to push patches over HTTP (port 80): | If you are stuck behind a firewall that blocks SSH traffic (port 22), the following alternative URL may be used to push patches over HTTP (port 80): | ||
Revision as of 20:42, 25 March 2013
This page documents how to setup ITK developer accounts. See our table of contents for more information.
Gerrit
Anyone may request access to the ITK Gerrit Code Review site to propose and review changes. Follow these steps to set up access:
- Get an OpenID
- Register at http://review.source.kitware.com using your OpenID (link in upper right)
- Sign in
- Set all fields in your profile at http://review.source.kitware.com/#settings
- Add your ssh public key at http://review.source.kitware.com/#settings,ssh-keys
Firewall blocks SSH traffic
If you are stuck behind a firewall that blocks SSH traffic (port 22), the following alternative URL may be used to push patches over HTTP (port 80):
- For Gerrit user bob:
$ git config --global url.http://bob@review.source.kitware.com/p/ITK.insteadOf bob@review.source.kitware.com:ITK - Generate a password at http://review.source.kitware.com/#/settings/http-password
- A password prompt will be presented when pushing patches to Gerrit.
This requires Git 1.6.6 or newer.
Git
Authorized developers may publish work directly to itk.org repositories.
Follow these steps to set up access:
- Submit your ssh public key to the Kitware Password form
- Perform an authentication test:
$ ssh git@itk.org info
