|
[
Permlink
| « Hide
]
Matt Quail [Atlassian] added a comment - 31/Jan/08 06:54 PM
The next time this happens, can you grab the response with the stack trace and post it here?
Now the behavior seems a bit inconsistent. Each trial run I post here will be preceded with a ctrl-refresh on the page.
This trial run had a post of: command add And a response of: <html> <br/> Thanks for that info, we will investigate this for the next release. Could you please zip up your FISHEYE_INST/var/log/* files and attach them (either here, or create a support request on http://support.atlassian.com/
attaching log files as requested
hmm... are those log files going to contain any sensitive information?
they won't contain passwords, but they will contain the names of many of the files in your repository, etc. I suggest you create an issue in support.atlassian.com and attach it there (since only you and Atlassian will be able to see the issue).
Can you remove it from this case please?
attachment has been removed
I submitted the logs in this support case: https://support.atlassian.com/browse/CRC-163
Unfortunately, after being so interested in Crucible/Fisheye, I no longer am. I swear that I remember reading the Crucible licensing page several times, and it saying that a license of Crucible included a license for Fisheye. On that basis, the combination seemed to be a reasonable price. I went ahead and got the purchase request approved, and now the licensing explicitly says that separate licenses for fisheye are required. When did that change? Crucible isn't mature enough (in workflow smoothness, mostly) to justify that cost to me. Too bad. Thanks for the feedback Bruce. That note about licensing has always been there. You probably got confused by the note on the download page. We will be trying to make this clearer.
Crucible is getting more mature all the time, hopefully you'll consider it again later. The upcoming release will add review metrics, a plugin framework, and an improved API. A more flexible workflow is on the slate for the following release. There is also an IDE plugin in the works too. Also note that the dependancy on FishEye is only an interim measure, we plan to release a standalone version of Crucible for people like yourself that don't value the FishEye functionality. This is also on the slate for this year. Thanks again for taking the time to report this bug. Sorry for wasting your time. I am encountering the same error in Version:1.1.4 Build:build-249 2007-11-09
Angus,
Can you raise a support issue on support.atlassian.com and we can work through the issue there with you. You'll probably want to grab the latest version of Crucible as a start to see if the issue still occurs. I'm closing as Bryce has moved on from his evaluation. If anyone has similar issues, please raise an issue on support.atlassian.com and we will work through the issue there.
Actually, we did end up going ahead with the purchase, and I've re-opened https://support.atlassian.com/browse/CRC-163
|
||||||||||||||||||||||||||||||||||||||||||||||||||||