It's been a while since I last blogged about the Azure DevOps Extension Tasks. Here are the things that have changed since the last update [https://jessehouwing.net/vsts-relnote-ci-cd-tools-for-vsts-extensions-1-1-75/]: * Added support for publishing Visual Studio extensions. * Support for versioning localized Azure Pipeline tasks * Support for executing under Node 10 * Fixed
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
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
The standard Authentication Schemed in VSTS include Basic (username/password), Token, Service Credential (for Azure) and AzureCertificate Authentication. If you simply need a username password or a Personal Access token you can derive your own Credential Type from one of the exiting Authentication Schemes. You can see an example of
> 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:
When creating a Visual Studio Team Services extension (such as a collection of build tasks), it makes sense to publish it as a privateextension first. You can do this by overwriting the extensionid from the commandline, but there is no direct commandline switch to override the visibility of an extension.
Though generally considered a bad practice I crafted two build tasks to manipulate your TFVC repository from the build [https://github.com/jessehouwing/vsts-tfvc-tasks]. You can now edit, delete and add files and check those changes in when you're ready. Before I explain how they work and how you can