Problems configuring Review Assistant...
Posted: Tue 28 May 2013 12:07
We have been trying to evaluate Review Assistant, but have run into a basic configuration problem.
Here's our workflow: All our programmers (less than 10) work remotely from various locations around the United States. Our source code is kept in several remote Git repositories stored on a Git web hosting service called Assembla. (Assembla is similar to GitHub.) Each programmer uses Git on their local machine to access cloned local repositories of the source on Assembla. Each programmer uses Visual Studio 2012 to do his/her development using the local source files, committing to their local Git repositories often during the day. Each programmer periodically pushes their local commits to the remote repository on Assembla and pulls down the other programmer's commits.
Here's what we've tried so far: We installed Review Assistant server on a Windows machine in our company's main office and mapped a remote port number to internal port 85. We set up a single Review Assistant project, indicating Git was the source control system. We installed Review Assistant client on each programmer computer and can successfully log into the Review Assistant server from each. On each programmer machine, we've specified the correct PATH variable for Git: "C:\Program Files (x86)\Git\bin". This path is the same on all programmer machines. However, a problem arises with the Repository specification inside the project specification. When Git is chosen as the "Type", it appears like all programmers must specify the same "Working Directory". Different programmers have cloned their local Git repositories into differently named folder trees.
Does Review Assistant REQUIRE that the Git source code repositories all exist on a central LAN and all programmers must be connected to that LAN and be using the centralized repositories (as opposed to local repositories). Is there any way we can use Review Assistant in our workflow configuration?
I just realized as I was typing this, we might be able to have each programmer set up a local file system "share" name and map that to the same drive letter (such as "X:"), but do we really have to jump through those kind of hoops in order to use Review Assistant?
Here's our workflow: All our programmers (less than 10) work remotely from various locations around the United States. Our source code is kept in several remote Git repositories stored on a Git web hosting service called Assembla. (Assembla is similar to GitHub.) Each programmer uses Git on their local machine to access cloned local repositories of the source on Assembla. Each programmer uses Visual Studio 2012 to do his/her development using the local source files, committing to their local Git repositories often during the day. Each programmer periodically pushes their local commits to the remote repository on Assembla and pulls down the other programmer's commits.
Here's what we've tried so far: We installed Review Assistant server on a Windows machine in our company's main office and mapped a remote port number to internal port 85. We set up a single Review Assistant project, indicating Git was the source control system. We installed Review Assistant client on each programmer computer and can successfully log into the Review Assistant server from each. On each programmer machine, we've specified the correct PATH variable for Git: "C:\Program Files (x86)\Git\bin". This path is the same on all programmer machines. However, a problem arises with the Repository specification inside the project specification. When Git is chosen as the "Type", it appears like all programmers must specify the same "Working Directory". Different programmers have cloned their local Git repositories into differently named folder trees.
Does Review Assistant REQUIRE that the Git source code repositories all exist on a central LAN and all programmers must be connected to that LAN and be using the centralized repositories (as opposed to local repositories). Is there any way we can use Review Assistant in our workflow configuration?
I just realized as I was typing this, we might be able to have each programmer set up a local file system "share" name and map that to the same drive letter (such as "X:"), but do we really have to jump through those kind of hoops in order to use Review Assistant?