ebrown_1
AlumniJoined 15 years ago
User Profile
Alumni
User Widgets
Contributions
Re: Prompting for password for every task in Eclipse JUNO using v6.5, CVS
The 7.3.7302 release now available fixes this issue. The problem was not related to loggin in per se, because that worked, but in saving the login ticket. NOTE: if you also have the CodeCollaborator GUI client installed, you must upgrade it as well as the Eclipse plugin, to this latest version. You will need to use the Test Connection procedure (described above) initially to get a login ticket. After that, you should not be prompted again. Eric888Views0likes0CommentsRe: Code collaborator not connecting to TFS while adding shelvesets
Naveen, Is the shelveset yours? If you create a debugging log that includes this error, we can look into why it's happening. If you're using the GUI client, select Help->Capture Debugging Log, then go to the main screen and reproduce the error adding a shelveset, then return to the debugging dialog and save and email the log file to support@smartbear.com. If you're using the command line client, rerun the ccollab command and include the --debug option as the first argument, e.g.: ccollab --debug addchangelist new myshelveset This will create a ccollab.log file in the current directory - email it to support@smartbear.com. Thanks! Eric1KViews0likes0CommentsRe: Prompting for password for every task in Eclipse JUNO using v6.5, CVS
John, 1 & 1.1. Can you tell me what version of the CodeCollaborator server you're using? If you email this information to support@smartbear.com, we'll look into this as a support request. 2. A fix for this issue should be going out in the next maintenance build. 2.1 We now use tickets for authentication, and you can validate your login by pressing the Test Connection button in the Server Connection settings for CodeCollaborator. This will prompt you for your password.3.4KViews0likes0CommentsRe: What are the exact permisions required for codecollaborator's Oracle account.
Perhaps you can help us answer this definitively, since we don't have an Oracle DBA in house. We do know that in most Oracle configurations, you can fulfill all requirements by running CREATE USER COLLAB ... And then using COLLAB for both the username and schema for Code Collaborator. Are the granted privileges the same as running GRANT ALL ON schema.* TO COLLAB? And are there privileges given by these that you are concerned about?1.3KViews0likes0CommentsRe: Using SVN without http access
Yes, you can do this. Read up on our server-side SCM integration at http://codecollaborator.smartbear.com/docs/manual/6.0/admin_version_control.html to see how to set this up. Note that our Subversion integration uses the svn command line client (so if you're using something like TortoiseSVN you'll want to install a compatible command line Subversion client).636Views0likes0CommentsRe: Is it possible to Specify which version of the file is under review
Sorry, we do not support the Add Versions functionality in our CCRC integration. If you want to see incremental revisions of a source file in a review, currently you would have to upload each revision as you go. Let us know if this would be a useful or necessary feature for your development environment - we are interested in enhancing our CCRC integration to fit how CCRC is used. I've created a feature request for this in our UserVoice forum at http://feedback.codecollab.com/forums/4652-code-collaborator-features/suggestions/2476476-add-versions-support-for-clearcase-remote-client-. You (and any other of your coworkers) can vote for it - this will help us gauge the demand for it.781Views0likes0CommentsRe: Print to Review for Doc Review cannot work on Windows 7
I assume you've recently downloaded and installed Print To Review. What version of the Code Collaborator client is installed on your system? If it's not a recent version, please download and install the latest client release instead.1.3KViews0likes0CommentsRe: ccollab addgitdiffs not finding local diffs
Ryan, Sorry that no one has answered your question yet! Yes, you can do this by generating a debug log (which we commonly use to debug issues) and examining the output. Use the --debug option to do this (i.e., ccollab --debug ...). This creates a ccollab.log file in the current directory. Just grep it for git and you'll see the commands issued. Eric1.1KViews0likes0CommentsRe: Is there a command via the command line client that will list completed reviews
Shawn, The command line doesn't have a way to do general queries such as this, although you can create custom SQL queries for your Code Collaborator database. Refer to our schema here for specifics: http://codecollaborator.smartbear.com/docs/manual/6.0/database_schema.html If you have questions about creating a query, email support@codecollab.com. One thing to consider is a query of all completed reviews could (eventually) make for a slow check-in. What I think would work for what you want to do, and a generally good approach to verifying commits, is to require the author put the review number in the commit comment. This allows you to use the 'ccollab admin review-xml' command line command to dump all the review metadata for a known review number. Your check-in policy could have a review number matching expression to find the review in the commit comment, and then you query the review-xml output for the details you're interested in checking. Eric881Views0likes0CommentsRe: Unsupported SCM System or Client
Carlos, Regardless of whether you eventually run with the Eclipse plugin or not, first let's get the Code Collaborator GUI client working with TFS on your system. The Code Collaborator TFS integration uses the Teamprise command line client, tf. It needs to either be in the system path, or be specified in your SCM configuration in the client (the tfs-exe parameter). The Validate button in your SCM configuration for TFS will verify that tf executes as expected. It is possible your new Teamprise installation does not include the tf command line client? The same applies to running under Windows - the tf.exe must either be on the path, or be specified in the Code Collaborator configuration for TFS. Perhaps your new Teamprise installation does not have the tf command line client? Let me know if that's the case. Eric2.1KViews0likes0Comments