Date Build Number Plugin installation

I'm using TeamCity for the first time and would like to include the current date in the build number.  Rather than try to work that into the build script and modify the build number from there, I saw there is a rudimentary date plugin.

Unfortunately, I'm having a hard time getting it to work.  At least, I think so because it's not putting the date in the build number and I don't think it's because I'm specifying the tag incorrectly.  It's not hard to use the tag {date}.

So here's my configuration:

datePlugin.jar downloaded from this site.
Zipped into
Zip in the teamcity data directory under plugins.
teamcity-plugin.xml as follows, also in plugins subdir:

<?xml version="1.0" encoding="UTF-8"?>
<teamcity-plugin xmlns:xsi=""
    <name>datePlugin</name> <!-- the name of plugin used in teamcity -->
    <display-name>Plugin for using a {date} tag in the build number</display-name>
  <deployment use-separate-classloader="true" /> <!-- load server plugin's classes in separate classloader-->

I've restarted both the web and agent services on this server.  Whenever I use the {date} tag in a build number, however, it does not get replaced.

There is a .unpacked directory under the plugins directory, so at least something is happening.  Unfortunately I don't know the proper tools to investigate further how far it is getting or how to debug it.





Sorry for the delay in replying.

Do you mean plugin?

It should work once you put the plugin under <TeamCIty home>\webapps\ROOT\WEB-INF\lib

If you want to put it under .BuildServer\plugins, then you should make sure you run TeamCity 4.0+ and put it as .BuildServer\plugins\datePlugin\datePlugin.jar

Debug server logs and console output for the server start can help investigate the problem if plugin won't start.

BTW, there is a feature request to address the issue and it has another plugin described in comments that adds propeties to use in the build number.


Hi Yegor,

Thanks for the pointers.  Haven't been able to figure out the pointer to the feature request yet, but I'm working on it.  If that doesn't work out, I'll go back to the advice on the third-party plugin.

As a side-note, I've now migrated up to the release version of 4.0.2 and was disappointed by the feature restrictions of the new version.  In particular, I've been "selling" the concept of continuous integration here at DidItBetter Software partly based on the fact that we could use Windows Authentication for access control to the build system, which has been a hotpoint for developers not wanting mistakes or external interference with their build process.  While this was readily available with the EAP TeamCity, I didn't see it coming that the release version wouldn't support this important feature.  Now I'm holding the bag, so to speak (that means I don't look good).

$2000 is a bit steep for a three-developer shop.  Is there any softer, kinder licensing for EAP participants?

We're not only a software developer but also an IT infrastructure consultant for local area shops, so we'd like to work further with your product and perhaps recommend it to our customers.  We've implemented CruiseControl.NET as a trial project to manage the compilation and deployment of web-based documentation (Help&Manual for chm, html, pdf), which reaches segments of our customer base that don't even do software, actually.  We're actively selling the concept to customers and TeamCity would make an even better back end, if we can get comfortable using it.



By the restrictions, do you mean NT domain authentication? TeamCity Professional only supports default authentication (that is, users are managed inside TeamCity only). For NT domain or LDAP authentication to work you will need Enterprice license. Another alternative is to use TeamCity EAP releases that come bundled with evaluation enterprise license.

As a conultant, I guess you can contact our sales to request an Enterprise license, but I am not sure what it takes to persuade them


Please sign in to leave a comment.