I just pushed out new versions of the following tasks: * MsBuild Helper Task [https://marketplace.visualstudio.com/items?itemName=jessehouwing.jessehouwing-vsts-msbuild-helper-task] * Fixed a number of bugs when the Agent's work folder has a space in it somewhere. * Snyk [https://marketplace.visualstudio.com/items?itemName=jessehouwing.vsts-snyk] * Fixed auto-update of built-in
To prepare your TFS Project Collection for migration, you may want to remove (stale) old data to reduce the database size first. Most actions are already documented here. Queries that can aid in detecting where your space is allocated are also found in this recent support ticket. Delete old workspaces
The new build and release engine that ships with Visual Studio Team Services and Team Foundation Server 2015 (The Release Management bits shipped with TFS 2015 update 2) provides a whole new way of configuring your Continuous Integration and Deployment pipeline. A much improved and simplified way. You may have
While I've released my VSTS Extension Tasks to GitHub [https://github.com/jessehouwing/vsts-extension-tasks] and the Visual Studio Marketplace [https://marketplace.visualstudio.com/items?itemName=jessehouwing.jessehouwing-vsts-extension-tasks] some time ago, I was reminded that I've never really blogged about it yet. You may wonder what it does. The VSTS Extension
> This StackOverflow answer covers the options in the Node and PowerShell3 handlers [https://stackoverflow.com/a/55610724/736079]. NOTE: This cmdlet works with the Powershell host that shipped with TFS 2015 RTM and which will be replaced with a new task runner. Whether this functionality will remain, is uncertain [https:
The documentation for SonarQube explains how to configure SSL when you're running on Linux [http://docs.sonarqube.org/display/SONAR/Running+SonarQube+Over+HTTPS]and how to use the native Tomcat functionality for a simple test environment, yet they recommend not to use this functionality in any production like setting.
When you have a TFS project collection with many Team Projects, it's a common practice to have a "shared" project containing a collection of commonly used libraries. This library may consist of Checkin policies, Build Activities, MsBuild tasks and Custom MsBuild targets. The alternative used to be to check in
If you're bulk-creating, importing or editing test cases in Visual Studio Team Services, you're probably aware of the "Edit as Grid" option, which opens your test case in a spreadsheet like layout for bulk editing: Not many people know that you can extend this grid easily to bulk-edit additional fields,