Hi Claude,
Rather than looking at the delagent.c code, just run it (it's a
command line utility).
Usage: ./delagent [options]
List or delete uploads.
Options
-i :: Initialize the DB, then exit.
-u :: List uploads IDs.
-U # :: Delete upload ID.
-l :: List uploads IDs. (same as -u, but goes with -L)
-L # :: Delete ALL licenses associated with upload ID.
-f :: List folder IDs.
-F # :: Delete folder ID and all uploads under this folder.
Folder '1' is the default folder. '-F 1' will delete
every upload and folder in the navigation tree.
-s :: Run from the scheduler.
-T :: TEST -- do not update the DB or delete any files (just
pretend)
-v :: Verbose (-vv for more verbose)
The only thing on your list that I think may give you trouble is
selecting the license information from the database. This is one
reason why we are greatly simplifying the process in 1.2. For now,
if you could share your report definition, we could offer some
specific help.
Bob Gobeille
On Jun 24, 2009, at 11:20 AM, Laser, Mary wrote:
Hi Claude,
Answers to your questions:
1) Yes, cp2foss is the best solution.
2) email notification is NOT sent out for every sub-job scheduled to
process an upload. You will only receive one notification of the
completed analysis. If you prefer to use a database trigger, that
should work, too.
3) Yes, you can definitely query the database for license info. You
might want to take a look at the common set of php functions for
license queries: http://fossology.svn.sourceforge.net/viewvc/fossology/trunk/fossology/ui/common/common-license.php?revision=1579&view=markup
4) I've never created a BIRT report but, from what I know of it,
this should be possible.
5) There is a agent, accessible via the fossology UI, to delete
uploads. You may want to take a look at this code to see how it's
done: http://fossology.svn.sourceforge.net/viewvc/fossology/trunk/fossology/agents/delagent/delagent.c?view=markup
License scanning is currently done manually on a project-by-project
basis.
Mary
________________________________
From: [email protected] [mailto:[email protected]
]
On Behalf Of [email protected]
Sent: Wednesday, June 24, 2009 6:44 AM
To: [email protected]
Subject: [FOSSology] Automated Procedure using Fossology
Hello,
We are planning on implementing the following automated procedure
using Fossology and would
like to find out if this is a plausible solution or if there is
a better approach of doing
the automation.
1. Use cp2foss to upload files for scanning.
2. Implement a job monitoring utility program to determine when job
has completed. One
way we are thinking of doing this is to use a database trigger.
The reason we do not
want to depend on the e-mail is because multiple e-mails are
sent out for each sub-job
associated with an uploaded file - Is this correct?
3. When a job has completed, extract the data results into our own
database. We hope we
could read the fossology database to get the license types of
an uploaded file out.
4. Interpret the results from the database and produce a BIRT report.
5. We are still lacking an automated way to delete uploaded files
to make spaces for new
uploaded files. Any ideas on this?
Meanwhile, is there an automated way in which HP using Fossology to
scan its build for
licenses and if so, how is it done? Any help is greatly
appreciated.
Thank You
_______________________________________________
fossology mailing list
[email protected]
http://fossology.org/mailman/listinfo/fossology
_______________________________________________
fossology mailing list
[email protected]
http://fossology.org/mailman/listinfo/fossology
