HOWTO: Timestamp Your Build
Ever wondered how long an Ant task takes? Or where to look for ways to performance tune your build?
Well, here’s a quick way to add changing timestamps to your Ant script or PDE build log, so you can see how long specific subtasks and antcalls take, or when they occur. This trick gets around the problem that once a property is set in an Ant script, it’s immutable.
Posted January 25th, 2008 by in category: ant, build, pde, scripting, testing
You can skip to the end and leave a response. Pinging is currently not allowed.
4 Responses to “HOWTO: Timestamp Your Build”
Leave a Reply
You must be logged in using your Eclipse Bugzilla account to post a comment.
Gunnar Wagenknecht Says:
January 25th, 2008 at 04:35 am
Nice. Thanks for this tip!
Ketan Padegaonkar Says:
January 25th, 2008 at 04:58 am
I generally use:
https://antutility.dev.java.net/
and
http://ant-contrib.sourceforge.net/tasks/tasks/performance_monitor.html
One of these gives a task level timing, the other a target, build-file level timing. That way my build scripts do not contain any other clutter that I myself need to read through to make sense.
Eugene Kuleshov Says:
January 25th, 2008 at 05:51 am
Long, long time ago I’ve hacked together an Ant logger that dumps execution of all tasks and targets. http://www.jroller.com/eu/entry/profiling_ant_builds_take_two
I even submitted an enhancement request bug 95337
Nick Boldt Says:
January 25th, 2008 at 12:15 pm
Thanks, guys. Also very cool solutions (with *way* more useful information than just ‘when did a task start/end’)!
(I just wanted something fast. It was after 2am and I was just looking to confirm that an event in the build’s flow — calling the task in the EMF doc plugin — happened at about the 9 minute mark.)