User talk:MikeL MSFT

Proposing changes
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 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)

Requesting Edit / addition of Release Management to Deployment tools section
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
MikeL MSFT (talk) 16:23, 26 April 2016 (UTC)
 * Ansible
 * OSGi
 * JNLP
 * RPM
 * Apt
 * Capistrano
 * Octopus Deploy
 * OpenMake Software Release Engineer
 * Total Software Deployment
 * ElectricFlow Deploy
 * Lansweeper
 * Visual Studio Release Management

Requesting edits to Proprietary section
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

 * Filesentral – GUI based version control aimed primarily at the non - programmers demographic
 * AccuRev – source configuration management tool with integrated issue tracking based on "Streams" that efficiently manages parallel and global development; replication server is also available
 * Autodesk Vault – Version control tool specifically designed for Autodesk applications managing the complex relationships between design files such as AutoCAD and Autodesk Inventor.
 * CADES - Designer productivity and version control system by International Computers Limited.
 * Dimensions CM - software change and configuration management system developed by Serena Software that includes revision control.
 * IBM Rational ClearCase – SCC compliant configuration management system by IBM Rational Software
 * IBM Configuration Management Version Control (CMVC) – version control system, no longer available.
 * IBM Rational Team Concert – Collaboration and application lifecycle management platform by IBM Rational Software
 * IC Manage Global Design Platform (GDP) – design data management for IC design and Perforce infrastructure support.
 * PTC Integrity (Formerly MKS Integrity).
 * Panvalet - Around since the 1970s, source and object control for IBM mainframe computers.
 * Perforce – Free for up to 20 users.
 * PVCS – originally Polytron Version Control System, developed by Don Kinzer at Polytron, first released in 1985. Now owned by Serena.
 * Quma Version Control System
 * Razor (configuration management), integrated suite from Visible Systems
 * SourceAnywhere – version control tool by Dynamsoft.
 * StarTeam – coordinates and manages software delivery process by Micro Focus, formerly Borland; centralized control of digital assets and activities
 * Surround SCM – version control tool by Seapine Software.
 * Team Foundation Server (TFS) - Development software by Microsoft which includes revision control.
 * Visual Studio Team Services - software as a service by Microsoft that includes Git and Team Foundation version control systems.
 * IBM Rational Synergy – SCC compliant integrated change management and task-based configuration management system, proprietary of IBM.
 * Vault – version control tool by SourceGear (First installation can be used for free)
 * Visual SourceSafe – version control tool by Microsoft; oriented toward small teams

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

Requesting edits to the Future and External Links sections
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)

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

Requesting edits to the Template for Version Control Software
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)

Requesting edits to Continuous Integration Tools
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

 * 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)

Requesting edits to General information and Features sections
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)

Requesting edits to the General Information section
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)

Requesting edits to Team Foundation Server description
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. 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.

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

Requesting edits to the On-premises vs. online section
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
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.

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

Requesting edits to Team Build section
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
(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. 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 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.

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

Requesting edits to Release Management section
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
In mid-2013 Microsoft purchased a product called InRelease from InCycle Software. 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)