CODEWITHSUNDEEP
continuous-integrationteamcity
arconaut
arconaut

Reputation: 3285

Put current build number of 'release' configuration to 'nightly build' configuration?

We've just started to use TeamCity as a continuous integration server. There's a problem we're trying to solve now:

We have a 'release' configuration, it has build versions set like this: 1.0.0.{0} We also have a 'nightly build' configuration, which build number is: 1.0.0.0.{build.vcs.number.1}

So the first 2 digits are OK, Major+Minor versions. Third one is supposed to be set up manually as well according to our process (rarely though). But as you can see, the last one increases with every 'release'.

The question is - how do I make TC copy the current 4th digit (or all of them) of 'release' to that of 'nightly build'?

Upvotes: 3

Views: 1085

Answers (2)

Mike Two
Mike Two

Reputation: 46203

One way to do it in 4.5 is to

  1. Make nightly have a snap shot dependency on release.
  2. find the internal build id of release.
  3. use a build number format in nightly that looks like

%dep.releaseid.system.build.number%.{build.vcs.number.1}

where releaseid is the id you found in step 2. This will replace the whole %...% thing with the build number from release.

The TeamCity 4.5 Docs for dependency properties explains this and shows you how to find the internal id.

Upvotes: 3

Yishai
Yishai

Reputation: 91931

If you can know it in your build script, you can send it to team city during the build. Here are the instructions. I can think of a couple of strategies for getting the build number from the release build, none of them elegant. The most obvious would be to publish an artifact from the release build that is basically a text file with the build number in it, and retrieve that from your build script.

Upvotes: 1

Related Questions