I am just trying to understand advantages of going to Team Drive for team repository on G suite vs using just shared folder on Google Drive. By searching different sources and doing testing I found the following results so far.
Frankly speaking this all makes me think whether Team Drive at the moment offers that much of advantage vs shared folder on Google Drive.
Questions:
1) did I miss anything in my analysis?
2) is there anything else Team Drive offers, which I did not mention?
3) Are there any other pitfalls (hidden problems) to use google Drive shared folders for team repository?
Advantages of Team Drive vs shared folder on Google Drive:
When contributors leaves the company, files they own will not disappear, if they were placed in Team Drive.
This however can he resolved, by simple automation, that manager becomes an owner of the files of people, reporting to him, who left the company
Edit access feature:
In a Team Drive you can have editors / contributors, who do not get permissions to delete or move files. Well, this is a good feature and clear advantage.
Limitations of Team Drive
One gets the same permissions for all files in one Team Drive.
Since most of the people contribute to some of the projects in one way or another, for us this means that everybody would get edit permissions for all project repositories in entire company, which is not what always desirable
Not possible to manage access permissions in hierarchical way
This is a consequence of the 1st one. In google drive say regional manager can have access permissions to entire region. He would then create subrigional folders and would assign them to sub-regional managers. Sub-regional managers would manager only their folders, but would not see other sub-regions folders. However permissions of regional manager would flow down and they will automatically see everything. Sub-regional managers would then create sub-folders for individual projects and give access permissions to individual Project Managers
In Team Drive such construction is not possible.
File and / or folders cannot be in multiple locations
This is really good feature of a Google Drive, which is missing in a Team Drive
Amount of subfolder levels limitation
It is 20 now, but still, this is a limitation
Amount of items (files/ folders) limitation
This is 400 k now, but still, this is a limitation
Limitations with migration of files from Google Drive to Team Drive
Links to folders will break.
Links to the folders do not get preserved, when they get migrated to Team Drive
Disappearing files / folders
If there was a file or folder, which was in multiple locations and one of these locations was in the folder, migrated to Team Drive, than this Drive folder/file would disappear from other locations as well, not only from the folder, which was explicitly migrated to Team Drive.
I can add something to your analysis:
Advantages of Team Drive
Drive File Stream: it's a Dropbox-like app, it will mount a virtual disk on your system. Files copied/moved there don't take up disk space.
Limitations of Team Drive
You can't share a folder, just singles files or the whole Team Drive. This is not something I would expect from an enterprise dedicated tool...
Related
I'm in a very frustrating situation where we are trying to clean out a large amount of data in a TFVC repo on an Azure Devops Server installation. I am a domain admin, I am the SQL server admin, and an admin anywhere I can find throughout Devops.
Yet, I had multiple issues trying to delete the top level folders out of the repo due to needing Read or Commit permissions. So, I managed to navigate through all the different levels of folders and identify a few folders/files where inheritance was turned off and I didn't have permission, so I added myself, and voila was able to delete the folder/file.
However, I have one folder left that refuses to let me delete it. It tells me I need Commit permissions on the folder. There are no other folders/files under this folder that are visible.
I've searched high and low for anything that would let me "take ownership" or some how override these permissions that are possibly buried under this folder somewhere. I suspect maybe there is a deny or broken inheritance under this folder that prevents me from even seeing the data.
Is there anyway to gain access to this and delete this folder?
A client is requesting I provide a list of "people with access" to all folders an files within the company. This is a daunting task and I was wondering if there was a way to do this whether it be through Vault or by some other means.
We have this VSTS online account, and we want to see a list of all mapped workspaces of all users in one place.
We know that we can go to each developer's PC and use tf.exe workspaces to get the list of workspaces on that machine.
But we need to do it without going to each developer's PC. The reason we need this is that we suspect some team members use their credentials and map a workspace on a machine outside our company's environment, without our permission.
Is there a way to see all mapped workspaces in one central place?
The easiest way is to use something like Attrice TFS Sidekicks. It should work with VSTS, even if it doesn't say it does.
However, the more permanent solution is to set up conditional access in your Azure AD. That allows you to add restrictions so that your users cannot log in from outside your network.
(I know it's an old post, but researching for my own purposes...)
Extrapolating off of how to remove TFS workspace mapping for another user
The following worked for me:
>tf.exe workspaces /collection:https://contoso.visualstudio.com/ /owner:*
I'm advocating using Visual Studio Team Services for our source control solution, and have actually started doing so. However, my manager, who is somewhat apprehensive when it comes to cloud-hosted storage and services, wants to know what our contingency plan is in the event of Team Services ceasing to be accessible for whatever reason.
I've pointed out that we have our source code on our developers' computers, in their mapped work spaces, but admittedly if we ended up with just that and no access to Team Services we'd certainly be in a bit of bind. They might all be working on different parts of the same solution and we wouldn't be able to check all of their changes back into the central repository or merge changes made in separate branches. We also wouldn't have access to the comments associated with previous check-ins, or our backlog, tests, etc.
So, the question is, is there a way to backup everything that we're hosting in Team Services so that, in the event of something going wrong, we'd be able to restore all of that to a locally-hosted installation of TFS (or somewhere else)?
I'm a bit late to the party but we developed a Team Services backup tool. We scheduled it as a scheduled task and it runs once a night. It then just clones all our repositories to disk.
Taken from this blog:
We use the VSO Rest API to query our VSO account and get all the data
we need. Since in VSO you can only have one Team Project Collection,
we retrieve all the team projects of the default collection. Each of
these team projects can have multiple repositories that need to be
backed up. A folder is created for each team project and saved to a
location on disk that can be configured in the app.config. When the
team project folder is created, the task loops over each repository in
the team project and creates folders for each repository.
You can also fork it on GitHub here
There's no out of the box backup ability.
Now, if you are only referring to source control, and not work items, pull requests, builds, test plans or anything else that the service offers, then I'd suggest you migrate your code over to git.
With git every developer will have a complete copy of the source repository, including all history and commit comments. From there, it's a simple task to push the git repository to a different git hoster (such as bitbucket or github) and make them your new centrally hosted git repository.
On a historical note, Visual Studio Team Services at one point offered a data export for a period of time. You might want to add a vote or three to this related UserVoice idea to help raise the importance of the feature with Microsoft.
Side comment: The business risks in using Visual Studio Team Services will come from either Microsoft shutting down the Visual Studio Team Services service or that the underlying Azure infrastructure has such a catastrophic failure that your Visual Studio Team Services account is unrecoverable. Both of those are extremely low risk, and very likely lower than the risks you'd have running TFS on-premises, in your own data centre, unless of course, your infrastructure and staff are better than Microsoft's :-)
Not a full VS backup in terms of a restore of service. But you can take a full Zip from root down using the Code web site. Right click the root folder and has a zip download option. Pretty neat feature.
The easiest way to back up everything is to use something like the TFS Integration Platform to periodically pull off all your data into an on-premises TFS solution. I've set this up using an Azure VM that we turned off when we weren't actively backing up, which makes it really low cost. For more info on using the TFS IP with Team Services, see this: http://nakedalm.com/migration-from-tf-service-to-tf-server-with-the-tfs-integration-platform/
I am looking for a private online source control system. Basically what I want is a private version of Google Code or SourceForge. Private in the sense that only me and the person I invite can view the source code. The source code in the source control should not be exposed to search engines or other people without the proper viewing rights.
I prefer to hold the source code on other servers, not on my machine. I don't want to handle all the database maintenance and backup and things like that. In exchange for this I don't mind to pay a monthly access fee for this.
Any ideas?
Atlassian's BitBucket just announced Git repositories last week. Bit bucket allows unlimited private repositories for free. You need to pay if you want more than 5 users.
A vote here for Unfuddle
The free offering has 200mb and unlimited (numbers of) git/svn repositories within that 200mb.
Assembla - for Subversion - www.assembla.com. Free Subversion / Trac
A friend of mine recently told me about bitbucket by ATLASSIAN
This is a great one, including their free plan version.
GitHub can do that (with a paid-for account).
I know this question has been posted a while ago. But, how about this:
If you're developing from a Windows machine, download the Google Drive client and sync your Google Driver folders on your local machine. Within those synced folders, create one called repository or something.
Then using git, you create a bare repository in that folder. Or in Bazaar, a repository with no-trees. This will create a repository that will not contain the actual working files, but just keep the revision history. This has the advantage of saving disk space as well as letting you pull and push from/to it like a centralized repo.
And since it is within your Google Drive synchronized folders, it will be backed up on Google drive and synced. And you can allow access to your folders using email addresses.
For Subversion I use DevjaVu.