Hello we are deciding at our project to move from Teamcity to TFS 2018 but we are not sure if its best idea. I was reading a lot comparison but they are pretty old 2 years is in programming world really lot. We like about tfs 2018 that it support it own nugget server it has own version control technicaly you can have everything at one place. Can you please give some pros and cons of both?
You can refer to this article to Compare TeamCity Vs. Team Foundation Server
About the vendors - JetBrains Vs. Microsoft
JetBrains: JetBrains, creator of the best Java IDE - IntelliJ IDEA - is a technology-leading software development firm specializing in the creation of intelligent development.At JetBrains, we have a
passion for making people more productive through smart software
solutions that help them focus more on what they really want to
accomplish, and less on mundane, repetitive "computer busy work".
Microsoft: Microsoft Corporation is an American corporation that develops, manufactures, licenses and supports a wide range of products
and services related to computing. The company was founded by Bill
Gates and Paul Allen on April 4, 1975. Microsoft is the world's
largest software maker measured by revenues.
Compare Pricing - TeamCity Vs. Team Foundation Server
TeamCity Starting from $299 Per license, Team Foundation Server
Starting from $20 Per month/user. .
Compare Features and Functionality
As with any business software solutions, it’s important to consider
features & functionality. The tool should support the processes,
workflows, reports and needs that matter to your team. To help you
evaluate this, we've compared TeamCity Vs. Team Foundation Server
based on some of the most important and required Enterprise
Integration features.
TeamCity: Data Import/Export, Basic Reports, Online Customer Support.
Team Foundation Server list of features include the following: Data Import/Export, Basic Reports, Online Customer Support,
Mobile Friendly / Cloud
TeamCity: their software can be used in the following: Standalone, On Premise while Team Foundation Server can be used with: Standalone,
Cloud, SaaS
Which Software is Better? TeamCity or Team Foundation Server?
Which solution is better? TeamCity or Team Foundation Server? As
usual, the question is not “Which software is better?” but “Which
software is right for your needs and budget?”. Neither of these two
Enterprise Integration software is necessarily “better” than the
other. Both offer industry-leading features and a scalable platform,
as well as the ability to custom-build a unique solution with optional
modules. If you would like to get quotes or having trouble deciding
which Enterprise Integration is the right for you, we’d love to help.
Fill out the forms in this page to get demos, free quotes and a custom
software recommendation.
Besides, you can integrate TeamCity with Team Foundation Server as needed to combine their advantages.
Without installing additional software, TeamCity servers and build
agents can interact with Team Foundation Servers (from 2010 to 2017;
2018 is supported since TeamCity 2017.2) and Visual Studio Team
Services.
Please refer to below articles to know more about that:
Cross-Platform TFS Integration
Integrating TeamCity with Team Foundation Server
Related
We're in the middle of migrating code, builds etc from an old TFS 2015 instance to a new TFS 2017 instance. So currently we have 2 TFS on premise instances. The migration is likely to take 6 - 12 months due to time constraints on resources.
One question we haven't been able to find a clear answer to is how the CAL licensing would work in this situation. We have users with MSDN licenses which gives a TFS CAL and also users with Test Pro licenses which also provides a CAL. But do those CAL's cover the user using both instances during the 6 - 12 months while we complete the migration?
To license TFS 2015/2017, you’ll need a TFS server license and a
Windows operating system license (Windows Server is best) for each
machine running TFS, plus a client access license for each person
connecting to TFS. Client access licenses (CALs) aren’t required for
people who just access work items – assign them “Stakeholder” access,
which is free.
Extensions to TFS such as Test Manager, Package Management, and
Private Pipelines require an additional purchase. Some TFS Extensions
are included with Visual Studio Enterprise subscriptions and many
others are free. Paid extensions can also be purchased monthly, no
Visual Studio subscription is required.
In your case, for every MSDN subscription that you own, you also have a TFS server licenses. So, theoretically, you could install as many TFS servers as you have MSDN subscriptions. I am not a licensing expert, but according to TFS Licensing Whitepaper appears to say nothing about tying a user CAL to a particular TFS server installation.
You could take a look at Daniel - the real one's question and Brian Harry MS's reply in this thread-- Included CALs and Tiered Pricing which has a similar situation like you.
Besides, If you want to double confirm this and know more information about TFS license, you could call 1-800-426-9400, Monday through Friday, 6:00 A.M. to 6:00 P.M. (Pacific Time) to speak directly to a Microsoft licensing specialist, and you can get more detail information from there. Worldwide customers can use the Guide to Worldwide Microsoft Licensing Sites to find contact information in their locations: http://www.microsoft.com/licensing/
In a Devops context, Who is the responsible for the automation tasks ?
more exactly in the case of "pipeline as a code" in jenkins . who is supposed to do this task ? the devoloper or the operator ?
who is the actor ?
"The key to DevOps is greater collaboration between engineering and operations."
Roles : DEVOPS
Responsibilities :
1. Management : The DevOps Engineer ensures compliance to standards by monitoring the enterprise software and online websites. The engineer also regulates tools and processes in the engineering department and catalyses their simultaneous enhancement and evolution.
2 Design and Development : Design and Development of enterprise infrastructure and its architecture is one of the major responsibilities that DevOps Engineers are tasked with. Such Engineers are highly skilled coders which enable them to script tools aimed at enhancing developer productivity.
3 Collaboration and Support : The DevOps’ Modus Operandi is to collaborate extensively and yield results in all aspects of their work. Everything ranging from technical analyses to deployment and monitoring is handled, with the focus to enhance overall system reliability and scalability. The diagram below gives one a clear picture of the values that define DevOps.
4 Knowledge : DevOps staff and Engineers aid in promotion of knowledge sharing and overall DevOps culture throughout the engineering department
5 Versatile Duties : DevOps staff and Engineers also take on work delegated by IT director, CTO, DevOps head and more. They will also perform similar duties to the designations mentioned above.
Standard Definition :
DevOps is an IT mindset that encourages communication, collaboration, integration and automation among software developers and IT operations in order to improve the speed and quality of delivering software.
Layman's Definition :
Any kind of automation that enables the opportunity for smoother Development, Operations, Support and delivery of the product is DevOps.
Indrustry's View :
There usually are two prominent area's where DevOps mindset is applied across industry :
a) Primary functionaries of DevOps like
• Continuous Integration,
• Continuous Delivery,
• Continuous Deployment,
• Infrastructure as an code or infrastructure Automation,
• CI/CD Pipeline Orchestration,
• Configuration Management and
• Cloud Management (AWS, Azure or GCP)
b) Secondary functionaries of DevOps like
• SCM tool Support,
• Code Quality tech support like Sonar, Veracode, Nexus etc.
• Middleware tech support for tools like NPM, Kafka, Redis, NGIMX, API Gateway, etc
• Infrastructure tech support for components like F5, DNS, Web Servers, Build Server Management etc
• OS Level support for miscellaneous activities lke Server Patching, Scripting for automation of server level tasks etc.
There is no exact answer to this. It depends on many factors.
The development team will most likely want more ownership over the pipeline, and therefore would want to own the templates / code required to achieve the end goal of automation.
The opposite side of this is also completely valid. An operations team could be the custodians of a pipeline and mandate a development team must meet certain standards and use their automation pipelines to be able to get into an environment or onto a platform.
If an environment is an island, and development teams are trying to get to that island. Each development team can build their own bridge to get there. Or the operations team can build a bridge and ask the development teams to use it. Both are valid and the end result is the same either way.
If the end result is the same, then the only thing that matters is how you apply it in the context of the organization, team(s) and the people you are working with to achieve that common goal.
The assigned developer (and scrum team) should be responsible for the complete delivery of all aspects of development through final deployment into production. This fosters the notions of ownership and empowerment, and focuses responsibility for the full life cycle delivery of the service (application).
DevOps engineering should be responsible for providing an optimal tool chain and environments for rapid and quality delivery. I see DevOps role as the development focused precedent to SRE. If SRE's maintain high performance, stable production environments, then DevOps team maintains optimal development and testing environments. In theory, DevOps should extend into the realm of SRE, conforming into a single team supporting the environments for rapid innovation with quality to meet the business needs.
Everything from committing of the code to production. This includes
Automation
Production Support
Writing automation scripts
Debugging Production Infrastructure
In short Devops = Infrastructure + Automation + Support
As stated in the title, my agency (also whole software department of my company) still use Visual SourceSafe 2005 as Version Control System.
My company is a hardware manufacturer for over 5 decades, and software development have started for nearly 2 decades. Just only my agency there are 30 developers, and the head office have even more devs. My agency VSS database is around 133 GB and the head office is more than 200 GB.
I've also skimmed through Google:
How do I convince my team to drop sourcesafe and move to SVN?
How to convince a company to switch their Source Control
Visual SourceSafe: Microsoft's Source Destruction System
Source Control: Anything But SourceSafe
etc.
I also know that extended support of VSS will end at July 11 2017. I also verified many things listed in the articles (lack of atomic checkins, poor branching/merging, binary files trouble, slow history, etc.). For example, I just status search through whole agency database (I can't check HQ since permissions):
55 "File names.dat maybe corrupt. Ask your SourceSafe administrator to run Analyse utility on this database."
5 "Error reading files."
1 "VSS/data/terqeaaa.b not found."
Is the situation of database bad? If it's right, then, how can I convince them to switch to other VCS? I need some reliable recently information and some evidence. The guide how to show/proof them is better.
I asked the admin to run Analyze but he ignored my words since I just started to work for a few months. People can see VSS basic weakness. They also complain "who check out this file?" and resolve conflicts by barehands. They have to use WinMerge to diff and compare, Get latest version instead of branching and checking out, never comment orsee history log, create entire new folder for new code, etc. However, they do not give up on SourceSafe. (They are using Visual Studio 2012 to develop and didn't notice Team Foundation Server).
I think you already summed up many of the reasons:
VSS is already in extended support and is only kept secure, but barely functioning. It's on life support in the palliative care ward. Extended support, in the real world means unsupported. Unless you have a very strong credit limit, Microsoft will not help you if it turns out you need the support.
VSS officially supports only the following operating systems, none of which are currently supported anymore:
Windows XP, Windows 2000, Windows NT 4.0 with SP6 or later, Windows Server 2003.
It hasn't has any improvements, fixes since 2008.
The Visual Studio and TFS documentation have been advocating the migration to TFS since 2008. There has been a full migration tool since 2012.
It has known issues with stability, internal consistency and corruption. A conscience administrator will need to spend regular time to ensure internal stability and consistency.
It doesn't support modern development workflows (transactional commits, distributed version control, modern branch/merge, cherry picking, optimistic locking etc).
It has a very limited security capacity, users with access to the share can simply grab the whole file share and force access.
It's not useful for remote access. Or at least requires VPN and a stable, very fast network connection. Even then it'll likely increase the chance for corruption.
The user experience in Visual Studio and other tools that directly support TFVC or Git is much, much better.
Cross platform support is non-existent. In the current market this is becoming more and more important.
The standard backup (archive) tool built-into the product has a limit of 2GB repositories.
Microsoft recommends at least weekly analysis of the sourcesafe database and recommends the logs and backups of the repo to be kept so corruptions can be manually be put back together by copying files from the backup back to the active share.
There is a supported migration path from VSS to TFS.
A migration to TFS brings more, ability for Continuous Integration, Release Management, Work Management (Agile tooling, backlogs), Test Management on top of a much more stable, performant and secure backend that makes use of the qualities of SQL Server for robustness, integrity and security.
I am interested in evaluating team foundation server and I have downloaded the 2010 trial and ready to install on my server. As part of the evaluation my boss has asked me to have a good idea of the final cost if we decided to use TFS. I have 2 questions in this post really.
What components do I need to purchase to be able to use TFS and currently how much do they cost? We have 3-4 developers who would need to use TFS. At the minute one of them is using Visual Studio 2010 Professional.
After looking around I noticed that TFS11 Express has just launched which looks to be free for upto 5 developers. Is this a viable option for us to use?
I would say the main thing we are looking for is source control.
Kind Regards
Ash
You'll find licensing information at this page.
Yes TFS Express will be a totally viable option for your team, if all you need is Source Control, some Work Item and some Continuous Integration. This edition is made for small teams such as yours and you wouldn't have to pay for a CAL.
As you have less than 5 developers and just looking for Source Control. Team Foundation Express will be viable option.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
I'm currently developing a web app on Django/Python, and I consider moving to ASP.NET MVC. I downloaded the Visual Web Developer Express edition, read NerdDinner, and I'm ready to go. I will probably keep working on MySQL.
One of the reasons I chose Django+MySQL in the first place was that it was free of charge. I'm bootstrapping a business and can't afford to pay for expensive software, even for deployment (storage and bandwidth are the exception).
My question is: can I develop on the express edition and get my product to production without having to pay to Microsoft? This is both a legal question and a practicality question (Assume I'll use open source version control, build server, etc).
I'm not experienced in Microsoft's different licenses, I wondered if anyone has any experience in driving a product to the web based solely on the express editions (I know you guys are not lawyers, but some of you are probably working at companies paying lawyers to help with such decisions...)
You've asked two questions here, so let's take a look at both.
From a legal standpoint the answer is pretty straightforward: yes, Visual Web Developer Express is provided free of charge and there is no limitation regarding using it commercially.
Your second question has to do with the practicality of using Express editions commercially. The short answer is: yes. The longer version of the answer sounds a little more like "yes, but...".
Although Visual Studio Express editions are fantastic -- especially when you consider their price -- you should be aware that they do lack functionality. To me, the most important things Express editions lack are --
Extension support. There's a healthy Visual Studio add-in ecosystem out there that you'll be locked out of. Not a fatal flaw, for sure. Just something to keep in mind.
Ability to create setup projects. Again, not fatal. You can do it manually or using some external solution. Also, if you are developing something for use on one customer (or for yourself) this is a complete non-issue.
Native 64-bit support. This is the one I can't work around. If you need to work on 64-bit environments and use some 64-bits controls, you're in a pickle.
Support for test projects. If you are into test-driven development, this is a very cool feature you'll miss on the Express editions.
Also, they have no class designer, some (small) limitations on debugging and most development tools you'll find that work with Visual Studio won't work with the Express editions.
All in all, you can definitely develop with VS Express. Compared to the tools you probably had for Django+Python, Visual Studio Express is a big leap forward anyway IMHO.
Also, you can always go with the Express edition for now and upgrade later if necessary.
Point 7 in the "Express" FAQ probably answers it best:
Can I use Express Editions for commercial use?
Yes, there are no licensing restrictions for applications built using Visual Studio Express Editions.
Other then that, reading the EULA should confirm that there is no "products built with this software is for private use only" clauses.
Not only can you develop ASP.NET MVC for free, you can do it on Linux using Mono, as Miguel points out and Michael explains... so in addition to no license fees for the runtime or IDE, you can host on free operating systems too!
You can also use MonoDevelop on Mac OS-X and although I'm pretty sure Windows users will prefer Visual Web Developer Express, they are getting MonoDevelop running on Windows, too.
When you've made your first million dollars, then you can 'upgrade' to Visual Studio 2010 :)
Yes, the Express editions are really free.
yes, you can develop on the free versions of microsoft software. you will have to pay for the os license of the development and hosting servers though.
for a business you may want to investigate the bizspark program which can give you up to three years of everything, including hosting.
It is absolutely possible to develop and deploy ASP.NET and ASP.NET MVC applications without having to pay to Microsoft. I see no any limitations/differences (both legal and practical) in deployment of ASP.NET applications, developed in express/full versions of VS. Personally I would recommend to buy VS2008 Pro (or maybe wait for VS2010) - it's much more powerful then VWD Express. Yes, It is expensive but I think it is worth its money.
UPDATED:
Reliable Dedicated/VPS hosting is expensive for both Linux/Windows platforms. So if your site will grow quickly - yor main costs will be hosting not tools
in development yes it is free visual studio express is really free but when it comes to deployment you will really need Windows server 2003 or 2008 you might also need another edition of SQL server if express doesn't meet the requirement :)
There is no need to settle for the Express editions or open source. If you are a legitimate startup, you can join Microsoft's relatively new BizSpark program and get a free MSDN subscription, which includes full editions of all the software for development purposes (e.g. Windows Server, SQL Server, etc).
Plus for web apps you get licenses to deploy the software in production, which I think makes BizSpark unique versus other MS partner programs. It doesn't include free hosting however.
Check out the site for eligibility requirements and restrictions.
(sorry Matt I know you mentioned Bizspark, but I wanted to provide more info and emphasize how relevant this is for the question).