Just been looking at http://wiki.apache.org/gump/BrutusConfig/NightlyBuild.
It looks like a good solution for handling nightly builds. AFAICS, the only variable parts of the builds are the svn/cvs fetch from whatever the default repository has been set to, so it looks as though the only backdoor is either hacking into the nightlybuild account - or updating the project repository itself, which should be detected by the commit message to the developer list. Archives such as http://archive.apache.org/dist/httpd/ display a header message describing the contents. Perhaps it would be a good idea to do something similar for the nightly output directories, e.g. some kind of disclaimer, with links to the official download pages? It would be useful if the cvs/svn branch could be specified, perhaps as a suffix to the repo parameter, e.g. cvs:rel-2_0, with default of HEAD. S. P.S. There seems to be a cut-n-paste error in the licence search part of the script. AFAICS, if there are any build artifacts, these will be taken as the license to publish the build artifacts ... Presumably this is fixed in the actual code, as the licence files do appear in the output. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
