MJackson
StaffJoined 11 years ago
User Profile
Staff
User Widgets
Contributions
Re: LDAP Authentication setup issues
Look for this part of the ROOT.xml file: <Parameter description="The name of the Code Collaborator system administrator who is always allowed to log in. " name="system-administrator" override="false" value="admin"/> (In other words, the value of that Parameter tag is the admin that is being referred to above.) For ldap, either you'd need an "admin" user to match the ROOT.xml declaration above, or change the above to match the login of an administrative user you already have defined in ldap. In other words, the system does password auth against LDAP as normal, but if the login matches that ROOT.xml declaration, they're exempted from license checks.3.9KViews0likes0CommentsRe: Displaying current filename as page title when opening file diffs in new tabs
Hi Gina, the "page title is SmartBear Login instead of the filename" thing is a known issue (COLLAB-512). We don't have that immediately slated for a dev sprint, but when we do fix it that ticket number will show up in the changelog section of the manual.1.1KViews0likes0CommentsRe: Defects disappeared and review materials stuck on Loading...
It's hard to tell without seeing the logs/system data but it sounds like there's some sort of error in the db for that review. I'd suggest opening up a support case through normal channels. They will likely want a review dump to diagnose the issue (click on the "System" link in the footer and then the download button on the page that leads to).2.6KViews0likes0CommentsRe: LDAP Authentication setup issues
Sorry we didn't catch this earlier. For what it's worth, the account defined as the admin in ROOT.xml never consumes a license (we don't want licensing issues to ever interfere with getting in to manage things; by the same token that's why admin by default doesn't have the ability to create new reviews).4KViews0likes2CommentsRe: Add Git Diffs with path?
Git diff itself (see "git help diff") requires a -- between revisions and path(s), and in turn the ccollab client requires that as those options are passed through to git diff. So for your example, you probably want something like: ccollab addgitdiffs new integration mybranch -- /configuration (nb: that would be interpreted as an absolute path... if you mean a directory named "configuration" in your repo, you probably want to omit the slash)5KViews0likes2CommentsRe: How to use Collaborator tool for code review in Testcomplete tool(10.0)
I'm not that familiar with TestComplete off the top of my head; as I understand it (and I could be wrong!) TC has some way to export test cases to a version control system (e.g. git). Those commits (or diffs) could then be added to Collaborator just like any other. This does assume that the exported test plans are in some sort of human-readable format; if it is a binary file then obviously a diff view during the review process will not be useful. (Our QA team does use TestComplete internally on Collaborator as part of their test plan; but I have not used it directly, hence the above is based on relatively minimal knowledge of their product.)1.6KViews0likes0CommentsRe: Using Flash within Collaborator
http://community.smartbear.com/t5/Collaborator-Feature-Requests/End-Collaborator-s-use-of-Adobe-Flash/idi-p/102316 There is an existing request to remove it (see above for full details). We plan on doing so in the near term. The short summary is that it is there to support older versions of IE.1.3KViews1like0CommentsRe: Cannot add git diffs when external diff viewer is configured
Unfortunately, we only officially support the current and previous major releases; i.e. only 9.x and 8.x at present. Our standard recommendation for users on older versions is to upgrade wherever possible (naturally, using a test environment first) into the window of supported versions. (9.2 in most cases. If you were using IBM's RTC or could not upgrade past JRE 6, you'd probably have to stay on 8.4.8406 at present.)1.9KViews0likes0Comments