New Git module

[gustavopinto]

Groundhog currently relies on github api to get information about commits. But, instead, we should perform local git analysis, probably using JGit or similar tool, which will increase our response time, and will be more scalable as well.

[gustavopinto]

I have searched for a while, and I'm in pretty doubt between gitblit and jgit. Both are fairly active, and they cover a lot of git features (much more than we plan to use). The only problem that I saw in gitbit is that it does not use maven.

However, if we only want to browse commits, I heavily recommend the use of gitective. It is built on top of jgit, and the code seems to be much more elegant.

[rodrigoalvesvieira]

Gustavo,

right now, I believe we just want to work with commits. I've searched the Internet for more info and I saw that JGit can be finely used with Gitective and so I'd choose JGit over gitblit. I also believe we won't have any maintainability problems with JGit.

I've no doubt about using Gitective, the library is really good and the code is elegant, like you said it was.

I've started working on this, trying to extract commits using both JGit and Gitective but I'm having trouble listing the commits of a project. This is probably a silly thing and I'm just not getting it because I must've been forgetting something.

Please, @gustavopinto, have a look at the commit referenced by the link above and tell me if you find something :)

The branch containing the temporary works of this issue is ft-new-git-module: https://github.com/spgroup/groundhog/tree/ft-new-git-module

[gustavopinto]

hey @rodrigoalvesvieira, the code is working now :-)

the code is elegant, but the documentation is not so much..

[rodrigoalvesvieira]

Hey @gustavopinto! Awesome!

Yeah, the docs are definitely insufficient :/

BTW, have you figured out how can we get individual commit data like commit date, commit message and such?

[gustavopinto]

Hmm.. I believe that when we have the commit on hand, we can use jgit to get more information about it. For example, we can use the RevCommit class. Some of its methods are: getCommitTime, getAuthorIdent, getShortMessage.

But, later I'll check the jgit documentation, and then I'll report my findings here.

[rodrigoalvesvieira]

ok, then :)

-- rodrigo

On Tue, Sep 10, 2013 at 4:06 PM, Gustavo notifications@github.com wrote:

Hmm.. I believe that when we have the commit on hand, we can use jgit to
get more information about it. For example, we can use the RevCommithttps://github.com/eclipse/jgit/blob/706f8eb9fccfe12f4d0c807efa614a2bcfd1d076/org.eclipse.jgit/src/org/eclipse/jgit/revwalk/RevCommit.javaclass. Some of its methods are: getCommitTime, getAuthorIdent,
getShortMessage.

But, later I'll check the jgit documentationhttp://wiki.eclipse.org/JGit/User_Guide,
and then I'll report my findings here.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/60#issuecomment-24186058
.

[rodrigoalvesvieira]

I ask for insights from @fernandocastor, @gustavopinto and @pork9 about what are the top 5 most important features that Groundhog should cover for local git data extraction. Commits? Tags? What?

[gustavopinto]

Commits FTW!

On Wed, Oct 9, 2013 at 7:15 PM, Rodrigo Alves notifications@github.comwrote:

I ask for insights from @fernandocastorhttps://github.com/fernandocastor,
@gustavopinto https://github.com/gustavopinto and @pork9https://github.com/pork9about what are the top 5 most important features that Groundhog should
cover for local git data extraction. Commits? Tags? What?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/60#issuecomment-26017315
.

[jesusjackson]

I think tags would be great too. So:
Tags FTL!