User talk:MikeL MSFT

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Proposing changes[edit]

Hi Mike, If you wish to propose changes to an article then copying the whole (modified) article (complete with category tags, maintenance tags etc) onto the talk page isn't the way to do it. It would be better to explain (on the talk page) what change you think should be made - e.g. "The first paragraph in <section> is out of date - the following would be better ...". Another option is copying the article to a separate page (a sandbox) as a subpage of your userpage or a subpage of the article talk page, making the edits there (and comment out category/stub tags) and then add a notice on the article's talk page pointing to the sandbox. DexDor (talk) 06:32, 15 April 2016 (UTC)[reply]

Requesting Edit / addition of Release Management to Deployment tools section[edit]

Hi my name is Micheal Learned and I am a content developer at Microsoft. I am submitting an addition this page for the Deployment Tool section for our deployment tool Visual Studio Release Management.

Thank you very much!

Deployment tools[edit]

MikeL MSFT (talk) 16:23, 26 April 2016 (UTC)[reply]

Requesting edits to Proprietary section[edit]

Hi my name is Micheal Learned and I am a content developer at Microsoft. I am submitting an addition to this page for the "Proprietary section" for our list of version control software. I added Visual Studio Team Services right after Team Foundation Server.

Thank you very much!

Proprietary[edit]

MikeL MSFT (talk) 17:45, 27 April 2016 (UTC)[reply]

Requesting edits to the Future and External Links sections[edit]

Hi my name is Micheal Learned and I am a content developer at Microsoft. I am submitting an addition to this page for the Future and External Links sections for our Distributed version control. The Future section will have a short sentence with links. In the External Links section inside the navbox, I have added new links under the Client-server and Distributed groups.

Thank you very much!

MikeL MSFT (talk) 12:35, 28 April 2016 (UTC)[reply]


Future[edit]

Some originally centralized systems now offer some distributed features. For example, Subversion is able to do many operations with no network.[1] Team Foundation Server and Visual Studio Team Services now host centralized and distributed version control reposotories via hosting Git.

External links[edit]





Requesting edits to the Template for Version Control Software[edit]

Hi my name is Micheal Learned and I am a content developer at Microsoft. I am submitting an addition to this page for the Template (Version Control Software) for our Revision Control System page. I have added links and current dates for Team Foundation Server and Visual Studio Team Service under the client-server and distributed group's.

Thank you very much!

MikeL MSFT (talk) 14:39, 28 April 2016 (UTC)[reply]






Requesting edits to Continuous Integration Tools[edit]

Hi my name is Micheal Learned and I am a content developer at Microsoft. I am submitting an addition to this page for the Continuous Integration Tools section for our List of build automation software. I changed the description for Team Foundation Server and added Visual Studio Team Services as a link with description just below Team Foundation Server.

Thank you very much!


Continuous integration tools[edit]

  • AnthillPro, build automation with pipeline support for deployment automation and testing. Cross-platform, cross-language
  • Bamboo, continuous integration software
  • Apache Continuum
  • Buildbot, a Python-based software development continuous integration tool which automates the compile/test cycle
  • BuildIT, a free graphical build or task tool for Windows with an emphasis on simplicity and ease of use
  • Buildout, a Python-based build system for creating, assembling and deploying applications from multiple parts
  • CABIE Continuous Automated Build and Integration Environment, open source, written in Perl
  • CircleCI
  • CruiseControl, for Java and .NET
  • GitLab CI
  • DeployBot, a hosted continuous integration service
  • Hudson, an extensible continuous integration engine
  • Jenkins, an extensible continuous integration engine, forked from Hudson
  • Sanelotto, a Python-based extensible continuous integration tool
  • Team Foundation Server, a cross platform continuous integration engine from Microsoft
  • Visual Studio Team Services, provides Azure hosted build capabilities.
  • TeamCity
  • Travis CI, a hosted continuous integration service

MikeL MSFT (talk) 17:55, 28 April 2016 (UTC)[reply]

Requesting edits to General information and Features sections[edit]

Hi my name is Micheal Learned and I am a content developer at Microsoft. I am submitting an addition to this page for the General information and Features sections for our Source code hosting facilities. I have added a row for Team Foundation Server and changed Visual Studio Online to Visual Studio Team Services to the general information and features section of this page.

Thank you very much!

MikeL MSFT (talk) 17:07, 2 May 2016 (UTC)[reply]

Overview[edit]

General information[edit]

Name Manager Established Server side: all free software Client side: all-free JS code Developed and/or used CDE Require free software on registration Ad-free Cost Notes
Alioth Debian Project 2003 Yes Yes FusionForge Un­known Yes Free Preference for Debian related projects
Assembla Assembla, Inc 2005 No Un­known Un­known No Yes 7-day free trial. Commercial projects with customizable sets of tools and features.
Betavine Vodafone 2007 No Un­known Un­known No No Free
Bitbucket Atlassian 2008 No No Un­known No Yes Free private repositories are limited to 5 users
CloudForge Collabnet 2000 No Un­known Un­known No Yes No
CodePlex Microsoft 2006-05 No Un­known Un­known No Yes Free Project must be OSS licensed
Freepository Un­known 1999 Yes No Un­known Un­known Yes Free accounts have web access only. Freepository is ceasing operations on 2016-05-01
GitHub GitHub, Inc 2008-04 No No Un­known No Yes Free for public, paid for private.
GitLab GitLab B.V. 2011-09[2] Yes Yes[3] GitLab Community Edition (CE) free software, GitLab Enterprise Edition (EE) proprietary No Yes Unlimited public and private repos, unlimited public and private collaborators[4]
Gna! The Gna! people 2004-01 Yes Yes Savane Yes Yes Free Only for free software projects. Code access review[5]
GNU Savannah Savannah Administration 2001-01 Yes Yes Savane Yes Yes Free Project by the Free Software Foundation and projects with a GPL compatible license. Code access review[6]
JavaForge Intland Software 2005 No Yes Un­known No Yes Free For open-source projects only.
Launchpad Canonical Ltd. 2004 Yes No Launchpad No Yes Un­known Supports Bazaar for version-controlled repository hosting. Git support is in beta.[7]
OSDN OSDN K.K. 2002-04 Un­known Yes Un­known No No Free For open-source projects only.[8]
Ourproject.org Comunes Collective 2002 Yes No Un­known No Yes Free For free software, free culture and free knowledge projects.
OW2 Consortium OW2 Consortium Un­known Un­known No Un­known No Yes Un­known Oriented on middleware technology.
SEUL Un­known 1997-05 Un­known No Un­known No Yes Un­known
SourceForge BizX LLC 1999-11 Yes[9][10] Yes Apache Allura No No Free, commercial services are offered as well For open-source projects only.[11]
Blocked in Cuba, Iran, North Korea, Sudan, Syria[12]
Tigris.org (community) 2000 Un­known No Un­known No No Un­known Restricted to collaborative software development tools. Tigris.org is no longer accepting new project proposals.
Team Foundation Server Microsoft 2012-10[13] Un­known No Un­known No Yes Free version and paid commercial version available
Visual Studio Team Services Microsoft 2012 Un­known No Un­known No Yes Free private repositories are limited to 5 users
Name Manager Established Server side: all free software Client side: all-free JS code Developed and/or used CDE Require free software on registration Ad-free Cost Notes

Features[edit]

Name Code review Bug tracking Web hosting Wiki Translation system Shell server Mailing List Forum Personal branch Private branch Announce Build system Team Release Binaries Self-hosting
Alioth No Yes Yes No No Yes Yes Yes Yes Yes Yes No No Un­known Yes
Assembla Yes[14] Yes Yes Yes Yes No No No Yes Yes[15] Yes Yes Yes Un­known No
Bitbucket Yes[16] Yes[n 1] Yes[17] Yes No No No No Yes Yes[n 2] No No Yes Yes Commercially (Stash)[n 3]
CloudForge Un­known Yes Yes Yes No No No No Un­known Un­known Un­known Un­known Un­known Un­known No
CodePlex No Yes No Yes No No Yes Yes No No No No No Yes No
GitHub Yes[18] Yes[19][n 4] Yes Yes No No No No Yes Yes[n 5] Yes 3rd-party (e.g. Travis CI, Appveyor and others)[20] Yes Yes Commercially (GitHub Enterprise)
GitLab Yes[21] Yes Yes[22] Yes No No No No Yes Yes Yes Yes[23] Yes No Yes[n 6]
GNU Savannah Yes[24] Yes Yes No No Yes Yes No[25] No No Yes No Yes Un­known Yes
JavaForge Yes[26] Yes Yes Yes No No No Yes No No Yes Yes Yes Un­known No
java.net/Project Kenai Un­known Yes Yes Yes No No Yes Yes Yes Yes Yes Yes Yes Un­known No
Launchpad Yes Yes No No Yes No Yes No Yes Yes[n 7] Yes Yes[n 8] Yes Un­known Yes
OSDN Yes Yes Yes Yes No Yes Yes Yes Yes No Yes No Yes Yes No
Ourproject.org Un­known Yes Yes Yes No Un­known Yes Yes Un­known Un­known Un­known Un­known Un­known Un­known Yes
SourceForge Yes Yes Yes Yes No Yes Yes Yes Yes Yes Yes No Yes Yes Yes
tigris.org No Yes Yes Yes No No Yes Yes Yes Yes Yes No Un­known No longer for new projects[n 9] No
Team Foundation Server Yes Yes Yes Yes No No Yes Yes Yes Yes Yes Yes Yes Yes Yes
Visual Studio Team Services Yes Yes Yes Yes No No Yes Yes Yes Yes Yes Yes Yes Yes Yes
Name Code review Bug tracking Web hosting Wiki Translation system Shell server Mailing List Forum Personal branch Private branch Announce Build system Team Release Binaries Self-hosting

Requesting edits to the General Information section[edit]

Hi my name is Micheal Learned and I am a content developer at Microsoft. I am submitting an addition to this page for the General Information section for our version control software. I would like to change the links for Visual Studio Online to Visual Studio Team Services in the row for Team Foundation Server, located between SVK and Synergy.

Thank you very much!

MikeL MSFT (talk) 18:06, 2 May 2016 (UTC)[reply]

Team Foundation Server (TFS) Microsoft Active Client–server, Distributed Merge or lock Proprietary Windows, Cross-platform via Visual Studio Team Services Free for up to 5 users in the Visual Studio Team Services or for open source projects through codeplex.com; else non-free, licensed through MSDN subscription or direct buy.

Requesting edits to Team Foundation Server description[edit]

Hi my name is Micheal Learned and I am a content developer at Microsoft. I am submitting an addition to this page for the Team Foundation Server description section for our Team Foundation Server article. I added a link to the DevOps Wikipedia article.

Thank you very much!


Team Foundation Server (commonly abbreviated to TFS) is a Microsoft product that provides source code management (either via Team Foundation Version Control or Git), reporting, requirements management, project management (for both agile software development and waterfall teams), automated builds, lab management, testing and release management capabilities. It covers the entire application lifecycle, and enables DevOps capabilities.[27] TFS can be used as a back-end to numerous integrated development environments (IDEs) but is tailored for Microsoft Visual Studio and Eclipse on all platforms.[28]

MikeL MSFT (talk) 14:30, 4 May 2016 (UTC)[reply]

Requesting edits to the On-premises vs. online section[edit]

Hi my name is Micheal Learned and I am a content developer at Microsoft. I am submitting an addition to this page for the On-premises vs. Online section for our Team Foundation Server article. I removed a Wikipedia link and made some changes to text in the paragraph.

Thank you very much!


On-premises vs. online[edit]

Team Foundation Server is available in two different forms: on-premises and online. The latter form is called Visual Studio Team Services (formerly Visual Studio Online). The cloud service is backed by Microsoft’s cloud platform, Microsoft Azure. It uses the same code as the on-premises version of TFS, with minor modifications, and implements the most recent features. Visual Studio Team Services requires no setup. A user can sign in using a Microsoft account to set up an environment, create projects and add team members. New features developed in short development cycles are added to the cloud version first. These features migrate to the on-premises version as updates, at approximately three-month intervals.[29]


MikeL MSFT (talk) 14:41, 4 May 2016 (UTC)[reply]

Requesting edits to Team Build section[edit]

Hi my name is Micheal Learned and I am a content developer at Microsoft. I am submitting an addition to this page for the Team Build section for our Team Foundation Server article. I added some changes to text and restructured the bottom of the paragraph.

Thank you very much!


Team Build[edit]

(Prior to TFS 2015) Team Build is a build server application included with Team Foundation Server. Two components make up Team Build - MSBuild and Windows Workflow Foundation. MSBuild is a declarative XML language similar to Apache Ant. WF was added to the build process starting with TFS 2010, prior to that only MSBuild was available. The build capabilities have continued to evolve with each subsequent release of TFS. In TFS 2010 and 2012, the WF templates (Extensible Application Markup Language) files were stored in source control and could be edited and versioned directly from source control. In TFS 2013, these files were removed to eliminate clutter and streamline the build process. The WF templates can still be downloaded, edited and stored in source control if desired and TFS 2013 does not break existing TFS 2010 or 2012 build process templates. With the support of Git in TFS 2013, Team Build has been enhanced to allow automated building of Git projects as well as TFVC projects.

Windows Workflow controls the overall flow of the build process and TFS includes many pre-built workflow activities for managing common tasks that are performed during a build.[30] MSBuild is the markup language that is found in the .proj (csproj for C# projects and vbproj for Visual Basic projects) files. The build system is extensible with users being able to create their own workflow activities, the ability to inject MSBuild into the process and to execute external processes. The workflow nature of the build allows for unlimited flexibility but it may take some work to achieve that flexibility. Shared[31] and open source projects have been started to build community backed activities to enhance the capabilities of Team Build.

The build process can be configured for various types of builds including scheduled builds, continuous integration, gated check-in and rolling builds. A gated check-in build will shelve code that a developer checks in, perform a "get latest" on the server code and perform a build. If the build succeeds, the code is checked in on behalf of the developer who submitted the code. If the build fails, the developer is notified and can fix the code before trying another check-in.

Builds have retention policies with them so that they do not accumulate when not needed (or builds can be directed not to produce any saved output) or build output can be locked and saved forever. New with TFS 2013 is the ability to check in the build results into source control. This was a necessary enhancement to support automated builds on the TFS service where there is no drop location to place the builds. In the on-premises version build output can be configured to end up in any accessible shared folder location.

The build process in TFS is also part of the traceability mechanism in that build brings together many of the artifacts that are created and stored in TFS. Assuming developers associate source code with work items on check-in, Team Build has the ability to report on the changes in each build - both source code changes and work item changes as well as test results (this includes [unit testing] results as well as automated functional testing (CodedUI) results). As bugs and PBIs are resolved and integrated into builds, the work items which track these artifacts are automatically updated to indicate in which build they were successfully integrated. Combined with the testing tools, testers then get an integrated view of what code was changed in each build, but also which bugs, PBIs and other work changed from build to build.

In Team Foundation Server 2015 and with Visual Studio Team Services Microsoft has reinvented the architecture for the build engine to be based on a cross platform friendly Node.js app. Windows, Mac, and Linux build agents are currently supported. Visual Studio Team Services provides for elastic build capabilities via build hosting in Microsoft Azure.[32]

MikeL MSFT (talk) 15:05, 4 May 2016 (UTC)[reply]

Requesting edits to Release Management section[edit]

Hi my name is Micheal Learned and I am a content developer at Microsoft. I am submitting an addition to this page for the Release Management section for our Team Foundation Server article. I added a new paragraph with links to the DevOps Wikipedia page as well as a link to Visual Studio Team Services to the bottom of the section.

Thank you very much!

Release management[edit]

In mid-2013 Microsoft purchased a product called InRelease from InCycle Software.[33] InRelease was fully incorporated into Team Foundation Server 2013. This capability complemented the automated build and testing processes by allowing a true continuous deployment solution. The tools were re-branded "Release Management" for TFS 2013. The Release Management capabilities give teams the ability to perform a controlled, workflow (provided by Windows Workflow Foundation) driven release to Dev, Test and Production environments and provides dashboards for monitoring the progress of one or more releases.

Microsoft has rebuilt Release Management forVisual Studio Team Services and will be updating the on-premise version of Team Foundation Server with the new changes in Update 2. The new version of Release Management leverages the web browser as the client, and relies on the same agent architecture as Team Foundation Build. Release Management enables DevOps capabilities for Team Foundation Server.


MikeL MSFT (talk) 15:31, 4 May 2016 (UTC)[reply]

  1. ^ OSDir.com. "Subversion for CVS Users :: OSDir.com :: Open Source, Linux News & Software". OSDir.com. Retrieved 2013-07-22.
  2. ^ "About". GitLab.com. Retrieved 16 August 2013.
  3. ^ Gerwitz, Mike (2015-05-20). "GitLab, Gitorious, and Free Software". GitLab.com. GitLab. Retrieved 2016-03-19.
  4. ^ "GitLab Cloud". GitLab.com. Retrieved 10 February 2014.
  5. ^ Step 1: Services and Requirements [Gna!]. Gna.org. Retrieved on 2015-04-01.
  6. ^ Hosting requirements [Savannah]. Savannah.gnu.org. Retrieved on 2015-04-01.
  7. ^ "Launchpad Blog". Blog.launchpad.net. 2015-05-01. Retrieved 2015-05-20.
  8. ^ "About OSDN". OSDN. Retrieved 2015-06-17.
  9. ^ "About Allura". SourceForge. Retrieved 2013-08-25.
  10. ^ "The Next SourceForge". SourceForge. Retrieved 2013-08-25.
  11. ^ "About (SourceForge)". SourceForge. Retrieved 2013-08-25.
  12. ^ Terms_of_Use – sitelegal. Sourceforge.net (19 October 2009). Retrieved on 2010-11-26.
  13. ^ http://blogs.msdn.com/b/somasegar/archive/2012/10/31/team-foundation-service-is-released.aspx
  14. ^ Andy Singleton (2012-03-27). "Announcing Advanced Merge Requests for Git". Blog.assembla.com. Retrieved 2015-05-20.
  15. ^ "Get Started for Free in 60 Seconds | Assembla Plans". Assembla.com. Retrieved 2015-05-20.
  16. ^ — Using Mercurial Queues And Bitbucket.org
  17. ^ Publishing a Website on Bitbucket - Bitbucket - Atlassian Documentation. Confluence.atlassian.com. Retrieved on 2013-09-21.
  18. ^ "Pull Requests 2.0 · GitHub". Github.com. 2010-08-31. Retrieved 2015-05-20.
  19. ^ no file attachments, but images can be embedded GitHub Issue Tracker — GitHub
  20. ^ https://github.com/integrations
  21. ^ "Features". GitLab. Retrieved 2015-05-20.
  22. ^ "GitLab Pages". GitLab. Retrieved 2016-03-07.
  23. ^ "Continuous Integration". GitLab. Retrieved 2015-05-20.
  24. ^ From Savannah's Maintenance Docs, How To Get Your Project Approved Quickly: "The review we do can be lengthy and difficult for both the submitter and the reviewer. Be sure to follow these steps; if your project doesn't comply with our requirements, we will ask you to make changes to your project or register again. This ensures a level of quality for projects hosted at Savannah, and even more important, raises awareness of these legal and philosophical issues related to free software."
  25. ^ "Savannah Administration - In Depth Guide [Savannah]". Savannah.nongnu.org. Retrieved 2015-05-20.
  26. ^ Integrator Workflow: Pull Requests – codeBeamer Knowledge Base
  27. ^ "Application Lifecycle Management with Visual Studio and Team Foundation Server". MSDN. Microsoft. 2013. Retrieved 2013-10-15.
  28. ^ "Adopting Team Explorer Everywhere". Microsoft. 2012. Retrieved 2013-10-15.
  29. ^ "New Release 'Cadence' Begins with Visual Studio 2012 Update 2". 1105 Media. 2013. Retrieved 2013-10-15.
  30. ^ "Team Foundation Build Activities". Microsoft. 2013. Retrieved 2013-10-17.
  31. ^ "Community TFS Build Extensions". Codeplex. 2013. Retrieved 2013-10-17.
  32. ^ "Overview of Team Foundation Build 2015". Microsoft. 2016. Retrieved 2016-03-15.
  33. ^ "Microsoft acquires InRelease, adding continuous deployment to Visual Studio, Team Foundation Server". The Next Web. 2013. Retrieved 2013-11-15.


Cite error: There are <ref group=n> tags on this page, but the references will not show without a {{reflist|group=n}} template (see the help page).

Retrieved from "https://en.wikipedia.org/w/index.php?title=User_talk:MikeL_MSFT&oldid=1164982163"