Ron W wrote: > > Does anyone have any experience with hooking up fossil to JIRA? > > > > Do you mean automatic ticket sync between Fossil and an external issue > tracking system? Or using an external issue tracking system instead of > Fossil's?
I guess I meant the former, though the latter is also interesting if it can be made as nice as Fossil's internal tracker (in the sense that it is easy to drill from the issue down to the check-ins addressing it). > My generic experience with the latter has been to either use pre and > post commit hooks, or create a wrapper around the VCS, to interact with > the issue tracking system. > > FWIW, I originally found Fossil while I was looking for an easy to use, > easy to setup issue tracking system that would not require involvement of > the IT people. I'm in the middle of a debate about whether to use Fossil or git+JIRA. If I can hook Fossil up to JIRA then any points about the superiority of JIRA will experience significant erosion. As a separate question along those lines, have people had other sorts of trouble (IT, data sanity or otherwise) with git+JIRA? > That said, there have been times when it would be nice if I could setup > Fossil to receive new tickets from an external system and send updates to > those tickets back. I just haven't had the time to truly look into this. > Off hand, it looks to me like this could reasonably be accomplished with > some combination of the JSON API and the TCL integration. I guess there are complexities around "reconciliation" with those simpler approaches. If the external system and Fossil are incommunicado for some period of time (during which they are diverging), then some process will need to have some way of determining the deltas on both sides and doing the sync. The TCL hooks will not suffice for that, unless you extend the scope of what you mean to encompass those full-sync semantics. (This is analogous to the thinking involved in implementing 'fossil sync'.) This in turn will have much to do with the vagaries how to get data into and out from the particular external bug tracker -- JIRA in my case. The tool appears to support a relatively featureful HTTP/REST/JSON API. I guess one of my questions is whether anyone has tried to bite off hooking up a fossil->jira feed using that API yet, whether they experienced any robustness problems or other gotchas in the JIRA API, etc. -- Eric A. Rubin-Smith Aterlo Networks, Inc. http://aterlo.com _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
