Contributions
Re: ISSUE -> When rework is done and new change set is uploaded to a review the previous uploaded files (with modifications) cannot be accessed anymore.
I am glad to hear you found that workaround. It may be possible the Binary compare viewer was selected by default, and prevented you from selecting a version. This solution will prove useful if the problem arises again. Thanks,1.9KViews0likes0CommentsRe: ISSUE -> When rework is done and new change set is uploaded to a review the previous uploaded files (with modifications) cannot be accessed anymore.
I need the logs to check if there are exceptions or errors on the plug-in code that prevent you to see previous versions. It would also help if we could see your Eclipse log and configuration details. To get this information, go to "Help" -> "About ..." -> "Installation Details" -> "Configuration" tab. Select all of the text in the "Configuration Details" box and save it in a file. Then click "View Error log" and save that information in a file as well. Please send that information on the email to support@smartbear.com Have you tried opening the review on another Eclipse client? Perhaps you could try installing the Code Collaborator plug-in on a simple Eclipse client and opening the file. This would be helpful in order to know if the problem is related to RSARTE or the type of file you are comparing. Do you have this problem when you open other types of files? Thanks.1.9KViews0likes0CommentsRe: ISSUE -> When rework is done and new change set is uploaded to a review the previous uploaded files (with modifications) cannot be accessed anymore.
Could you please send an email support@smartbear.com with a Review dump of the review where you got the error? I have been trying to reproduce the problem, but have not been able to. I would need a Review dump in order to continue testing. Please include the case number 71975 on your email, so we can associate it with this case. To create a debugging dump of the review, open the review in question, then go to the "System" link at the bottom of the page (depending on administrative settings, you may have to be an administrator to do this). In the "Server Backup/Debugging Dump" section, select the following settings: "Server Logs" => "Include Server Logs" "File Contents" => "Include all file content" "Which Data" => "Complete database dump" "Restrict to One Review" => "Only data from Review ID xxxx" Then click on the "Download Dump File" button. DO NOT attach the dump if you reply on this forum; please send it via email to support@smartbear.com, as it may contain sensitive information. Thanks.1.9KViews0likes0CommentsRe: ISSUE -> When rework is done and new change set is uploaded to a review the previous uploaded files (with modifications) cannot be accessed anymore.
Hello, You can select the previous versions from the drop downs at the top of the compare editor. By default the most recent version is displayed on one of the sides, but you can select any two versions to compare, not necessarily the most recent one. What SCM are you using? I would like to investigate to check it is not an error related to the SCM you use. Thanks.1.9KViews0likes0CommentsRe: Create trigger running batch file does requires login every time?
Hi Laszlo, You can either specify the command global options --user and --password on the command line or log in via the ccollab login command line program on the machine that executes the trigger. The login ticket time to live can be configured under Admin > General > External Clients and "Login Ticket Time-To-Live" setting. The global options reference can be found at http://support.smartbear.com/viewarticle/25357/ Regards,933Views0likes0CommentsRe: Is there any way we could add create parameters to the P4 client?
Hi Laszlo, An option would be to run a script that first creates a new review and sets the custom fields that you need to change. Here is the documentation for the command to create a review http://support.smartbear.com/viewarticle/25542/ I tested with this sample shell script: #!/bin/sh #Params: #1: $p #2: $u #3: $c #4: %C ccollab admin review create --custom-field "p4field=$4" --title "Review for changelist $4" ccollabgui --pause-on-error --scm perforce --p4port $1 --p4user $2 --p4client "emptyArgumentPrefix $3 emptyArgumentSuffix" addchangelist last $4 Then on P4V, I configured the script as a tool under Tools > Manage Custom Tools... > New > Tool. I selected the "Add to applicable context menus" check box on the Add Custom Tool dialog. On the same dialog, I set the Application as the script file and the Arguments as $p $u $c %C When I ran the tool, the script first created a new review with the custom field and title I specified. Afterwards the add to review wizard was opened with the review just created as the selected review. After going through the wizard, the review got created with the changelist I selected and the custom field and title I specified on the script. Please let us know if this works for you. - Manuel921Views1like0CommentsRe: Prompting for password for every task in Eclipse JUNO using v6.5, CVS
Hi John, I will forward issues 1 and 1.1 to Product Development so they can be appropriately prioritized. Regarding 2, please make sure you have a valid log in ticket. You can log in from Eclipse on Window > Preferences > Code Collaborator > Server Connection > Test Connection. You will be prompted for the password if you are not logged in. Please notice that if you have the Code Collaborator client installed you may need to open the Preferences dialog by right clicking on the tray icon, then go to Server Connection and finally click on Test Connection, you will also be prompted for the password there. It seems the Eclipse plugin is not saving the new password, but the client does. I will also forward this issue to Product Development. Thanks! - Manuel3.4KViews0likes0CommentsRe: Create trigger running batch file does requires login every time?
Could you please try to manually log in using the "ccollab login" command line before executing the batch file and removing the login command from the batch file? Please let us know if that works for you. Thanks, - Manuel933Views1like0CommentsRe: ccollab addchangelist from Synergy task fails
Unfortunately, deleted files on Synergy are currently not supported in the Code Collaborator integration. If you create a review with only deleted files, the review will get created, despite the error you are seeing, but the materials list will be empty. On the other hand, you can also add other changes besides deleted files and the review will get created without issues, however the deleted files will not appear on the review. Please check if there is a uservoice feature for that at http://feedback.codecollab.com/pages/general If there is not an existing request, please create one for the scenario you need. Thanks!989Views0likes0Comments