neos team mailing list archive

[Holger Röder <holger.roeder@xxxxxxxxxxxxxxxxxxxxxxxxxxx>]

Tool independence is nice to have, but in this case, I think we can
stick to bazaar and use the revision numbers it provides. If we ever
change our configuration management system, we'll know that revisions 1
to X can be found in the 'old' bzr repository.

But how can we make sure that a running RevAger instance knows the
revision number it was built from? Updating the appResources.properties
file during the build process might be a workaround, e.g. by adding the
following commands to our build script (exec + propertyfile in 'init'
target):

<property name="propertiesfile"  value="build/neos/resi/resources/appResources.properties" />
...
<exec executable="/usr/local/bin/bzr" outputproperty="revno">
	<arg value="revno" />
</exec>
<propertyfile file="${propertiesfile}" comment="set revision number in properties file">
 	<entry key="appBuild" value="${revno}"/>
</propertyfile>

However, this assumes that bzr is installed - which might not be the
case if a user downloaded RevAger.src.zip from out website. :) We'd also
have to deal with different binary locations etc. - argh! :)

Any other ideas?

-- 
(FR) Build number and release date should be obtained automatically
https://bugs.launchpad.net/bugs/497927
You received this bug notification because you are a member of Team
N.E.O.S., which is the registrant for RevAger.

Status in RevAger: New

Bug description:
We should find a way to automatically integrate the current build number from the VCS (i.e. using "bzr revno", but a solution which does not depend on the bzr binary would be even better) and the current date (should be rather simple) dynamically into the build script, that is, without relying on resources/appResources.properties. This would simplify bug tracking from development builds. Since these strings are currently updated rather rarely, "Help->About" often reports incorrect information.