Bill, Could you have a perfect build sitting out on a drive somwhere and diff the perfect build against the one that was produced?? This seems like it would be the quickest way to verify the build... If you use actuall file names in a script etc, it seems like it would be a pain to maintain as new files are added, deleted, etc. A patterneset would be nice to confirm the structure of the build and specific files are there... You could compare the build against a cvs structure, but this would depend on the structure of your modules, and again whether you want to verify the existence of files vs. how they were modified during the install proc..
Mike -----Original Message----- From: Bill Lynch [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 01, 2003 10:16 AM To: Ant Users List Subject: Re: Release/package testing Not to pester, but any ideas on this? Any outside projects for this sort of thing? Cheers, --Bill Bill Lynch wrote: > All, > > I use ant to run generated my releases and I've slowly been adding some > testing of my releases into the process. For example, I unzip the zip's > and tar.gz's of a source release and try to build it to make sure > everything was put together successfully. > > As a next step I'm interested in verifying the actual files in the > build. Can anyone recommend a good way to do this? Ideally, I'd have a > patternset which would represent a "perfect" build and check that > pattern against what was actually produced. Is there anything built in > to Ant (or other extensions) to help me with this? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
