Azure Pipelines - Scrum Bug (Page 2)

Azure Pipelines

A collection of 37 posts

New versions of TFS/VSTS build tasks

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

Extending your
Build and Release pipeline

Azure Pipelines

Extending your Build and Release pipeline

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

Automatically populate your Source branch when publishing to Sonar

When you enable your build definition to trigger on multiple branches, you may not want them all to publish into the same Sonar project. Sonar has the concept of Branches, they're simply appended to the Project Key with a -. This prevents an old Hotfix build from messing

Define a custom Authentication Scheme for your VSTS extension

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

Access all available build variables from your VSTS Build task

> 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

Binary promotion of Visual Studio Team Service Extension

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.

Publish Build Tasks to TFS 2015 without configuring Basic Auth on the server

When you want to publish build tasks to a TFS 2015 server, you need a Basic Authentication enabled endpoint. Unless your server is configured with SSL, this is a major security concern. Until now the guidance I received was to setup a second Application Tier, configure it with Basic Auth

Mimic the XAML build's Output Location option in Build 2015

If you've been using XAML builds in the past, you've probably discovered that, by default, it drops all the outputs of all your projects into one folder called the Binaries Folder. Unless you do anything using a post-build script, the contents of that folder will be

Manipulating your TFVC repository from Build 2015

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

Building multiple configurations and/or platforms in Build 2015

In XAML builds you could specify one or more configurations to build, if you left these values empty, the solution default would be built. Unless you were using a customized build template, each build|configuration pair would be built and tested in sequence. The Build Agent will create a sub-folder

Upgrading from XAML to Build 2015 with minimal changes

This series is currently a work in progress XAML builds on Visual Studio Team Services will be deprecated in September 2016. While support for XAML builds seems to stay around on-premise for a little while longer, it's time to upgrade to Build 2015. You may have invested quite

Access multiple TFVC repositories in a Build 2015 definition

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