Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 339104 - [server] Provide REST API for git log
Summary: [server] Provide REST API for git log
Status: RESOLVED FIXED
Alias: None
Product: Orion
Classification: ECD
Component: Git (show other bugs)
Version: 0.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 0.2   Edit
Assignee: Szymon Brandys CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 334213 339105 340051 340052 340053
  Show dependency tree
 
Reported: 2011-03-07 10:56 EST by Tomasz Zarna CLA
Modified: 2011-09-02 03:44 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tomasz Zarna CLA 2011-03-07 10:56:19 EST 
Could be implemented as GET /git/commit/file/{projectId}/[{path}].
Comment 1 Szymon Brandys CLA 2011-03-15 12:25:07 EDT 
I released changes. The current shape of API is:
1) GET /git/commit/[refId]/file/[pathToFile]?parts=body will return the commit content
2) GET //git/commit/[refId]/file/[pathToFile] will return a log with commits from the first commit to the given refId

The next thing to do is to 
1) parameterize GET so we could specify the full range for the log (Bug 340052)
2) try to return a multi-part response containing both the commit content and details (author, message, etc.) (Bug 340053)
3) revisit tests and add/enable those for git log (Bug 340051)

FYI : I used low level JGit API instead of LogCommand. LogCommand does not allow to filter commits using file paths. See Bug 340049.