Pulling build number from dependency

I have config A1 in project A that pulls artifacts from config B1 in project B. It also copies the build number from B1. The build number format in B1 is set to {0} and the build script generates a new version number and emits the appropriate message to set the build number. The build number changes correctly for B1 once the message is emitted. The build number format in A1 is set to %dep.bt192.build.number% (where bt192 is the id for B1).

This was working fine in 6.0 (and all the way back to 4.0). With 6.5, A1 is now copying the incrementally assigned value from B1 (the build number created by {0}). Is this new behavior? If so, is there a workaround to get the correct build number from B1?

8 comments
Comment actions Permalink

Hi

I rechecked this scenario, and was not able to reproduce the issue.
Could you show screenshots of configuration A1 settings - build number format, snapshot dependency.

Thanks

0
Comment actions Permalink

General Settings from A1:
A1 - Config.png
Dependency Settings from A1:
A1 - Dependencies.png
History from A1:
A1 - Status.png
Notice that the builds starting from June 3, which is the first build after upgrading from 6.0 to 6.5. The builds all have the 3 digit incrementing value from the dependency build and not the dependency build's 4-part build number. I had to manually set the build number for the June 6 build, which is why it has the correct format. The most recent build should have the build number 3.0.20110604.1 from the most recent B1 build, but it has 266 instead.

B1 Config:
B1 - Config.png
B1 History:
B1 - Status.png
The build number for B1 is assigned by the build script by emitting the buildNumber message.

0
Comment actions Permalink

Has there been any further action on this? It is rather irritating.

0
Comment actions Permalink

Do you need anything else from me?

0
Comment actions Permalink

Could you please check 'Build Properties' tab of a successfully finished build of B1. What are the values of properties that contain build?number in name?
What is the value of configuration parameter 'build.number'?

How do you set build number for your builds of B1?

0
Comment actions Permalink

For B1, the build.number and system.build.number properties are both 266 which is the original incremental build number. The build number for this build is set using the teamcity-info.xml file. My earlier statement that it was set via the buildNumber message was incorrect. These are somewhat older build configurations and we do it differently in the later configs.

0
Comment actions Permalink

Thank you for infomration.
I created an issue for your case at
http://youtrack.jetbrains.net/issue/TW-17688

Please vote for it.

I added a workaround to the issue. Does it applicable to your case?

0
Comment actions Permalink

It appears that the workaround is successful in my case. I just added a buildNumber message when I write the teamcity-info.xml file and the build number is now reflected correctly. Thank you!

0

Please sign in to leave a comment.