Skip to main content

Do not create a Work Item at Build Failure

The default settings in TFSBuild.proj includes among other things that a Work Item (bug) is created whenever a build failes. This is a very useful feature, but if you do not want it this way it is possible to turn this feature off.

The definition of the CoreCreateWorkItem target in Microsoft.TeamFoundation.Build.targets looks like this:

<Target Name="CoreCreateWorkItem" Condition=" '$(SkipWorkItemCreation)'!='true' and '$(IsDesktopBuild)'!='true'" DependsOnTargets="$(CoreCreateWorkItemDependsOn)">
    <PropertyGroup>
        <WorkItemTitle>$(WorkItemTitle) $(BuildNumber)</WorkItemTitle>
        ...
    </PropertyGroup>

    <CreateNewWorkItem
        TeamFoundationServerUrl="$(TeamFoundationServerUrl)"
        BuildUri="$(BuildUri)"
        BuildNumber="$(BuildNumber)"
        Description="$(WorkItemDescription)"
        TeamProject="$(TeamProject)"
        Title="$(WorkItemTitle)"
        WorkItemFieldValues="$(WorkItemFieldValues)"
        WorkItemType="$(WorkItemType)"
        ContinueOnError="true" />
</Target>

One of the conditions to run the CoreCreateWorkItem is that the property SkipWorkItemCreation is not set to true. By setting this to true we can simply skip that step. The property is set in the PropertyGroup-section.

<PropertyGroup>
    <SkipWorkItemCreation>true</SkipWorkItemCreation>
    ...
</PropertyGroup>
Labels:

Comments

Post a Comment

Popular posts from this blog

The Cornball goes to Brunch with Chaplin

Lately I've been working pretty hard on different projects but not really stumbling upon anything blogworthy. The most recent project is quite interesting though, a single page, touch friendly, web application using the latest and greatest technologies. We've ended up with using Brunch with Chaplin , which is a very neat way of setting up a Backbone based single page web project with Brunch and Chaplin . Aside from this, I have my own little project that has lived on for almost 15 years already, The Cornball . From being a plain Windows application written i C an Win32 API, it has been ported to .NET using WPF, and is currently a Silverlight application hosted on Windows Azure. I could not find a better time to reanimate this project and create a new web based version, touch friendly, super optimized, awesome in any way. So I did... So please follow my journey at Github . It's going to take a while, I assure you, but I already have some ground work done. Meanwhile,...
2 comments
Read more

Binding Enum with DescriptionAttribute in WPF

Binding an enumeration to a ComboBox can be done in several ways. In most cases you don't want to display the value itself, but a more user friendly description. One common approach is to use the DescriptionAttribute on the Enum values to supply a description for each value.  This is all possible in a very MVVM friendly way. First step is to add the  DescriptionAttribute  to the values of the enumeration. public enum MyValues { [Description("First value")] First, [Description("Second value")] Second } To retrieve the description from the enum we use a simple extension method. This method returns the value of the DescriptionAttribute if it exists, otherwise the string representation of the enum value is returned. public static string GetDescription(this Enum value) { var fieldInfo = value.GetType().GetField(value.ToString()); var attribute = fieldInfo.GetCustomAttributes(typeof(DescriptionAttribute), false).FirstOrDefault() as ...
2 comments
Read more

Binding a HTML-formatted string to a WPF WebBrowser control

Sometimes there is a need to display a HTML formatted string in a WPF application. There are a couple of ways to do this, but the most stright forward is to use a WebBrowser control and the NavigateToString method. This approach has one big flaw, you cannot use binding to a string out of the box, but I found a great solution through Stack Overflow which adds a bindable property to the  WebBrowser  control using  NavigateToString . The following class is all that is needed to add that behavior. A new depencency property named Html is introduced to the  WebBrowser  and the proper change action is performed in the OnHtmlChanged method. public class BrowserBehavior { public static readonly DependencyProperty HtmlProperty = DependencyProperty.RegisterAttached( "Html", typeof(string), typeof(BrowserBehavior), new FrameworkPropertyMetadata(OnHtmlChanged)); [AttachedPropertyBrowsableForType(typeof(WebBrowser))] public static string GetHtml(...
1 comment
Read more