Exceptions thrown during GIT slurp

XMLWordPrintable

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Low
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Severity 3 - Minor

      Yeah, not a problem at all. Usually I'd file a Jira or something (I've
      got a long history with the Atlassian public development model), but
      didn't really have time at the moment.

      Not a worry if they want to follow up, or once things quiet down here
      a little getting us to try an experiment.

      Kirk

      On Wed, Oct 28, 2009 at 5:53 PM, Jesse Gibbs <sales@atlassian.com> wrote:
      > Hi Kirk,
      >
      > I've forwarded your log file and this email thread to our FishEye
      > development team so they can investigate further. I can't speak to when the
      > investigation will happen since team is working feverishly to wrap up the
      > 2.1 release, slated for mid-November.
      >
      > Would it be OK if they follow up with you in case questions arise during the
      > investigation of the issue?
      >
      > Let us know,
      >
      > Jesse Gibbs
      > Atlassian
      > [sales@atlassian.com]
      >
      > San Francisco, United States: +1 415 701 1110
      > Sydney, Australia: +61 2 9262 1443
      > Amsterdam, Netherlands: +31 20 794 4530
      > We're hiring (a lot). Tell a friend, earn some cash.
      >
      > ________________________________
      > The thing was that it looked at first glance like it was working, but
      > then it was throwing exceptions and things. (I actually captured the
      > logs and they're attached). Now some of this may just be that Git is
      > such an immature an changing tool, or that Github was having issues
      > (which it often does), but when I started seeing that many stack
      > traces, and you guys were explicitly saying that it wasn't supported
      > for production workloads, I just backed off for the time being.
      >
      > Kirk
      >
      > On Wed, Oct 28, 2009 at 3:49 PM, Jesse Gibbs <sales@atlassian.com> wrote:
      >> Hi Kirk,
      >>
      >> Sorry to hear that FishEye's integration with git isn't meeting your needs
      >> yet.
      >>
      >> Are there specific issues which we could pass on to our development team
      >> that you think are most important to improve? This sort of feedback is
      >> invaluable to us as we continue to improve our products.
      >>
      >> Please let us know,
      >>
      >> Jesse Gibbs
      >> Atlassian
      >> [sales@atlassian.com]
      >>
      >> San Francisco, United States: +1 415 701 1110
      >> Sydney, Australia: +61 2 9262 1443
      >> Amsterdam, Netherlands: +31 20 794 4530
      >> We're hiring (a lot). Tell a friend, earn some cash.
      >>
      >> ________________________________
      >> Hi, Doug,
      >>
      >> Right now we're not planning on going forward with FishEye, largely
      >> because the support for Git just isn't good enough yet. I've used
      >> FishEye extensively in the past with Perforce repositories, and it
      >> just works brilliantly, but the Git support really isn't ready for
      >> prime-time.
      >>
      >> When and if the Git support ever improves enough for our use, we'll
      >> definitely reevaluate FishEye.
      >>
      >> Thanks a lot,
      >>
      >> Kirk Wylie
      >>

            Assignee:
            Unassigned
            Reporter:
            Kirk Wylie
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: