TeamCity – customize email notification for specific Projects

emailnotificationsteamcity

I'm using TeamCity 5.1.5

I'd like to customize the email notification template on a per project basis.

Project A : use custom email notification email template to include additional info about the build and test results

Project B,C,D : use the default email notification template

I've perused through the TeamCity documentation and looked into the /config/_notifications/email directory and can't seem to find anything that indicates email templates can be configured on a per project basis. Any help is appreciated.

gracias!

Best Answer

As far as I know, the template files can not be configured on a per-project basis.

However, using the FreeMarker expression syntax and properties provided by TeamCity, you can update the e-mail template to conditionally provide certain information for a given project.

For example:

<#if project.name = "Project A">
    Build Results: Passable
    Test Results: Smelly
</#if>

Related Solutions

Php – What methods exist for setting up a large email notification system

I'd recommend using the third party mailing service Silverpop, or something like it. We've used them for a few years and have been fairly satisfied. They already have relationships with the major email clients (AOL, Yahoo!, Gmail, etc.) and they do a good job of telling you if the stuff you're sending is likely to be classified as SPAM.

They have a fairly extensive API that uses XML HTTP/HTTPS requests that can tie in to existing systems. You can use it to remotely trigger emails, schedule mailings, customize email contents, set up, manage and query huge lists of recipients, run batch processes, etc.

It isn't a perfect service, but compared to a lot of others out there, they do pretty well. I have had very few complaints about them thus far.

Full list of /P MSDeploy arguments for MSBuild from TeamCity

Firstly, the short answer is you can't find the complete list. MSBuild does not have a complete list of parameters you can chose from since you can send any parameter you like. It is a means of communication between the caller of MSBuild and the author of the MSBuild build script (a vs sln or csproj file for instance).

If the build script use the parameter it is used otherwise it is ignored.

So this is a valid call to msbuild:

msbuild /p:<anything>=<anything>

Secondly, you shouldn't send parameters to msbuild from teamcity using the /p: command options. Instead, set configuration or system properties in your teamcity build configuration. They will be passed to msbuild automatically as parameters.

Best Answer

Related Solutions

Php – What methods exist for setting up a large email notification system

Full list of /P MSDeploy arguments for MSBuild from TeamCity

Related Topic