FB4 Project Throws Exception In FB5

FinalBuilder Discussion
1

I’m in the process of converting our FB4 projects over to FB5. In doing so, I’ve got a set of steps in one project that does this:

1. Determine the date as of 10 days ago.
2. Get a FileSet with all files on a network share (it’s where the HTML logs from FB4 went), filtering only those files outside the date range.
3. Delete the matching files.

The idea was that all log files older than 10 days get deleted when a build is run.

Under FB5, the build is throwing an error when it gets the #2 above:

Date filter using date: 1/6/2007
pattern “.” is empty
However, when I go to that directory directly, I can see several files sitting there. So I’m not sure whey the FileSet is coming up empty.

That said, this raises a larger question… it seems that FB5 now manages log files for us. While I can’t figure out how to tell it WHERE those files should go, I do see that there’s a Logging page under Tools->Options that lets me specify a maximum number of logs. Is this essentially doing what the actions above were supposed to?

Thanks,

J Donnici

2

Doh… I should have pointed out that the log files it’s gathering into the FileSet are being created by an Export Log File action at the tail end of the build. This was done so that they could be sent as email attachments when a build failed.

In any case, I know where those files are coming FROM… just not why fetching them into a fileset is throwing the exception.

3

Jeff,

I just did a quick test and it’s working for me. Can you send your project (or a sample that shows the bug) to support so we can see excactly what’s happening please?

(re: those log files, as you probably have figured out already the max number of logs to keep is for the log entries within the project log file).

.t8

4

Tate,

I tracked down the problem. Under FB4 the action that was failing (Define FileSet) had a Filespec of “.”. When that project was opened/converted in FB5, the Filespec disappeared from that action, but the “Comment” was set at “.”.

So after looking closely at the action, I could see that it was missing the filespec and adding “.” back in there took care of it.

Thanks,

Jeff

5

ooh, sorry about that Jeff… but thanks for letting us know.