# 1.0.0.187 - Build Number

**URL:** https://www.finalbuilder.com/forums/t/1-0-0-187-build-number/4826
**Category:** Discussion
**Created:** [April 26, 2012, 2:06am UTC](https://www.finalbuilder.com/forums/t/1-0-0-187-build-number/4826 "2012-04-26T02:06:01Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![rlove](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/rlove/32/27_2.png) [@rlove](https://www.finalbuilder.com/forums/u/rlove)
#### Post date: [April 26, 2012, 2:06am UTC](https://www.finalbuilder.com/forums/t/1-0-0-187-build-number/4826/1 "2012-04-26T02:06:01Z")

</div>

I am setting up my first configuration after the new install. &nbsp; &nbsp;I just realized that I might not be able to do what I do with FBS when it comes to the version number.

We typically populate the Version number like this.

Major.Minor.Release.Build - Where:

Major=Our Major Release Currently 5

Minor=Our Minor Release Currently 21

Release= Typically 0 but if we have to Hot deploy a change it increments

Build= SVN Revision Number, that way we know the exact code that produced that build.

I can see that you might need to know the build number in Continua (Not sure at this point) and I would be willing to change to:&nbsp;

Major.Minor.Release.Build - Where:

Major=Our Major Release Currently 5

Minor=Our Minor Release Currently 21

Release= Continua Build Number

Build= SVN Revision Number

But I can't see how this might be done.

---

<div class="post-metadata">

### Author: ![Vincent](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/vincent/32/938_2.png) [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)
#### Post date: [April 26, 2012, 2:28am UTC](https://www.finalbuilder.com/forums/t/1-0-0-187-build-number/4826/2 "2012-04-26T02:28:35Z")

</div>

It can be done but it’s not obvious just yet, lacking some doco in this area. This can only be done once you have added a repository to the configuration… go back to the page with the buildnumber on it and set the build numer to : 5.21.0.$Repository.YourRepoName.LatestChangesetId$   
  
 This obviously will only work for version control systems that use numbers for their changesets/revisions - Git & Mercurial for example use a hash.   
  
 If you type $ the build number field you should get some code completion happening. $ is used for objects (like Server, Repositories etc), % is for variables like in FB and FBSErver. So you could define some variables for the major,minor,release and end up with :   
  
 %Major%.%Minor%.%Release%.$Repository.YourRepoName.LatestChangesetId$   
 (I just noticed we need to widen the Version Format field!)   
  
 Note that LatestChangeSetId refers to the latest changeset associated with the build. Depending on your triggering setup there may be 1 or multiple changesets associated with each build.   
  
 HTH