I am setting up my first configuration after the new install. 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:
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.