GIT in a corporate environment ?

[rrh]

Whilst most of our development is centralised, one of our larger developments includes a couple of overseas contractors developing in VS2010 / C#.

As a result - mainly in order to simplify branching/merging - it has been proposed that we switch from Subversion to GIT.

Being somewhat anal I am concerned that this might affect our unit testing / continuous integration, but am unable to obtain clear answers.

Any comments about deploying GIT in a corporate environment would be appreciated.

 

[roguemat]

What about TFS? (I have not had much experience with GIT)

 

[walter_l]

We have recently migrated from Subversion to Mercurial. It presented quite a learning curve to people unfamiliar with DVCSs, but now (5 months later) most seem to have gotten the hang of it. Mercurial was selected over git because of a slightly less steep learning curve and the more mature GUI tools available.

The only effect on continuous integration that I can think of, is whether or not your continuous integration system supports the proposed VCS.

 

[rrh]

What about TFS? (I have not had much experience with GIT)

TFS is a centralised system, like Subversion.

The actual query is more related to centralised vs. distributed version control.

 

[rrh]

We have recently migrated from Subversion to Mercurial. It presented quite a learning curve to people unfamiliar with DVCSs, but now (5 months later) most seem to have gotten the hang of it. Mercurial was selected over git because of a slightly less steep learning curve and the more mature GUI tools available.

The only effect on continuous integration that I can think of, is whether or not your continuous integration system supports the proposed VCS.

I hear good things about Mercurial: that said, Git appears (as Eric Sink says) 'more interesting' so Mercurial is largely ignored in the dust storm

The advantage of continuous integration is that - each time code is checked in - the CI system (e.g. CruiseControl) checks out all code, performs a rebuild, performs all unit tests and then deploys.

With a distributed system isn't it a little tricky in enforcing check-ins - and thus builds / deploys ?

 

[Other Pineapple Smurf]

We are in the process of migrating to GIT from subversion. No issues and GIT is a big improvement - we use hosted GIT Hub.

 

[rrh]

We are in the process of migrating to GIT from subversion. No issues and GIT is a big improvement - we use hosted GIT Hub.

How are you handling continuous integration ?

 

[Other Pineapple Smurf]

How are you handling continuous integration ?

We are all use to version control so no issues with the migration, then again we all work in the same office so no lcak of communication.

 

[rrh]

OK, am I correct that you aren't using CruiseControl / TeamCity / Hudson (or similar) to perform continuous integration testing ?

 

[Other Pineapple Smurf]

OK, am I correct that you aren't using CruiseControl / TeamCity / Hudson (or similar) to perform continuous integration testing ?

Nope, we use Linux and test driven development.

 

[kooldude]

Hi, I would suggest Mercurial if you are on windows environment. But setting up a central server to push your changes is little bit tricky with IIS and python.

How are you handling continuous integration ?

You can have Mercurial working fine with TeamCity / CruiseControl. Never tried Hudson.

 

[rrh]

Hi, I would suggest Mercurial if you are on windows environment. But setting up a central server to push your changes is little bit tricky with IIS and python.


You can have Mercurial working fine with TeamCity / CruiseControl. Never tried Hudson.

Thanks for the update - that's good to hear.

I guess that is all a matter of discipline: we will just have to make sure that the off-site developers commit their changes to a local box on a daily basis so that we can continue to perform our daily builds.