From: Dannes W. <da...@ex...> - 2013-10-28 15:13:34
|
Hi Joe, In the build scripts we use the "git.commit" variable: in our build system ( build.exist-db.se) this property is set by Jenkins. when doing this by yourself, you need to set the same property. It is difficult to do this in ant in a platform-agnostic way ( http://stackoverflow.com/questions/2974106/how-to-lookup-the-latest-git-commit-hash-from-an-ant-build-script), therefore it is IMO better to leave it out from the scripts. I'd not be fond to have a dependency on jGIT or so. regards Dannes ref: https://github.com/eXist-db/exist/blob/develop/build/scripts/build-impl.xml On Mon, Oct 28, 2013 at 3:53 PM, Joe Wicentowski <jo...@gm...> wrote: > Hi all, > > When I check out the develop branch of the eXist-db/exist git > repository and build, the git revision doesn't appear to be added to > VERSION.txt. I see lots of mentions of "git.commit" in the build > files but can't track down where this property is set. > > Is there a way for eXist-db to detect the git revision it was built from? > > Thanks, > Joe > > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most > from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > -- eXist-db Native XML Database - http://exist-db.org Join us on linked-in: http://www.linkedin.com/groups?gid=35624 |