|
Well, for my private installation (just me and a handful of machines) I'm still using VSS with VS2008 and it's been fine but, yeah, in an environment with multiple developers I'd definitely go with TFS.
|
|
|
|
|
How many developers ?
What target technology ?
How many location (including writing tickets, reading tickets, development, testing, etc...) ?
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus
Entropy isn't what it used to.
|
|
|
|
|
We're a very small shop with an IT department that just shrunk to below ten people, but the number of people that should be able to write tickets counts in thousands.
We're exclusively doing Visual Studio for the foreseeable future.
|
|
|
|
|
Jörgen Andersson wrote: We're exclusively doing Visual Studio for the foreseeable future.
TFS (sixthed?)
|
|
|
|
|
We use JIRA and SubVersion; and will be soon using the Crucible (codereview) and FishEye (code tracking) JIRA plugins.
I'd rather be phishing!
|
|
|
|
|
Are you happy with Jira? Any specific gotchas?
|
|
|
|
|
The switch was made a couple of weeks ago; we used an in-house system (MS Groove workspace) and had a good process workflow that we were not able to completely reproduce with JIRA, mostly because of different mentality.
JIRA is working nicely for end-users; logging work and adding comments is simple and straightforward , and our manager (a good one) is happy with all the reporting and management tools.
One thing is that by default, JIRA will sent TONS of emails; so you have to configure it properly (system and per user).
we are about to integrate Crucible for code review, I did not try it yet, so I cannot comment about that
I'd rather be phishing!
|
|
|
|
|
Really depends on the team, their size and skill-set, the project, etc. Recently I decided to go with SVN for a project, mainly because I need both *Nix and Win support and nobody else where I work has *Nix experience, and I'm not using VS to develop it. Once git gets better Windows support I'll switch over to that.
If I were in a large corporate environment again, with a bunch of MS devs using VS, I'd be tempted to stay with TFS. That unless until MS increases their git support in VS too, in which case TFS goes bye bye along with SVN.
Jeremy Falcon
|
|
|
|
|
Jeremy, TFS includes Git based version control. I have just discovered this at my new position, where TFS seems the de facto, but I was very pleased to learn that this still boils down to Git.
No object is so beautiful that, under certain conditions, it will not look ugly. - Oscar Wilde
|
|
|
|
|
That's cool to know. I still haven't dove deep into how MS is using git yet, but I'm digging it.
Jeremy Falcon
|
|
|
|
|
I was 'blissfully' ignorant of so much until I started the new job last Monday. Suddenly everything is cloud. TFS, Visual Studio Online, and Azure. The only 'local' servers my work has come close to are the domain and Exchange.
No object is so beautiful that, under certain conditions, it will not look ugly. - Oscar Wilde
|
|
|
|
|
Interesting, mail is usually the first thing to be outsourced otherwise.
|
|
|
|
|
|
That's a good enough reason for many companies.
|
|
|
|
|
|
Those people should stop using Visual Studio as well.
|
|
|
|
|
Collin Jasnoch wrote: But I have heard attempted arguments against TFS
And what would the argument for it be?
I have used a variety of systems and have never found one that I thought was either great or horrible.
Although I will say that git is useless when multiple deliverables with interdependencies are needed.
|
|
|
|
|
|
Collin Jasnoch wrote: By that I mean the argument for it depends on the business model
I don't understand that statement.
I have experience in a wide swath of environments including very large to very small companies, different process models and different industries.
So is there a specific example of some business model and a specific feature of this tool that you can specify and tie together.
|
|
|
|
|
Anything but TFS. It's not bad, it's just very lackluster.
|
|
|
|
|
Would you mind expanding that?
|
|
|
|
|
TFS has basic issue tracking, but configuring fields and changing allowed statuses requires exporting xml, editing it and importing it.
Each project has a template for how issues are tracked, but changing templates midstream can be a pain, and some features aren't available for all templates. Upgrading major versions of TFS can be a pain, and synchronizing the 5 databases to get clean backups requires a custom script.
The source control portion is better now, and you don't have always be connected to the TFS server without it complaining. However, TFS is lacking things like being able to search for commit messages. The file search will only search by file name not file content.
Branching and merging work just like other systems and I haven't had any issues with any of the basic operations. However, it can support something like a 20 server configuration with multiple database servers, web servers, sharepoint servers, and custom source proxy servers for handling remote offices, so it can definitely scale up to handle something as huge as the windows codebase.
|
|
|
|
|
Thanks!
|
|
|
|
|
Andy Brummer wrote: However, TFS is lacking things like being able to search for commit messages.
WAIT WHAT THE SHEEP? Just... can't?
Now, I'm sure you could open the relevant DB and fire a query at it 
|
|
|
|
|
There are plugins that do that now, but the early recommendation was to export all the comments to a text file and then search the file.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
