Click here to Skip to main content
15,886,258 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
All,
I find myself today, thanks to Covid-19, in a small development group (4 max but currently 2 as someone put there notice in and a guy retired) without Source Control of any kind. (Zip/Nada/Nothing)

They have a mainframe that is basically on its way out by 2022. Also Web (Asp.NET forms with light JQuery) and a fairly rich Windows Form development Set (majority of source).

I got current management to flip the bill for Source Control (assuming its realistic) as there has been more then a few situations where the latest source code for a project was not known. Currently the source files are spread across servers and personal machines. :(

My goal is to set up a repository location where all our code can be quickly pulled by any developer working at our location. Regardless of who "owns" the project and whether they are with the company or not any longer. Also I would like to have a standard set of history of file changes. I do not see much Branching occurring as most projects are owned by an individual. There is no DEV, STAGE, Production environments setup currently...but who knows down the road (I can only hope). Also many projects probably only get updated a few times a year at max (mature). There are some projects though that are active with weekly changes but its limited currently probably to less than 10.

So what are the advantages of each of the Remote Repository (GITHub/Azure Devops)?

If you were in my situation what would you suggest for source control?

I am not sure if the CI/CD integration is something to even consider at this point but I am sure its probably something to talk about/consider in any decision but lets get Source Control setup first.

Thanks for the help,
Chris

What I have tried:

All,
Over the years I have used Rational Clearcase, Source Safe, TFS, and also while at Microsoft (7 years) a tool called Source Depot.

My previous employer, prior to my current, was going from TFS (slightly outdated) to Azure DevOps (GIT). The big hold up was getting our TFS history over to SQL 2019 which was part of a much larger project/plan/upgrade by Corporate. Not to mention a changing of the guard (Manager) did not help.

Anyways it appears from my previous experience and my research GIT is now the tool of choice. We are Visual Studio 2019 centric so integration with VS2019 is required. The cloud storage option (i.e. GitHub/Remote Repository) is approved assuming its private/secured by management.

So I began playing with GIT along with GITHub and a few small projects of mine but upon integrating with VS 2019 I saw that Azure DevOps (Microsoft) is a possibility as well. GIT and GitHub seemed to be simple enough but keep in mind my colleagues have never used source control before at all.

I have to be honest my experience with my new employer has been pleasant as its definitely slower pace then any of my previous employers in the past 24 years. I know Covid-19 has had some impact but looking over the environment its not Microsoft or my last employer at all but I would like to get them setup correctly.
Posted
Updated 11-Feb-21 6:53am
Comments
Maciej Los 11-Feb-21 12:47pm    
VS 2019 + GitHub is the best option - in my opinion.
BTW: what's the question?

1 solution

Being a Dutch cheapskate I set up our builder and GIT server mostly with free tools
(with the exception of Dotfuscator which is paid)
All on Windows and we are building locally mostly .NET projects.

The GIT server is Gitea[^]
The builder is TeamCity[^]
Database for Gitea and TeamCity: PostgreSQL[^]

As TeamCity has a learning curve (as most CI tools) you could also consider starting with Gitea only and see if that meets your demands.
 
Share this answer
 
v2
Comments
Cmgray74 11-Feb-21 13:23pm    
I was wondering if there was a local <your in="" house=""> server version or Free option. I know GitHub has a local <your in="" house=""> server version as well but it costs.

Not sure if I can sell them on the Gitea, even though to me seems like a reasonable choice, but I will mention it for sure.

Thanks
Chris
RickZeeland 11-Feb-21 13:29pm    
We have Gitea running for 2 years now on a virtual machine without problems.
GitHub has the option of private repositories, but that could be a paid option.
If you are used to GitHub you will find Gitea easy, as the interface is almost the same.
F-ES Sitecore 12-Feb-21 4:54am    
You can run your own git server in-house, you don't need to use external repositories.
Cmgray74 11-Feb-21 13:36pm    
RickZeeland,
Another thing is their databases/database servers are in similar states. All that I have seen are MSSQL(6 -> different versions). Is the GITea databases easily upgradeable/portable/migratable? I could see this being a problem now or in future.
RickZeeland 11-Feb-21 13:40pm    
Gitea supports SQL Server, but I have only used it with PostgreSQL.
More info here: https://docs.gitea.io/en-us/database-prep/

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900