I need to find out the actual build number for Tridion 2013 SP1. Need info for corporate auditing prior to installation.

3 Answers 3


The build number is ''

You can find this by clicking on the SDL Tridion logo the CMS, I'm also sure this information can be found in the installation documentation. If you can't find the logo, you can also try the About entry in the left-hand slide-out menu. On my system, this can also be reached via http://localhost/SDL/#app=wcm&entry=about

Full version details

  • Content Manager Build 7.1.0
  • Content Manager Explorer Build
  • Experience Manager Build
  • Update version - SP1
  • Content Delivery Version: 7.1
  • Jar file build version (Handy for build systems like Maven): 7.1.0-STABLE.165
  • 3
    Rather than create a new answer, I've added the full list to your answer John.
    – Nuno Linhares
    Mar 3, 2014 at 15:54
  • 3
    Took the liberty of adding the proper build system version string for the CD Jars.
    – Raimond
    Mar 3, 2014 at 16:29

Yes you can find under the Home > Web content Management > About there u will find out build number,


As John says, clicking the logo in the CMS will get you a long way. If you need to audit the version of every deployed jar and dll, you will need mroe work. The problem here is that hotfixes often ship new versions of files.

There is a script on Tridion Practice which automates the extraction of build versions from jar files. This is a powershell script for use on Windows, but I've heard a rumour that customer support have a Bash version for use on *nix systems.

If you want to find the equivalent information for .NET assemblies, you can also do this easily enough from the powershell. Here's a quick and dirty version to demonstrate the principle. You'd probably need to modify it to suit your own purposes:

gci 'C:\Program Files (x86)\Tridion\bin' | ? {$_ -is [IO.FileInfo]} | % {$_.VersionInfo.ProductVersion + "`t" + $_.Name}
  • OP indicated he needed it prior to installation, so there is nowhere to click... Mar 4, 2014 at 10:34
  • An audit prior to installation would presumably be checking the current versions of things. Otherwise, what would you be auditing? Mar 4, 2014 at 21:40
  • Perhaps they want a detailed list of what versions will be installed exactly so that they can audit on that after the install, or maybe they want to Google for known issues with those versions. I wouldn't know, but fact is that is what the OP stated, if that is unclear, you should ask the OP for more info ;) Mar 5, 2014 at 7:52
  • The OP said 'auditing prior to installation'. Unless they clarify that further, I'll assume that they intend to audit prior to installation. Mar 9, 2014 at 19:24

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.