Nice, now we are able to help are our clients take the last step in migrating from TFS to VSTS. Good work!
Build and release:
- View VSTS dashboards within Microsoft Teams
- Investigate build history through a new build dashboard widget
Soon, very soon, the word “account” will be replaced by the word “organization” all over VSTS. Read all about it in the DevOps Blog from Microsoft. Nice change!
Be sure to check this out if you are a VSTS user. Cool new navigation in preview. Read all about it in the Microsoft DevOps blog article.
Just a heads-up! Have you all seen the new VSTS Release Pipeline view? How cool is that?! Thanks @Microsoft @VSTS team for listening to the community!
Detailed view on one environment:
Heel interessant artikel om te lezen hoe VSTS wordt ontwikkeld en gedeployed qua branching in Git. Mooi om te zien hoe ook Microsoft open is over hun manier van werken en hier blog artikelen over schrijft.
Nice new blog post from Alex Nichols, Senior Program Manager on the Visual Studio Team Services team at Microsoft:
“We recently published an update to the “Features under development” roadmap on our Features timeline. This feature list, although subject to change and not comprehensive, provides visibility into our key investments in the medium term. We update the feature list as part of our agile planning rhythms, about every 9 weeks. Some of the features link to deep dive blog posts or articles where you can find out more. We also denote the version of on-premises TFS we expect the feature to be included in, often after getting mileage on VSTS. Here are a few features that are particularly noteworthy.
Code: Add required reviewers as a contributor
You’ll soon be able to get a little more specific in pull requests. In Q1 we plan to allow pull request contributors to add required reviewers instead of merely relying on branch policies.
Code: Filter by target branch and labels
In repositories with a lot of branches and activity it can be difficult to focus in on the important pull requests in progress. In Q2 we plan to add filters to the pull request list for target branch and labels to get you collaborating sooner.
Code: GVFS for Mac – Public Preview
While GVFS got it starts in supporting the development of Windows, the largest Git repository on earth, that isn’t the only massive repository at Microsoft. Office also has a lot of code, as you can imagine, and shares a lot of it between their macOS/iOS and Windows products. Based on our work with the Office team, in Q2 we plan to bring GVFS for Mac back out to the community as well in public preview.
Work: New Agile Hubs
We are in the middle of a big refresh to our core hubs in Work. In Q2 you’ll see consistent filter and favoriting experiences across the board to help you get to the work items you care about with ease. As you build the list of favorites you’ll find it handy to quickly jump between the work of various teams or sets of related work.
Build and Release: Configuration as code (YAML)
Last Fall we announced the availability of YAML builds to give you another option for defining and evolving your CI as your code evolves. In Q2 we look forward to bringing that out of preview and making it generally available. In Q3 we look forward to bringing YAML to releases in public preview so that your deployments can evolve with your code as well.
Build and Release: VM and additional languages support for DevOps Projects
Coming off the release of Azure DevOps Projects last Fall, we’re planning to add additional support to cover even more situations you may have to start a new project. In Q1 we plan to add virtual machines as a new target service option and both the Go and Ruby language options.
Package: Maven general availability and upstream support
Maven artifacts can be set up as a feed in Package Management to share them with your team and organization. In Q2 we plan to make this type of feed generally available and also bring upstream support so you can setup Maven feeds stored in a variety of locations.
Admin: Multiple Accounts per “Organization”
As more teams use VSTS for their projects and create accounts, we’ve heard clear scenarios from organizations that have driven focused investments starting with the thoughtful relationship of accounts (known as “Team Project Collections” in on-premises TFS) under a single organization umbrella. We’ve made key progress internally on this current #3 top requested idea on UserVoice and plan to bring this public this year after adopting it for ourselves.
We appreciate your feedback, which helps us prioritize. If you have new ideas or changes you’d like to see, provide a suggestion on UserVoice or vote for an existing one.”
A nice list of improvements and features in the next VSTS release! Check out the below link!
26 September 2017 9:00 – 27 September 2017 17:00
Janssoniuslaan 80, 3528 AJ Utrecht
Software engineering practices have changed drastically in the last few years. Agile practices, DevOps, Cloud Computing, Open Source and similar developments have proven their effectiveness. Microsoft’s platforms for software development and cloud computing have also embraced these concepts and are at the leading edge in their domain.
In this two-day training you will learn how software development works with Microsoft’s tools and languages. Based on a consistent sample, you will learn how to
- setup a development environment with the latest version of Visual Studio and Visual Studio Team Services,
- highlight and learn to benefit from the latest developments in the Visual Studio C# IDE (e.g. PerfTips, live code analysis, CodeLens, diagnostic tools, (etc.),
- use cross-platform build- and test-automation tools like Visual Studio Web and Load Tests, Visual Studio Team Services, Gulp, xUnit and Jasmine to automate your build- and quality assurance processes,
- manage your Technical Debt,
- create highly available and secure environments for your web APIs and web applications in Microsoft Azure with Azure Resource Manager (ARM),
- setup a multi-stage (dev/test/prod) environment in Azure,
- automate deployment to Microsoft Azure with Visual Studio Release Management,
- using Application Telemetry with Application Insights,
- discuss the advantages of the upcoming container technology Docker,
- we will use a sample (web) application during the course.
You will need your own laptop to do the hands-on labs. Ideally, you have the latest version of Visual Studio installed (detailed instructions about the necessary Visual Studio configuration will be provided) and you have access to your own Microsoft Azure subscription. If you do not have access to Visual Studio and/or a Microsoft Azure account, Microsoft will provide a limited number (first come, first served) of free Azure Passes that you can use to run a VM with Visual Studio in it. In that case you just need internet access and a remote desktop client on your laptop.
For the labs about build- and test-automation, you need your own Visual Studio Team Services subscription (free edition available).
- Welcome and introduction.
- Setup development environment for the course.
- Discuss the sample application used during the course.
- Setup Continuous Integration (including first steps in test automation).
- Managing Technical Debt with SonarQube.
- Adding an artifact repository to your release pipeline.
- Continuous deployment with Visual Studio Release Management.
- Configuration as code.
- Application Telemetry with Application Insights.
- Operating web applications in Azure App Services and Docker.
Features under development
This feature list is a peek into our roadmap. It identifies some of the significant features we are currently working on and a rough timeframe for when you can expect to see them. It is not comprehensive but is intended to provide some visibility into key investments. Most features are linked to a blog post and/or UserVoice entry where you can learn more and comment. These features and dates are the current plans at this time and are subject to change. The “Planned Date” reflects when the feature will be available on VSTS and the “Server” column reflects when it will be available in TFS on-premises, if applicable.
Source: Team Services Feature Updates