Collaborator client/Visual Studio addin and admin rights
Hi, We are using Collaborator 10.0 and Visual Studio addin with VS 2015. For some reason we are experiencing problems using the client GUI and VS addin if we don't run them with administrator rights. Without admin rights, the client GUI starts but the Add Changes/Shelvesets/Changesets buttons don't do anything. In Visual Studio, the Collaborator pane shows up but doesn't show any reviews and the Add files to review and New review from changes buttons are dead. When we start the client or Visual Studio as administrator, we have no problems. Is it a feature that admin rights are required or should they work also without them? Any advice to fix this would be nice. Thanks a lot, - Dukeman
There is no git option in Windows Client 8.5.8501
We have a corporate installation of Code Collaborator. The server version is 8.5.8501. I have downloaded and installed the Windows Client version 8.5.8501. When I try to add an SCM configuration there is no git option. I see AccuRev, CMVC, CVS and ClearCase. If I select the folder with the git repository and let it auto detect it informs me that it doesn't know the type of version control. For reference, I have Cygwin git installed as well as Windows git. Windows git is on the system PATH. What am I missing?
username discrepancy between ldap, sso and git result in "not participating" error
Hello, We have collaborator13.6.13601 enterprise, and recently a few users that have a specific prefix in their username in ldap, are not assigned a role on a review, instead they get "not participating", see screenshot. in ldap the user is `t_foo`, where "t_" denotes a contractor/temporary employee If we go into the user admin section and rename the user to "t-foo" to match what Github uses, the old "t_foo" user is recreated in Collaborator automatically, and the user still cannot be assigned to a review properly. Most of our users have the username convention "<lastname><f>"
create-review post commit hook - password management and participants
Hello Is there any tutorial on how to get this working in a production environment? Especially useful would be some hints on how: 1. the hook should manage the required passwords ( ccollab-admin-trigger-create-review) (we use LDAP). 2.we can control the participants of the review (ie. like a per-user or per-source branch template?I imagine this could be done with some "custom scripting" but since it's probably a very popularrequest is there some built-in support or best practice?)
CodeCollaborator and Git - ClearCase addversions equivalent for Git?
Dear experts, My team is actively pursuing the command line utilization of Collaborator with Git (not GitHub or an public remote Git application). In clearcase, the branch name and revision number of a file is uploaded via the "addversions" command using the "ccollab" program. This has the wonderful feature of being able to switch between revisions and knowing which version you are on. WIth Git, there aren't really "version" as much as there are hashes for commits, which are what show up when you upload diffs or files to Collaborator. I know it is possible to upload comments to the overall review page such as: $ccollab addgitdiffs --upload-comment "$(git log -g -n 1 "03db" --)" "69451" "03db^..2fbe" that grabs info from the commit 03db and puts it on the review page. This does not contain information on the branch normally. Is there anything that can mimic the behavior of ClearCase so that the Git branch is clear and it is relatively easy to track which revision of each file is being looked at, or is this a lost cause. Thank you for any help.
Get list of git commits for a review?
We need to confirm that every commit in our git master branch has been reviewed in some completed CC review. Most people use the "Add Git Diffs..." and then do a master-their_branch diff. After their review is approved and they've merged their branch into master, we'd like to generate a report that shows that every single commit in the master branch has been reviewed. Any techniques, help or insight on how to start off or to do this will be greatly appreciated. For example: if there is a Rest API that I can call for each review that lists all of the commit SHAs, then I can write a quick script to call that and then use "git log" against master and thereby confirm that no commit has been left out. TIA!Linux P4V with Smartbear: It takes long time to show existing reviews
While trying to update existing review with new changes, Linux P4V "Smartbear - Add to Review" GUI takes very long time to show all the existing reviews. Also 100% of the time, it doesn't have to show incoming reviews which is not useful at all and I think it takes huge time to get them all. Number of incoming reviews is not in my control as people keep adding me in reviews. This tool unnecessarily searches and shows all incoming reviews which are open for past many years. Need to option to show only outgoing reviews and it should show the existing outgoing reviews in very short time.