20

I'm trying to use assembly info patcher to create a version number something like:

1.2.3.1a3c19e

where the last bit is the git short hash.

I've tried using a powershell script build step to create the short hash (as I cant find a variable that has it) and adding this to a system variable but this build step appears to run after assembly info patcher, so isn't much use.

Neil P
  • 2,920
  • 5
  • 33
  • 64

2 Answers2

34

If you want to write this to the Assembly Info field it can be done, but it requires a separate build configuration to generate the build number. The sole purpose of this step is to create the build number that has the hash appended to it.

1. Create a build configuration to generate the short hash

Build Config

2. Add a step to generate the hash

Build Config

3. Add a parameter to store the hash

Param

4. Add a second build configuration and add a dependency to the first one

Dependency

5. You can now consume the parameter in the dependent step

Consume

6. At this point you can use it in the assembly info patcher

Patcher

The alternative to this is to write your build number back to Git using the VCS labeling build feature.

Labeling

Hope this helps.

Matt
  • 3,684
  • 1
  • 17
  • 19
  • 2
    Just want to add that separated build configuration is needed because assembly info patcher is running after changes from VCS have been collected and before steps start to execute. There is a way how you can get rid of separated build configuraiton for the example above by using powershell script which go thru all AssemblyInfo.cs files and does replacement instead of assembly info patcher: `(Get-childitem -include AssemblyInfo.cs -recurse) | Foreach-Object { Set-Content -Encoding UTF8 $_ ((Get-content $_) -replace "1.0.0.0", "1.0.0-%GitShortHash%")}`. – Alexey Andrushkevich May 25 '15 at 10:03
  • @Alexey. I agree you could write a script to do this in powershell, but I would be very wary of dropping this code in as it's more likely to break the build. By default, AssemblyInfo.cs contains AssemblyVersion and AssemblyFileVersion which would fail to compile if you used the short hash. The AssemblyInfo.cs would need some "prepping" first for this script to not break the build. – Matt May 25 '15 at 12:12
  • @DevOps, you are right for 100%. I have left my comment and example of script just to make note that it's possible to do this without adding another build configuration what can be problematic for smbd due to license limitations. The powershell script I've posted has to be updated in order to replace version for required attribute only. – Alexey Andrushkevich May 25 '15 at 12:17
  • How/when does the PS variable get into the `GitShortHash` parameter in Step 3, as you've left the value empty? Does the parameter in step 3 need to be an environment variable, configuration parameter, or system property to get the value? Mine is always empty even though the build log shows `##teamcity[setParameter name='GitShortHash']`. – flipdoubt May 03 '19 at 22:11
0

If you mean .NET assembly you will not be able to use git's short hash as the revision number just because it accepts numbers only. You can check it yourself and put the version above to AssemblyVersion. I bet your app will not be compiled. Instead you can use %build.counter% variable from teamcity as the revision number.

Alexey Andrushkevich
  • 5,992
  • 2
  • 34
  • 49
  • 5
    It is true that you can't write this hash to certain fields. I assume the goal here is to tie up the assembly version to the git commit, in which case it would make sens to write to the Assembly informational Version as this accepts a string. – Matt May 24 '15 at 12:40