build.buildNumber not resolving for build_started.ftl email

Hi,
Sometimes the ${build.buildNumber} resolves and sometimes it doesn't on the "build started" emails.  For build completion emails, it works fine.

When it doesn't resolve, emails are sent out with the buildNumber as ???.  

We generate custom build numbers with autoinc so using  ${build.getParametersProvider().get("build.vcs.number")} is not a valid solution inside the build_started.ftl.  

We need to use ${build.buildNumber}

Thanks

3 comments
Comment actions Permalink

Hi Dan,

You're right. If you're using parameters references in a build number, it is possible that some of them will be unresolved, e.g. on a build start.
In this case ${build.buildNumber} returns "???" (in fact you can see the same on a web UI).
You can obtain the raw value using ${build.rawBuildNumber}.


--
Maxim

0
Comment actions Permalink

Maxim,
Thanks for you reply.  If i use the build.rawBuildNumber I get %build.vcs.number% instead of ??? from the build_started.ftl email.

0
Comment actions Permalink

Hi,

Yes. That is exactly the reference that TeamCity can't resolve.
I've created the issue on this matter: http://youtrack.jetbrains.com/issue/TW-20804. Please watch it.


--
Maxim

0

Please sign in to leave a comment.