Back to Support-Home 

• CAF FAQ
  • LOST Password Reset
  • Contacts and escalation when technical problems are encountered
  • New mirror request process
  • History rewrite process
  • How to upload changes/patches to a project
  • Steps the admin needs to follow to add a new person to contribute/administer the project or remove a person
  • Benefits of a full repo sync vs. git clone of a repo

CAF FAQ

This page is for general CAF questions and usage.  For project specific information please check the project wiki.  Links to project specific wiki pages can be found here:

• CAF Active Projects

LOST Password Reset

Go to forgot password in a private/incognito browser window as you may have some cookies stopping the password reset page working correctly.

Contacts and escalation when technical problems are encountered

• For support requests send an email to: itpeople@codeaurora.org

New mirror request process

• In order to request a new mirror for an existing project, send an email to: itpeople@codeaurora.org.  
• Be sure to include:
  • The project the mirror request is for.
  • The URL where the code will be mirrored from.
  • The path to the CAF repo where the code will be mirrored and whether the mirror is in an existing repo or a new repo.
  • The Jira ticket showing LOST approval.
  • If the mirror needs to be re-synced, how often. (Daily or Weekly)

History rewrite process

• Repo history change requests send an email to: itpeople@codeaurora.org
• Admins will make necessary changes to the repo config and respond. 
• once the history changes have been made respond back to itpeople@codeaurora.org notifying them that the change is complete.
• Admins will then remove the ability to change history.

How to upload changes/patches to a project

• First make sure you have been given write access and SSH is setup properly:
  • gitolite_ssh_setup

• Pay special attention to the section called: 'Configure ssh client settings'

If you clone with this method:

           git clone git@git.codeaurora.org:external/<Project Name>/ + <Path to Repo>

for example:
              git clone git@git.codeaurora.org:external/thundersoft/qrd8x25-fmc/qrd8x25-fmc-jb/platform/build.git

For patches:

           git clone git@git.codeaurora.org:quic/sba/<project>_patches.git

for example:
              git clone git@git.codeaurora.org:quic/sba/femto_patches.git

This will work to push the changes:

           git push origin <Branch Name>

for example:
              git push origin master

Steps the admin needs to follow to add a new person to contribute/administer the project or remove a person

• To add contributors or change admins, send an email to: itpeople@codeaurora.org.  
• Be sure to carbon-copy the project Admin so that they can approve this change.

Benefits of a full repo sync vs. git clone of a repo

If syncing from git servers has been slow, try the following. Before you run "repo sync", please tell git to do an on-the-fly substitution of the git URLs to a different location:

The major upside of using http://source.codeaurora.org with "repo sync" is that repo will use a look-aside CDN location for downloading the majority of clone bundles but this only happens during "repo sync" not a regular git clone.  Additional details and mirror information can be found here:  CodeAurora Mirrors

You should be able to see the speed boost yourself if you run the following command:

• curl -L http://source.codeaurora.org/platform/manifest/clone.bundle > /dev/null

Check what it says in "Average Dload" column after it's done. Probably more than 30k you're getting when doing "git clone".