Question

We are getting ready to use an offshore dev team for one of our projects. My concern is security. We havent used this team before and we are simply trying them out on a small test project to fix a few bugs on a particular application. They will need access to kiln and fogbugz.

Right now for this particular application we have the stable, test and dev repositories.

We have a couple of ways to go and wanted to get your opinions:

1. Simply assign them to the appropriate repository as a user and they can create a local version of the repository, make the bug fixes and push that code back to the repository. we would then deploy the code on the test server and see if they have fixed the bug(s) correctly.
2. Clone the appropriate repository, set them up with appropriate user rights, let them fix the bugs, push that code back to the cloned repository then we can merge with the 'real' version of that repository.

Any ideas?

Thanks in advance

Answer 1

If you want to keep everything separate, I would use the second option. Give them permissions to an entire Kiln project, but only clone the repos that they need to that project. That way, they will be able to use Kiln to its fullest, and you won't have to expose more than you need to.

You can add a new project by going to Admin (in the top right corner of the page) and clicking Projects. From there, create a new project and give them admin permissions on it. Then go through your other projects and give them no permissions on everything else.

To clone the repos, just make branches of each repo they need. When you're making the branches, make sure to click 'Advanced Options' and choose 'Central Repository'. Then, when you've made all of your new central repos, go to their settings page and change their project to the new project you just set up.

Once the offshore team has started committing changesets, you can pull them from their project into your project by going to each repo's In/Out tab and pulling. This should make it easy to let them do what they need to do, while still isolating the repos they need to work on.