Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 367404 - [server] Pull operation problem
Summary: [server] Pull operation problem
Status: RESOLVED FIXED
Alias: None
Product: Orion
Classification: ECD
Component: Git (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 0.4 M2   Edit
Assignee: Tomasz Zarna CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 359621
  Show dependency tree
 
Reported: 2011-12-22 05:15 EST by Szymon Brandys CLA
Modified: 2011-12-23 06:46 EST (History)
0 users

See Also:


Attachments
mylyn/context/zip (38.58 KB, application/octet-stream)
2011-12-23 06:45 EST, Tomasz Zarna CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Szymon Brandys CLA 2011-12-22 05:15:43 EST
Steps:

1) Clone a repo that needs credentials
2) Add another remote to the repo. Make sure that it requires different credentials than this in 1)
3) Try "Git Pull" on remote 1). You are asked to provide credentials for remote 1), when you provide it, the operation continues.
4) Try "Git Pull" on remote 2). You are asked to provide credentials for remote 2), when you provide it, the operation does not continue and keeps asking for the credentials.
5) Try to provide credentials for 1) instead and it continues now.

I was chatting with Tomek about the issue. It seems that our Git Pull API should rather POST on a clone instead of POST on a remote. It seems that JGit pull operation consults the clone configuration and is not called against any specific remote.

I think we should make the change in our API and move "Git Pull" action on the git repo view to clone objects.
Comment 1 Tomasz Zarna CLA 2011-12-23 06:45:48 EST
Created attachment 208771 [details]
mylyn/context/zip
Comment 2 Tomasz Zarna CLA 2011-12-23 06:46:41 EST
The action has been moved to Clones with 1408576998ff1afc89aa830f1c6399e4a9bdaefe (server) and d73fe200ba3d395ddfd8812c4f31dede72fcc749 (client).