My favorites | Sign in
Project Home Downloads Wiki Issues Source
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 2581: Gerrit misbehaves on *.git.git
1 person starred this issue and may be notified of changes. Back to list
Status:  Duplicate
Merged:  issue 1699
Owner:  ----
Closed:  Apr 2014


Sign in to add a comment
 
Reported by xe...@spotify.com, Apr 3, 2014
Affected Version: 2.7-35-g805ef26

What steps will reproduce the problem?
1. Clone a project from Gerrit <user>@<host>:<project>.git.git
   - This will clone the project correctly
2. Push a change-set and create a review
3. Replication will now fail as it will try to replicate to <project>.git.git

What is the expected output? What do you see instead?
- "It is expected that the clone of a project, accidentally adding an extra .git to the remote uri will fail to clone. And that the replication should try to replicate the actual name of the repository."

Please provide any additional information below.

In Gerrit you can clone from both <project>.git and <project>.git.git. Latter will clone into folder named <project>.git and will set upstream to <project>.git.git. Then you'll be able to push the change into Gerrit and it will appear under <project>.git project name in web search.

Technically the change will be available in original project but both web ui search and replication will see it as a different project and replication will fail trying to replicate to <project>.git.git.

Workaround is to go to Gerrit database and fix the project name for the change (dest_project_name column in 'changes' table).
Apr 3, 2014
Project Member #2 david.pu...@sonymobile.com
(No comment was entered for this change.)
Status: Duplicate
Mergedinto: 1699
Sign in to add a comment

Powered by Google Project Hosting