jgit as a jira plugin

Hey there,

I've integrated jgit into a plugin for the Jira Issue tracking system. There is more information here: http://confluence.atlassian.com/display/JIRAEXT/Jira+Git+Plugin

I'm new to git, jgit and jira plugin writing, so I have a number of questions. These are the ones I have for you:

1) I noticed that there is a maven pom file.  Are you present in a  
maven repository?  Also any problem with embedding a working snapshot  
in my plugin?
2) I'd like to find out the jgit way to achieve the equivalent of 'svn  
update'.  I understand that fetch can do this but being new to git, I  
don't really understand quite what I need yet.  The goal is to have  
git the latest commits from the origin before indexing.

Thanks for jgit - it took me a day or two to wrap my head around getting the list of files changed in a commit but otherwise its great to have something that can be integrated into jira.

later, jl

-- J. Longman longman@xiplink.com

The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you have received this in error, please contact the sender and delete this communication and any copy immediately. Thank you.

"J. Longman" <longman@xiplink.com> wrote:

Cool!

No, we aren't hosted in any repository yet. The pom file exists to make it easier for people who prefer maven to build, but its not the primary build system for jgit.

Use a Transport instance to execute a default fetch (no args) on say the "remote" origin. That will download the objects to the local database, but it won't update a working directory. But I'm not sure you would care about the working directory in the backend of Jira.

Yea, about that, we wanted to write more tutorials on the API...  ;-)

On 29-Oct-08, at 7:08 PM, Shawn O. Pearce wrote:

Basically I stole the pgm.Fetch code:

Transport tn = Transport.open(repository, "origin");
final FetchResult r;
List<RefSpec> toget = new ArrayList<RefSpec>();
try {
	r = tn.fetch(new TextProgressMonitor(), toget);
} finally {
	tn.close();
}

Can I assume that this enough to update the database? If so I think I'm doing what you're suggesting. After this (and not shown) is some logging code taken from Fetch, which results in the following:

 From /Users/longman/workspace2/work/../masterRepo/
     131dcf5..078d43f  master     -> origin/master

but there doesn't appear to be any specific mention of the incoming changes.

Well, the egit does provide some examples, just there's another API involved which can be confusing. The code in the jira git plugin the key classes are GitManagerImpl and RevisionIndexer, but the RevisionIndexer has some Lucene (text search engine) API mixed-in. Plus I'm still even learning about git much less the jgit api so I can't vouch for quality or correctness ;-). I could snip some code out and send it to you off-list for inclusion in the wiki maybe.

later, j

-- J. Longman longman@xiplink.com

The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you have received this in error, please contact the sender and delete this communication and any copy immediately. Thank you.

"J. Longman" <longman@xiplink.com> wrote:

Yes

Well, the new changes are what "git log 131dcf5..078d43f" outputs.

"J. Longman" <longman@xiplink.com> wrote:

Oh.

Your RevisionIndexer must be looking at HEAD, which is the current branch data. However the fetch process updated the remote tracking refs, which are in a different namespace.

You should point your indexer at "origin/master", or use a bare repository (one with no working directory) and fetch directly into "refs/heads/*" instead of into "refs/remotes/origin/*", that way the indexer can look at branch "master".

Fetch doesn't ever touch the working directory; it only updates the database in the background and the refs/remotes/ namespace so that other applications can see the data that was transferred and choose how to process it.

In command line Git "git pull" uses "git fetch" to get the data and then uses the received data to update the working directory. But a lot of workflows also will just issue "git fetch" on their own to get the data, then examine it with "gitk --all", or do nothing at all because they are mirroring the data, or have to close their laptop and catch a bus, etc...

If all you are doing is scanning the revision history and the files via JGit you just have to run a Transport.fetch() call and then look at the refs that were updated during that call. See the FetchResult object you get returned for the list; it is what the pgm.Fetch class uses to display the output cited above.