Autoincrementer plugin with TeamCity 6.5 EAP

Bump... anybody from JetBrains willing to fix the problem? Last check-in on autoincrementer was by pavel.sher, build output is here: http://teamcity.jetbrains.com/viewLog.html?tab=buildLog&buildTypeId=bt287&buildId=45856?

I'd fix it myself if I had access to the repo :)

Cheers,

Dean

I fixed the build on teamcity.jetbrains.com. For 6.5 version you can use this build:
http://teamcity.jetbrains.com/viewLog.html?buildId=50484&buildTypeId=bt287&tab=artifacts

For versions 5.0.x - 6.0.x:
http://teamcity.jetbrains.com/viewLog.html?buildId=45821&buildTypeId=bt177&tab=artifacts

Thanks for that Pavel. Unfortunately it still doesn't work... I'm wondering if it has something to do with our use of build templates - the %autoinc.ABC_TRUNK% syntax works just fine if used in a standard build configuration, but breaks if we use it in a template. Any ideas?

Cheers,

Dean

Hi Pavel,

This is definitely not working in the latest TeamCity 6.5 EAP (build 17704) either. I'm not sure whether this is a bug I should log against the plugin or against TeamCity itself. Can you advise?

Thanks & Regards,

Dean Ward

Is it possible to create a very simple build configuration where this problem can be reproduced? We are using this plugin internally, and it works fine. Probably there is some specific in your case, would be great to have project-config.xml where this problem reproduces.

Hi Pavel,

As luck would have it that pushed me in the direction needed to fix the issue! I think when the plugin was not working the individual build configurations picked up %autoinc.ABC_TRUNK% as a configuration parameter and they were each populated with <empty>. When a working version of the plugin was re-instated the local version of the parameter was used and so we got build numbers with a missing value!

I've gone through and removed all the spurious parameters and now everything is working :).

Thanks very much for your help and for producing the best build server around!

Dean