Team Foundation Build Custom Tasks

Sign in to queue

Description

The new Team Foundation Build system is a significant improvement over the legacy XAML-based build system. It's more transparent and predictable, natively cross-platform, and lets you write your own steps far easier than ever before.

In this video, I'll walk through creating custom build tasks that you can include as part of your build definition.

I'll start by briefly introducing the new build system and I'll provide some background on how it works and the reasons for the changes. I'll also show some resources that Microsoft has made available.

I'll show you what's involved in the creation of a custom build task, using the new Octopus Deploy Create Release custom task as an example. I'll walk through creating a manifest, adding any associated resources required for your custom task, and uploading it to Visual Studio Online.

Finally, I'll create a new build definition and add our custom task. I'll queue a build and show you what happens under the covers to make everything work together.

Resources:

Embed

Download

Download this episode

The Discussion

  • User profile image
    Chris Eelmaa

    Nice.

    I didn't understand where does the version number of release come from?

    Thanks.

  • User profile image
    Damovisa

    @Chris Eelmaa:

    Hi Chris,

    The version number for the release is tied to the version number of the Nuget Package pushed to Octopus. Using OctoPack means the Nuget Package version (in this case) is given the version of the assembly in the project being compiled.

    You can set the Release numbering format in the Project Settings page in Octopus Deploy.

    I hope that helps,

    Damian Brady

Add Your 2 Cents