May is coming to a close, and we’ve had more Team Services accounts installing extensions than any month since we launched the Marketplace. The ecosystem momentum we’ve seen this year is strong, and there are still so many exciting integration opportunities out there to go enable.
Over the last few years, Microsoft has been moving the entire company to a modern engineering system built on Visual Studio Team Services and using Git as our version control system. For many of the projects within Microsoft, this is no problem,
Note: If you do not see the preview feature on your account, kindly leave a comment to this blog with your team services account name.
There are multiple stakeholders for a release. Whether the team is small or large, keeping the right stakeholders informed about how releases are progressing and what actions are required.
Have you ever struggled to create a mental model of how the deployments to your environments would progress? We are introducing the pipeline view for your release definitions that will show how your deployments flow. Approvals, environment and deployment settings are now in-context and easily configurable.
Discovering relevant work items should consume as little time and effort as possible. That’s why we have built work item search with speed and simplicity in mind, so you can spend more of your time on your work and less time searching for work items.
A little over a year ago we released the new work item form to Visual Studio Team Services and now with TFS 2017 the same great functionality is available to our on-premises customers. Here are some highlights of the new features available today:
Integrated development control to track existing code assets and to create new ones
Notification of changes to work items through the Follows action
@mention and #ID functionality in the discussion field to notify people when a discussion is updated and add relevant work items
A work item extensibility model which lets you extend the form with custom controls,
To demonstrate our continued commitment to support Java developers and their full lifecycle DevOps needs with Visual Studio Team Services (VSTS) and Team Foundation Server (TFS), I want to share some of our recent and exciting Java-related feature announcements. Our teams are working with large and small Java teams every day to better understand their needs and to solicit recommendations for improvements of our tools.
Back in March, I wrote about the WhiteSource Bolt extension for VSTS. This is a fantastic way to automate security checks for open source vulnerabilities in the release pipeline of your team project. The most frequent question Iâ€™ve received is, When can we have this for TFS too?
We have had a number of customers ask us how they can create / define variables while creating a Release, similar to how they can do this while queueing a Build. So I thought I would write a quick blog that explains how this can be done.
It was a busy week for everyone last week at the Build 2017 conference in Seattle. Thanks to everyone who was able to attend the conference and stop by the DevOps area to talk about VSTS. Even for the people that were there in person it is impossible to catch everything,