OlegB
AlumniJoined 9 years ago
User Profile
Alumni
User Widgets
Contributions
Re: Does Collaborator support multi-repository code reviews?
alexey_subach, Yes, number of repositories are not limited. Commits can be uploaded from different repositories to the same review. You just need to configure the desktop clients properly. I.e. one SCM configuration for each of the Git repository: https://support.smartbear.com/collaborator/docs/source-control/git.html#options The command-line solution is more flexible and can be scripted in case you need to automate this job.477Views0likes0CommentsRe: Command line ccollab stopped working and now cannot configure SCM...
Hi dspells, It seems the command-line client can't detect your SCM system automatically. To avoid this issue, you can use the global options and force the client to use specific SCM-related options: https://support.smartbear.com/collaborator/docs/reference/cmdline-global-options.html#subversion Also, you are trying to upload all the locally modified files from your local SVN repository. Make sure that the current directory of the terminal/cmd was changed to the directory where your local SVN repository locates before executing the "ccollab addchanges new ." command.1KViews0likes0CommentsRe: Migration of user accounts to new machine?
Hi davem All the users, review, and configuration data is stored in the database. If you want to copy this data to a new machine, you will need to migrate it: https://support.smartbear.com/collaborator/docs/server/admin-tasks/backup.html Note: the data can't be migrated partially. Note: the migration dump file can only be restored to a completely empty database.866Views0likes1CommentRe: Perforce updating changes
Hello Witty You can use the same command to upload the changes from your pending changelist. Collaborator will detect the changed files and upload newer versions to a review: https://support.smartbear.com/collaborator/docs/reference/command-line/ccollab-addchangelist-perforce.html613Views0likes0CommentsRe: Gitlab Improvements in 13.5
Hello rabzak, For the Merge Requests, GitLab uses a specific pipeline. Collaborator still creates job for it but, in previous versions, the job was added to a new thread. Thus, the status of the Collaborator's job wasn't shown in the overlay of the MR pipeline. In newer versions, Collaborator starts adding the job to the same MR pipeline.456Views0likes0CommentsRe: Unable to install Code collaborator client
Hello lakshmikanth, Are you running the installer on a Unix instance and under "sudo"? If yes, try to run it using your own account. If the issues still persist, try to run the installer in console mode. To do this, add the "-c" option, e.g.: sh ccollab_server_13_5_13500_unix.sh -c If still no luck, ensure that you are using the Oracle vendor of Java and it is set as default in the system: https://support.smartbear.com/collaborator/docs/reference/java-compatibility.html https://stackoverflow.com/questions/12787757/how-to-use-the-command-update-alternatives-config-java1.8KViews0likes3CommentsRe: CodeCollab GUI Error
Hello BooHyunJang, This error may indicate corrupted instances of both Collaborator client or Java. It also can be caused by an unsupported Java vendor. Try to follow the steps below: 1. Uninstall the Collaborator client. 2. Launch the command prompt as administrator. 3. Navigate to the location of the Collaborator client installer and run it from the command prompt as below: the_name_of_the_executable_file -manual When the client installer is executed with the -manual option, it will ask you to provide the path to the Java location. If you see any exceptions, post them here. 4. Check if the issue exists after re-installing the client. If the issue still occurs, try to uninstall Java completely, install Oracle Java 1.8, and follow the steps above one more time.1.2KViews0likes0Comments