Version 1.27 released on May 29, 2009

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.

For example, job J2 in Family F2 can wait on Job J1 in Family F1 by specifying the dependency like this:

    # This is in the F2 Family file
     J1::F1()

       J2()

For more information, check out the jobs and families configuration documentation.

Quick Links
Calendars
FAQ
Tokens
Security
Report a bug
HOWTO
Release Notes
1.31 2009-05-29
1.26 2009-05-19
1.25 2009-05-18
1.24 2009-04-26
1.23 2009-03-24
Change Log
1.31 2009-05-29
1.26 2009-05-19
1.25 2009-05-18
1.24 2009-04-26
1.23 2009-03-24
Features Coming Soon

Enhancements to the included web site
  We plan on adding contextual menus so that you can right-click on a job from the status screen and select one or more actions.
Simulator
  The simulator would show you how your jobs would run on dates that you specify, so that you can see what will happen rather than wait for the jobs to be run. You will also be able to change the exit codes of jobs, to see what would happen if a certain job failed.
Multiple Hosts
  Specify which host on a network a job should run on, and what userid it should run as.