[Anthill] build number

[Maciej Zawadzki]

Asbjorn,

Some information on this is provided in the FAQ -- 
http://www.urbancode.com/projects/anthill/faq.jsp.  Let me know if you 
need more info.

Q: What general fomat does the Anthill version file use?
A: The general format of the version file is:

<prefix><buildNo><postfix>

where

<prefix>can be any String like "MyProduct" or "1.0."
<buildNo>has to be a number like 1 or 50 or 1150
<postfix>can be any non numeric String like " alpha" or " beta"

So if you have a version such as 1.2.3.4, then 1.2.3. is the <prefix>, 4 
is the <buildNo> and the <postfix> is an empty string. The 
UrbanCodeVersionAdapter looks for the build number starting at the end 
of the string and working its way forward. The build number is the first 
numeric portion that it encounters. So you could have a version such as 
1.2.3.1150 alpha and then the build number would be 1150.

Q: What format does the Anthill version file use when building on a branch?
A: If you are on a branch, then the <prefix> must contain the name of 
your branch as specified in the RepositoryAdapter properties page. This 
is mostly because we could not figure out how to assign version numbers 
to multiple branches while making sure that each version number was 
unique across all branches Including the branch name in the version 
number solves this problem. We're definitely open to other ideas here.

So, if you are using CVS, and you have a BRANCH called "My_Release_1", 
you would configure the RepositoryAdapter to check out that branch. In 
the RA properties page there is a field that allows you to specify the 
branch that Anthill will build. Then, the version file in that branch 
will need to contain a string like the one below: My_Release_1 1.0.1150 
or My_Release_1 1150

Anthill will then increment the last numeric portion that it finds -- 
1150 in each case.

We usually have multiple branches of a project in Anthill at the same 
time. We have a separate version file for each branch. The TRUNK may 
have a version file called MyProject.version and the My_Release_1 branch 
may have a version file called MyProject.My_Release_1.version. Each 
version file would have different version string inside.



Regards,

--Maciej


Asbjorn Hoiland Aarrestad wrote:
> hi!
> 
> I have a problem with the build number. It does not increase each time 
> we do a build. Does anybody know the conditions for increasing the build 
> number, and how to make sure that each build gets a different buildnumber?
> 
> 
> - asbjørn