Teamcity variable replacement in nuspec file

Question

This is my nuspec file to get the package generated from teamcity. The version is actualy set by the teamcity variable.

<?xml version="1.0"?>
<package >
  <metadata>
    <id>Company.Name</id>
    <version>$version$</version>
    <title>Title</title>
    <authors>My Name</authors>
    <owners>We are the owners</owners>
    <requireLicenseAcceptance>false</requireLicenseAcceptance>
    <description>Support</description>
    <releaseNotes>Summary of changes made in this release of the package.</releaseNotes>
    <copyright>Copyright 2013</copyright>
    <tags>Core</tags>
    <dependencies>
        <dependency id="Core.Assembly" version="[1.0.$teamcity.build.id$]" />   
    </dependencies>
  </metadata>
</package>

How would I replace the version with the current teamcity build id number? Tried with both $teamcity.build.id$ and %teamcity.build.id%

This did not work. I tried with $version$ as well. The version gets correctly replaced in the version tag of the package, but not on the dependency.

I want to use the same version of the package that is in the current build, so they have the same build number.

score 13 · Accepted Answer · answered Jul 29 '13 at 19:23

Resolved with AssemblyInfo patcher from Teamcity Build Features.

To fix,

Configuration Steps -> Build Steps -> Add Build Feature (Button)

Add AssemblyInfo Patcher and give the version to 1.0.%teamcity.build.id% and that resolved the problem.

Having the dependent libraries at the version with the $version$ resolved it.

Hope it helps.

score 11 · Answer 2 · edited Nov 21 '14 at 15:58

11

You don't need to replace it via TeamCity variables. Use the -version switch, something like:

nuget.exe pack <nuspec> -version %teamcity.build.id%

This way the nuspec version will be overridden at runtime.

edited Nov 21 '14 at 15:58

infojolt

5,244
3
40
82

answered Jul 28 '13 at 21:50

Manuel Spezzani

1,041
7
15

3

Dependent Libraries need to be of the same version. Resolved with Assembly Patcher. – Kannaiyan Jul 29 '13 at 19:20

score 3 · Answer 3 · answered Dec 09 '15 at 03:09

3

I solved it by simply putting [$version$] in my dependency.

answered Dec 09 '15 at 03:09

Jeff Dunlop

893
1
7
20

AssemblyInfo Patcher versions your dll as well. Otherwise dll will be on one version and nuget package will be on another version. – Kannaiyan Dec 10 '15 at 15:59
1

This worked for me. The key is to make sure the `-Version` switch is used on the `nuget pack` command. – craftworkgames Mar 06 '17 at 11:45

score 3 · Answer 4 · answered Dec 15 '15 at 19:34

3

In TeamCity 9.1 You can override the version number in the "Nuget Pack" build step.

answered Dec 15 '15 at 19:34

Jacob Brewer

2,574
1
22
25

This may be cumbersome to configure if you want to have same versions across all projects. Means you need to configure for each nuspec instead of one centralized location. – Kannaiyan Dec 31 '15 at 16:12

Teamcity variable replacement in nuspec file

4 Answers4