Development and Deployment Procedures

[DominionZA]

Been working with Git lately. What a terrible, fiddly experience. So much less user friendly than something like Subversion or CVS.

I felt the same when I moved to GIT from SVN.
You got to stop thinking SVN and think GIT. It is seriously powerful - and when you grasp it - super easy. GIT revolutionised merge and branch management IMO.

It must be a familiarity thing then, I went from subversion to git and there was a bit of a learning curve but now I wouldn't give it up

+1

 

[Hamster]

Been working with Git lately. What a terrible, fiddly experience. So much less user friendly than something like Subversion or CVS.

I used Mercurial through the command line and it was super easy. Then I switched a team from TFS to Git and the command line sucks

But, using it with SourceTree or Git Extensions makes it very easy. From a source management perspective it is the best I've used especially if you run it on Stash which gives you pull requests and branch permissions.

I've had it twice now where a team is switch from a file based (if I can it that) source control system like SVN to a DSCS. At first they bitch and moan at me, then they go quiet and after a month or two they all/most say "hey, I can't believe we ever worked without it".

TFS and SVN belong in the dark ages imo

 

[patrict]

+1 for sourcetree, unless you need to do something complex, where git command line wins

 

[DominionZA]

Have yet to do anything GIT wise via the command line. Find Sourcetree and the MS GIT Provider in VS does the job very well.

 

[Hamster]

Only problem we find with SourceTree is that it can become sluggish when dealing with large and very busy repos.

GitExtensions is better imo, very powerful, written for power users...but not as user friendly as SourceTree

There is another alternative - SmartGit. Haven't played with it too much but looks pretty good.

 

[DominionZA]

TortoiseGIT too. Handy if you're used to TortoiseSVN.
We only use it for very old projects that are still limping along in VS2010.

Gonna have a look at GitExtensions.

 

[semaphore]

Smartgit is terrible i've used it for a while, it also becomes slow. Now i just use command line.

 

[_kabal_]

I use tortiosegit for view log, and Cygwin + git Cli for everything else.

Ditched STS for intellij about a month ago. can't believe I didn't do this years ago. eclipse does some things better, especially around standard hot swop, but now with jrebel, intellij does more better. The biggest improvement is speed. Probably save around 20 minutes a day from no more eclipse mini pauses

 

[Hamster]

TortoiseGIT too. Handy if you're used to TortoiseSVN.
We only use it for very old projects that are still limping along in VS2010.

Gonna have a look at GitExtensions.

I can't remember how good TortoiseSVN was, but compared to TortoiseHg - which was excellent - TortoiseGit sucks.

 

[Hamster]

Smartgit is terrible i've used it for a while, it also becomes slow. Now i just use command line.

It did seem nice for large merges, but i the that you have to open the log in a new window. Eventually it might be worth learning the command line :/

 

[semaphore]

It did seem nice for large merges, but i the that you have to open the log in a new window. Eventually it might be worth learning the command line :/

Our repository is 11gb. This thing crawls on SSDs

 

[Hamster]

Our repository is 11gb. This thing crawls on SSDs

Probably written in java :twisted:

Do you use command line exclusively or have a GUI tool to help our now and again when things get rough?

 

[semaphore]

Probably written in java :twisted:

Do you use command line exclusively or have a GUI tool to help our now and again when things get rough?

Command line only, biggest pain, but not as much as waiting for smartgit to refresh after 10mins. But we very rarely have severe merge conflicts.

Is is written in java, but sourcetree is worse. Wpf ****

 

[sp4ceman]

we are a dotnet house.

subversion is our source control control. team city does our testing and building and deployments.