On Tue, 2005-04-26 at 19:22 -0700, Bryce Harrington wrote: > Hi all, > > One of the things I've needed for automating the nfsv4 regression tests > is something to look for new patches (and tarballs) in a cron job, > download them, and trigger the tests. > > It turns out for hotplug testing I have exactly the same need. > > This tool is derived largely from Judith Lebzelter's SourceSync module > from the PLM. I needed something similar, but simpler, that can be run > from the cmdline and doesn't require a database. > > Basically, you run it like this: > > ./package_retriever -d /testing/packages hotplug_pkgs.txt > > where hotplug_pkgs.txt might look like this: > > PACKAGE: hotplug_cpu > URL: http://sr71.net/patches/ > DEPTH: 2 > WANTED: patch-2\.6.*gz > NOTWANTED: patch-2\.6\.[89].*gz > NOTWANTED: patch-.*test\d*\.gz > > and it downloads new files to /testing/packages/hotplug_cpu/ > > Anyway, if anyone would find this script useful, I've posted it here: > > http://developer.osdl.org/dev/nfsv4/tools/ > > I'll probably be posting some updates once I've started putting it to > use in the regression testing. > Could it be worked back into PLM? i.e. The database is used to determine what needs to be pulled but PR does the actual pulling? Tim > Bryce > > > ------------------------------------------------------- > SF.Net email is sponsored by: Tell us your software development plans! > Take this survey and enter to win a one-year sub to SourceForge.net > Plus IDC's 2005 look-ahead and a copy of this survey > Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix > _______________________________________________ > Plm-devel mailing list > Plm-devel@xxxxxxxxxxxxxxxxxxxxx > https://lists.sourceforge.net/lists/listinfo/plm-devel -- Timothy D. Witham - Chief Technology Officer - wookie@xxxxxxxx Open Source Development Lab Inc - A non-profit corporation 12725 SW Millikan Way - Suite 400 - Beaverton OR, 97005 (503)-906-1911 (office) (503)-702-2871 (cell) (503)-626-2436 (fax)
