[git-users] Re: Enforcing best practices in GIT Server inherited
On Monday, March 9, 2015 at 8:44:09 PM UTC-4, William Lasiewicz wrote: > > 3 questions. Thanks in advance for reading this and to whoever answers my > 3 questions. > > I am the release manager and we have perforce but we inherited a GIT > repository. > So far about 20 developers access this which is done through creating a > ssh key and then adding that key on the machine where we have git. > Everyone logs in through the same user "git". Everything is at Git\home, > which contains about 25 .git directories. > Telling who checked in files is on the honor system. > As far as I can tell, setting up a git user is done by adding a user to > the machine. > Is this really how this is done for this? > The first thing I want to do is give everyone their own user name so code > access could be restricted to the areas that are needed. Is this something > not done in GIT? > One thing you need to bear in mind with open source software is that all you get is the source code. Then you have to make it work for you, and that means adding components around the core component. Commercial products have manuals, support, recommended hardware configurations and so on. In the case of Git it makes sense to have a central repository management system similar to the p4 depot. This is where GitHub may come in or you may want your own on/site solution using Gerrit, for example. I work for a large global enterprise and we use Git heavily these days ... we have a centralized system of servers that are based on Gerrit, and everyone can be identified using their corporate id. And we thousands of developers on that system. Gerrit provides access control and repository management features as well as code review, so have a look at the options for managing your repositories. BTW Perforce are supporting Git heavily and have just announced Helix ... check out their web site. Remember that whole Android development is performed this way, and companies like Google, Sony Mobile and SAP are contributors to Git and Gerrit., and of course Git was developed for the development of Linux. > > So far I can't come up with a reason why you would use this instead of a > real tool, but we don't have perforce licenses to add for all these people > and the bosses want me to look in to taking our perforce which has > substantial automation in builds and deploys and converting it to this tool > which looks to be as sophisticated as the old file based stuff that was > used 15 years ago. > What could be benefited from using this? > As others will have said Git is widely used both in open source and in enterprises, so it is not novel or strange ... you will find that many developers out there are already familiar with Git. It is fast, and developers are able to be more independent of network and infrastructure issues. This is important if you work with countries where the network is slow or unstable, so it is more robust than systems that rely on a live connection between a client and server. It scales but if you need to use very large repositories then Mercurial may be a better bet since Facebook invested in it. Others will no doubt add more! Git is here so it is worth investing some time in learning about its capabilities ... -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[git-users] Re: Enforcing best practices in GIT Server inherited
On Tuesday, March 10, 2015 at 1:44:09 AM UTC+1, William Lasiewicz wrote: > > 3 questions. Thanks in advance for reading this and to whoever answers my > 3 questions. > > I am the release manager and we have perforce but we inherited a GIT > repository. > So far about 20 developers access this which is done through creating a > ssh key and then adding that key on the machine where we have git. > Everyone logs in through the same user "git". Everything is at Git\home, > which contains about 25 .git directories. > Telling who checked in files is on the honor system. > As far as I can tell, setting up a git user is done by adding a user to > the machine. > Is this really how this is done for this? > The first thing I want to do is give everyone their own user name so code > access could be restricted to the areas that are needed. Is this something > not done in GIT? > > I think you're better off looking at Git as a protocol or format, rather than a hosting tool. There are many hosting tools that support, or are built around Git, someone already mentioned Gitolite to you in another thread, but there are also more "enterprisey" solutions like GitLab, GitHub Enterprise, Atlassian Stash and so on, if you want to pay for more features and support. > So far I can't come up with a reason why you would use this instead of a > real tool, but we don't have perforce licenses to add for all these people > and the bosses want me to look in to taking our perforce which has > substantial automation in builds and deploys and converting it to this tool > which looks to be as sophisticated as the old file based stuff that was > used 15 years ago. > What could be benefited from using this? > If you're asking about the benefits of Git, well, it depends on what you need from your SCM. Git's main strengths are performance (for small/medium sized repositories at least), it is distributed, it's very adaptable and versatile (can fit all kinds of branching strategies and release processes), and it has a huge user-base in the programming industry, being undoubtably the most used VCS in open source. -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
