MSBuild Service Tasks

Skip to end of metadata
Go to start of metadata
You are viewing documentation of TeamCity 4.x, which is not the most recent released version of TeamCity. Please refer to the listing to choose another version.
Search

Searching TeamCity 4.x Documentation

Table of Contents

For MSBuild, TeamCity provides the following service tasks that implement the same options as the service messages:

TeamCitySetBuildNumber

TeamCitySetBuildNumber allows user to change BuildNumber:

It is possible to use '{build.number}' as a placeholder for older build number.

TeamCityProgressMessage

TeamCityProgressMessage allows you to write progress message.

TeamCityPublishArtifacts

TeamCityPublishArtifacts allows you to publish all artifacts taken from MSBuild item group

TeamCityReportStatsValue

TeamCityReportStatsValue is a handy task to publish statistic values

TeamCitySetStatus

TeamCitySetStatus is a task to change current status text and/or message

*'{build.status.text}' is substituted with older status text.
Status could have one of the following values: NOT_CHANGED, FAILURE, SUCCESS, NORMAL, ERROR

Labels:

nunit nunit Delete
messages messages Delete
msbuild msbuild Delete
service service Delete
task task Delete
Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.

1 Comment

comments.show.hide

  1. Feb 24, 2009

    Sire404

    To make msbuild run project files with these TeamCity-specific servicemessages in them, use the following hack:

    Add a condition that is only true when built through TeamCity, like this:

    <TeamCityProgressMessage

      Condition="'$(TEAMCITY_BUILD_PROPERTIES_FILE)' != '' "

      Text="Message to the TC interface" />
    Thanks to Dave Oilar!
    (http://www.jetbrains.net/devnet/thread/279897)