That sounds like exactly what I want. How can I get that value into build.id from ant? Is there an ant task that will run shell commands?
I like your metadata idea. I suppose what you really want to know is if there are un-checked-in changes in the tree, but that would be too slow in svn. On 2006-06-24, at 12:34 EDT, Benjamin Shine wrote: > I think this gets set up in > build-tools/build-opt.xml: <condition property="build.id" > value="x.x.x.x" else="INTERNAL"> > Then it gets applied in WEB-INF/lps/server.xml target lps-xml, > which does overwrite-with-filter. > > In tools/trunk/build-tools/nightly/nightly-go.sh I do this: > buildnum=`svn info -rHEAD http://svn.openlaszlo.org/openlaszlo | > grep Revision | sed -e"s/Revision: //"` > leave out the -rHEAD and you've got what you want: the revision of > the repository you've got > > For consistency -- if you feel like consistency -- do this to get a > build identifier: > (start with $branch = branches/legals, or trunk > branchmunge=`echo "${branch}" | sed "s/\//-/"` > buildname=${buildnum}-openlaszlo-${branchmunge} > > or maybe (going beyond consistency, to metadata) > buildname=${buildnum}-openlaszlo-${branchmunge}-${USER}-`date` > > > > > On Jun 24, 2006, at 8:29 AM, P T Withington wrote: > >> Is there a way we can get the 'build version' number into the >> canvas? There seems to be a canvas.build variable that is >> currently always set to x.x.x.x, which I guess is intended to hold >> a build number. I guess what I am really asking, is there a way >> to ask svn what revision my playpen is synced to? If I can get >> that, I can probably figure out how to jam that into the canvas in >> the appropriate spot. >> >> I think this info would be useful for bug reports. > > benjamin shine > software engineer > [EMAIL PROTECTED] > > > _______________________________________________ Laszlo-dev mailing list [email protected] http://www.openlaszlo.org/mailman/listinfo/laszlo-dev
