TeamCity support

Should probably introduce script alias properties to make it cleaner and easier to use.

• Set build version
• Block opened/closed
• Progress message/start/finish
• Publish artifact

Script aliases:

// Detect if this is a team city build
bool IsTeamCityBuild();

// Set progress.
void SetTeamCityProgress("Building things");

// Start and finish progress scope.
void StartTeamCityProgress("Building things");
void FinishTeamCityProgress("Building thing");

// Set build version.
void SetTeamCityBuildVersion("1.0.0");

// Open and close message block.
void OpenTeamCityBlock("Run unit tests");
void CloseTeamCityBlock("Run unit tests");

// Publish artifact.
PublishTeamCityArtifact("./bin/**/*");

Convenience:

// Report progress
using(TeamCityProgress("Building things")
{
    // Do magic 
}

// Wrap operations in message block.
using(TeamCityBlock("Run unit tests"))
{
    // Do magic
}

[patriksvensson]

I like the idea of a Cake runner for TC!

On 26 aug 2014, at 08:18, Gary Ewan Park [e-mail] wrote:

Or, you might want to think about a Meta Runner:

https://github.com/JetBrains/meta-runner-power-pack

Which don’t require you to restart the TeamCity Server in order for them to be used.

— Reply to this email directly or view it on GitHub.

[patriksvensson]

I syspect all this have been implemented. Will investigate 😄