Release Notes: You can now configure TaskForest to automatically retry running a job if it fails. The number of times it retries and the amount of time between retries are configurable on a per-job basis. TaskForest now also features a very powerful email system. You can configure TaskForest to email you when a job fails, when a job is retried, and when a job succeeds after failing and being retried. Each kind of email can be sent to a different email address, and these email addresses can be configured system-wide, or for each job, or for anything in the middle.
Release Notes: A button was added to the logs form on the Web site that pops up a calendar window to help you select a date. The logs display page now has links to navigate to the next and previous days. Some more test cases that wouldn't run properly during certain times of the day.
Release Notes: You can now place jobs on hold and later release the holds off the jobs. The Web server now supports a default time zone option for display, as well as colored statuses. This version gracefully handles the case where a job is marked for rerun and then removed from the Family file before it has the chance to rerun. The Web site now prunes out carriage returns from job files. This would cause interpreted scripts to fail when the "#!" line contained a carriage return. Finally, this version fixes a few test cases that wouldn't run properly during certain times of the day.
Release Notes: You can now have a job in one Family depend on the completion of a job in another Family. This allows you to have one Family depend on another. This release also fixes a bug with recurring jobs, and supports the chained option for taskforestd and taskforestdssl.
Release Notes: This release fixed an unnecessary dependency on the Perl module Date::Calc, which may have caused tests to fail.
Release Notes: This release supports calendars. A calendar is a set of rules that defines on what days a job may run. Each rule may or may not conclusively determine whether or not a Family should run today. The rules are evaluated in the order in which they are specified. The last rule that conclusively determines whether of not a Family should run wins, in the case of conflicting rules. If none of the rules is conclusive, then the Family will not run today. You can set rules to specify certain dates or ranges of dates, or specific days, like "third Friday of every month."
Release Notes: This release introduces the concept of tokens. If a job depends on a token, it must acquire a free token before it can run, or wait for another job to release a token after completion. Since there is a finite set of tokens, you can use tokens to prevent too many jobs from running at the same time. This release also formalizes the way Families with foreign time zones are handled. This allows you to "time shift" your family, essentially allowing your family to run for 24 hours in a later timezone. This shifts the end of day towards the end of the family's running time.
Release Notes: This release fixes a nasty bug where Family files were not being parsed properly if the files were in DOS format (with CRLF endings, instead of just LF). Unfortunately, most Web browsers save textarea text with CRLF, so a Family file that was originally in Unix format (LF) could wind up being in DOS (CRLF) format if you edited it via the Web site.
Release Notes: New in this version is the ability to release all dependencies from a job. This makes the job available to run immediately, regardless of how many jobs it is supposed to wait for, or what time dependency it has. Releasing a job effectively changes its status from 'Waiting' to 'Ready.'
Release Notes: A bug that was causing the rerun and mark commands run with the --cascade or --dependents_only flag to print an error message when there was, in fact, no error, and to possibly exit before rerunning or marking all requested jobs was fixed.